[
https://issues.jboss.org/browse/JGRP-1262?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1262:
--------------------------------
The 2 new properties are
- client_bind_port: the port on which the local client socket should listen (o = random)
- port_range: the number of ports to increment client_bind_port if no free port is found
- bind_addr is used to bind the client socket
Bind FD_SOCK outgoing socket
----------------------------
Key: JGRP-1262
URL:
https://issues.jboss.org/browse/JGRP-1262
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.6.13
Reporter: Dennis Reed
Assignee: Bela Ban
Priority: Minor
Fix For: 2.6.18, 2.11.1, 2.12
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).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira