[jboss-jira] [JBoss JIRA] Commented: (JGRP-515) UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-515?page=comments#action_12362468 ] 
            
Bela Ban commented on JGRP-515:
-------------------------------

I'm tempted to reject this patch, as the reason for the issue you have seems to be a bug in certain OSs (Linux for example), where binding to the wirldcard address (0.0.0.0) does *not* reject multicast traffic with a different class D address !

I actually want to use the wildcard address (only binding the mcast_sock to mcast_port), as this eliminates chances of nodes picking the wrong NIC and therefore not seeing each other.

If you want to separate traffic for different clusters on some operating systems, pick different mcast addresses *and* ports.

> UDP.java requires the multicast address in the multicastsocket constructor to fix crosstalk on certain operating systems
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-515
>                 URL: http://jira.jboss.com/jira/browse/JGRP-515
>             Project: JGroups
>          Issue Type: Patch
>         Environment: Tested on Fedora Core 6, JDK 1.5.0_10
>            Reporter: ggimler
>         Assigned To: Bela Ban
>             Fix For: 2.5
>
>         Attachments: UDP.java
>
>
> I'm submitting a patch for a crosstalk issue described below.
> I'm trying to debug a problem I'm seeing when running JGroups on the
> same network/machine as another application that is sending/receiving
> data via regular multicast (not through JGroups).  I'm using version
> 2.4.1-SP3.  My scenario is as follows...
> JGroups send on 228.0.0.1:50000
> JGroups receive on 228.0.0.1:50000
> This works fine.  When I start up another application that does
> Sends regular multicast on 228.0.0.2:50000
> Receives regular multicast on 228.0.0.2:50000
> Then the JVM with the JGroups sender/receiver complains with:
> May 15, 2007 4:47:59 PM org.jgroups.protocols.TP handleIncomingPacket
> WARNING: packet from 192.168.101.133:36594 has different version
> (26725) from ours (2.4.1). Packet is discarded
> The patch is in UDP.java:

-- 
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