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

PSFletchTheTek's avatar
PSFletchTheTek
Icon for Cumulonimbus rankCumulonimbus
Jun 05, 2023

SOCKS Proxy Config, floating or non-floating interface?

Hi all, I've got a socks proxy configured on LTM in a big-ip cluster. Would you expect the onward comms to come out of the floating or none floating ip? It's currently coming out of the non-floa...
application delivery
PSFletchTheTek's avatar
PSFletchTheTek
Icon for Cumulonimbus rankCumulonimbus
Jun 06, 2023

Hi,

i've got it set to automap, but i'll try enforcing a snat pool and see if it works, but i thought automap would do the same.

The one thing to note, is socks does not work like the load balancing that the f5 normally does, it has no pool in the config, the socks protocol tells the f5 where to communicate to.

I'll try snat pool and report back. thanks

Paulius's avatar
Paulius
Icon for MVP rankMVP
Jun 06, 2023

PSFletchTheTek At face value both automap and a SNAT pool list work the same overall but source from different IPs. Automap definitely uses the closest non-floating self-IP closest to the destination which is the behavior that you are seeing. When you make the switch from automap to SNAT pool list ensure that you are allowing that SNAT pool list IP outbound to reach the particular destinations you are attempting to reach. As whisperer noted, even though you aren't load balancing traffic the way traditional virtual servers are configured it still functions the same way as far as passing traffic that has arrived at the F5 much like a forwarding virtual server functions when you have an F5 in path and routing traffic from external to internal on the F5.