Forum Discussion
Deployment of X-forwarder on all VIP
Hi lttarvina,
first let us understand why you want to apply this iRule to all your virtuals? Do you understand what this iRule does?
Let me start by answering your first question. The 10.10.10.10 is the client IP address.
If I use tmsh to look at the connection table for my virtual server (vs_nginx_http) I will see this output:
root@(big-ip)(cfg-sync Standalone)(Active)(/Common)(tmos)# show sys connection virtual-server vs_nginx_http
Sys::Connections
192.168.57.1:39236 192.168.57.80:80 10.0.2.246:39236 10.0.2.80:80 tcp 6 (tmm: 1) none none
Total records returned: 1
So my client IP address is 192.168.57.1, [IP::client_addr].
My virtual server IP address is 192.168.57.80, [IP::local_addr] in a client-side iRule event.
My SNAT IP address is 10.0.2.246, also [IP::local_addr] but in a server-side iRule event.
And the IP of the node / pool member is 10.0.2.80 [IP::server_addr].
The iRule you are looking at will add a log entry every time someone with the IP 10.10.10.10 invokes a request on any virtual server that has this iRule attached.
If you have a busy system and you get a lot of requests from whatever IP you insert into this iRule, you will create A LOT of log entries.
What exactly are you trying to achieve? Maybe addint the iRule to only one virtual is enough, for troubleshooting something?
KR
Daniel
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