The client-side of the TCP connection FD_SOCK makes is not bound to a specific IP, so the OS just chooses one.
This makes it difficult to set up strict firewall rules on a multi-homed server.
Customer would like a way to bind the outgoing socket to a specific IP
(either re-using bind_addr or adding an additional property would work).
- relates to
-
JGRP-1288 FD_SOCK ignores port_range when opening server sockets
- Resolved