Forum Discussion
jwlarger
Cirrus
CirrusTest access sourcing from float
To test firewall rules we telnet to the pool member's service port, which proves access for the self IPs, but not for the float. Anyone know how to source from the float?
# telnet -b floating_self_ip destination_ip-b hostalias Uses bind(2) on the local socket to bind it to an aliased address (see ifconfig(8) and the ``alias'' specifier) or to the address of another interface than the one naturally chosen by connect(2). This can be useful when connecting to services which use IP addresses for authentication and reconfiguration of the server is undesirable (or impossible).Be aware of route domains; https://devcentral.f5.com/s/question/0D51T00006i7apM/telnet-to-server-from-f5.
jwlargerCirrus
CirrusTested today with no joy. v11.6.3, only one route-domain (0). Selecting the floating self IP results in:
Cannot assign requested address
No connection.
Escape character is '^]'.
SetSockOpt: Bad file descriptor
Lidev
MVP
MVPsame result on v13.1, I'm going to end up believing that there's no way to test flows from floating IP 😳 (nc -s give the same bind failed).
Any others solutions ? @Andrew C. - F5 Support Engineer
Andrew-F5Employee
It appears that we associate the non-floating self-ip to the VLAN despite the floating *also* using the same vlan.
The linux subsystem references TMM's VLANs as physical interfaces, non-floating IPs are assigned to the VLAN as you'll notice with "ifconfig".
- Andrew-F5
Try this:
# tmsh
# telnet -b floating_self_ip destination_ip port
In my lab it allowed me to use my floating self without issue. Performing telnet from TMSH allows telnet to have some awareness of TMM objects and constructs such as floating self-ips.
- Lidev
same issue 😕
#tmsh
# telnet -b 10.xx.xx.xx yy.yy.2.2 443
Trying yy.yy.2.2...
Couldn't bind to 10.xx.xx.xx
it works with selfip but not with floating selfip