For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

chris_connell_1's avatar
chris_connell_1
Icon for Nimbostratus rankNimbostratus
Dec 21, 2010

Floating self IP and virtual IP using same address.

Hi     A client is sending wap traffic to a virtual server (destination IP for the request is the virtual address defined on the F5 virtual server). This is not working in that I cannot see any ...
config
design
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jan 21, 2011
By chance, did you try netcat? You may find that curl, wget or netcat will honor the route domain syntax - I'm not sure though.

 

 

You basically need utilities that support IPv6 to connect from the LTM CLI to non-default route domains. So curl and netcat on LTM will work. But wget isn't included by default.

 

 

Aaron - if you're doing an HTTPS VIP, you're no longer able to manage device via Self-IP:443 then? How about if you're doing SNAT Automap? Do replies to automap address hit VIP instead of self-ip?

 

 

I expect if you define a VS on 443 on an IP defined as a self IP, you won't be able to connect to the admin GUI on that IP. If you enable SNAT using that self IP, TMM shouldn't use any reserved ports (<1024) to source traffic from. The TMM connection table should handle packets for established connections so there shouldn't be an issue there.

 

 

Aaron