-
Type:
Sub-task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP_EWP 5.1.0
-
Fix Version/s: EAP_EWP 5.1.1
-
Component/s: Clustering
-
Labels:None
-
Affects:Release Notes
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
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).