[jboss-jira] [JBoss JIRA] Commented: (JGRP-916) TCP_NIO uses default IP address instead of bind_addr

[Victor N (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458367#action_12458367 ] 

Victor N commented on JGRP-916:
-------------------------------

Bela, did you set bind_addr to 192.168.1.6 for example?
The problem is not that "it does not work at all" - it does work, but the traffic is not limited to this IP (some trrafic will use 192.168.1.5).

> TCP_NIO uses default IP address instead of bind_addr
> ----------------------------------------------------
>
>                 Key: JGRP-916
>                 URL: https://jira.jboss.org/jira/browse/JGRP-916
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.7
>         Environment: ubuntu linux 8.10
>            Reporter: Victor N
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.6.9, 2.8
>
>
> I have seen that TCP_NIO ignores 'bind_addr' in some requests, in the same situation TCP works perfectly.
> How to reproduce.
> let's assume you have 2 computers - the first one with 1 physical network card but this card have several IP addresses (the first IP is considered default); the seconds computer just has 1 network card with one IP.
> node A - run it at the first computer and set 'bind_addr' to a NON-DEFAULT IP address
> node B - run it at the second computer
> You will see in networks sniffer that some packets goes from wrong address - instead of 'bind_addr", the default IP is used. And the communication does not work.
> In the same situation TCP works perfectly, so it seems to be bug in TCP_NIO.

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