[jboss-jira] [JBoss JIRA] Closed: (JGRP-274) Don't bind to a NIC if bind address is not set

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-274?page=all ]

Bela Ban closed JGRP-274.
-------------------------

    Resolution: Duplicate Issue

JGRP-344 is the real issue

> Don't bind to a NIC if bind address is not set
> ----------------------------------------------
>
>                 Key: JGRP-274
>                 URL: http://jira.jboss.com/jira/browse/JGRP-274
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.3 SP1, 2.3, 2.2.9 SP3 (2.2.9.3), 2.2.9.2, 2.2.9.1, 2.2.9, 2.2.8, 2.4
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5
>
>
> If -Dbind.address or bind_addr are not set, JGroups picks the NIC to bind sockets to itself. However, especially for ServerSockets, this may not be desirable because we may want to have ServerSockets be able to receive packets through all interfaces, e.g.
> - NICs are 192.168.5.2, 192.168.0.2 and 127.0.0.1 (loopback)
> - When the bind address is set to 192.168.5.2, a given ServerSocket on port 7500 will *only accept packets from this NIC*
> - If someone connects to 192.168.0.2:7500 or 127.0.0.1:7500, the client will not be able to establish a connection because nobody is listening on those ports on the given NICs
> - If bind address was not set, this would be possible
> - Affected: FD_SOCK, FD_PING, TCP, TCP_NIO etc
> - We need to think about semantics for MulticastSockets where a wildcard address (not setting the bind address) means that the operating system picks the NIC, and *not* that the MulticastSocket will listen on all interfaces for incoming packets

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira