We've been using F5 for load balancing our MWGv7 appliances and have recently found that the F5 passes the client source IP to the MWG in the X-Forwarded-For (XFF) field, and that we lots of traffic reaching the MWG with the F5 address as the client source IP. This can be seen in both MWG access logs and packet traces. This configuration appears to work but results in debugging problems (can't isolate Connection Traces to a single IP) and some web application problems.
Has anyone else using F5 encountered this? How can the F5 be configured to send the true source IP and not inject the XFF field?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.