X-Forwarded-For displays wrong ip (v6) in logs

Showing results for 
Show  only  | Search instead for 
Did you mean: 

X-Forwarded-For displays wrong ip (v6) in logs

L1 Bithead



We have a azure setup, web application, where an agw first terminates traffic and applies xff and then forwards to firewalls which then decrypt the session. We have X-Forwarded-For enabled and usually works fine and displays the correct ipv4 address in logs. From time to time though logs instead display ipv6 addresses which we dont use and afaik we know there is no ipv6 in play at all.


We are having a hard time troubleshooting since pcaps on firewalls are encrypted, is there a way around that? We've tried to look at pcaps on clients where we can decrypt in wireshark but xff is not visible there.


L4 Transporter

Hello @Magnus_App 

It sounds like a software-related issue.

You may open a TAC case to get the fix/workaround.


Network Security Engineer
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!