Forum Discussion
a problem about get source address through X-forward-for
Here I could see that your another VIP 134.175.22.206:9091 The client original address is visible to the backend pool member
1st column is same to 3rd column
106.19.21.235:56092 134.175.22.206:9091 106.19.21.235:56092 134.176.1.227:9091 tcp 48 (tmm: 3) none
In that case your pool member 134.176.1.227:9091 will response directly to the Client IP 106.19.21.235:56092 bypassing F5 load balancer , are you seeing any asymmetric routing issue on this VIPs
- 1qazJun 05, 2020
Nimbostratus
thanks,
VIP 134.175.22.206:9091 don't use SNAT,no automap
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com