[JBoss JIRA] Created: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
9:20 a.m.
Binding to mcast address in UDP.java is not working on Linux with IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
9:24 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Bela Ban updated JGRP-956:
--------------------------
Fix Version/s: 2.8
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
8:57 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Bela Ban commented on JGRP-956:
-------------------------------
Apparently, we need to use global IPv6 addresses, or -if not - we need to provide a
scope-id. The algorithm for generating the scope-id is (onlt for *non global* addrs):
* If there is an attached scope-id: no-op
* Else
o Find all interfaces which have the address configured
o If the resulting set has 1 interface: add the interface name
to the address, ie. ADDR%IFNAME
o Else if the result set has more than 1 address: throw an
exception saying that the user has to provide the non-global
IPv6 address with a scope-id
This should be relatively simple to implement, and JGroups finding out the correct
scope-id should also be simple, except for the case where identical link-local addresses
are defined on multiple interfaces.
This needs to be in the 2.4 and 2.6 branches and on head
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
8:21 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
This last comment has been relocated to a separate issue: JGRP-977.
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
8:23 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
The confusing error message which is generated when we try to bind to IPv6 multicast
address is:
16:35:19,970 INFO [DefaultPartition] Initializing partition DefaultPartition
16:35:20,231 WARN [UDP] could not bind to /ff02:0:0:0:0:1:2:3 (IPv6 address); make sure
your mcast_addr is of the same type as the IP stack (IPv4 or IPv6).
Will ignore mcast_addr, but this may lead to cross talking (see
http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking for details).
Exception was: java.net.SocketException: Invalid argument
16:35:20,289 INFO [STDOUT]
---------------------------------------------------------
GMS: address is fe80:0:0:0:215:17ff:fe2d:6821:44270 (cluster=DefaultPartition)
---------------------------------------------------------
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
11:14 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
Well, it turns out that it is possible to bind to IPv6 multicast addresses, that it does
not lead to crosstalk when we do so, and that this jira issue was the result of incorrect
coding of the Java system property java.net.preferIPv6Stack.
I modified Brian's promiscuous.jar so that it took an additional boolean parameter:
true -> bind to multicast socket; false -> bind to multicast port only.
So, in the case of IPv4 addresses, we can bind to port only:
$ java -jar promiscuoustraffic.jar 192.168.2.12 192.168.2.12 230.10.11.12 230.10.11.13
64000 1 false
setting up sender socket with address /192.168.2.12
setting up good receiver socket with address /230.10.11.12
binding mcast socket to port:64000
setting up bad receiver socket with address /230.10.11.13
binding mcast socket to port:64000
Listening on address /230.10.11.12
Listening on address /230.10.11.13
Sending 'Hello' on /230.10.11.12:64000
/230.10.11.13:64000 -- Received Hello
/230.10.11.12:64000 -- Received Hello
Bad news. Detected the Promiscuous Traffic problem. Received Hello on undesired address
/230.10.11.13
Or we can bind to multicast address:
$ java -Djava.net.preferIPv4Stack=true -jar promiscuoustraffic.jar 192.168.2.12
192.168.2.12 230.10.11.12 230.10.11.13 64000 1 true
setting up sender socket with address /192.168.2.12
setting up good receiver socket with address /230.10.11.12
binding mcast socket to address:/230.10.11.12:64000
setting up bad receiver socket with address /230.10.11.13
binding mcast socket to address:/230.10.11.13:64000
Listening on address /230.10.11.12
Listening on address /230.10.11.13
Sending 'Hello' on /230.10.11.12:64000
/230.10.11.12:64000 -- Received Hello
Good news. Did not detect the Promiscuous Traffic problem.
We can now show that promiscuous traffic does not occur when binding to multicast address
on Fedora 8 with JDK 5:
$ java -jar promiscuoustraffic.jar 3ffe:ffff:100:f101::1 3ffe:ffff:100:f101::1 ff0e::1:2:2
ff0e::1:2:3 64000 1 true
setting up sender socket with address /3ffe:ffff:100:f101:0:0:0:1
setting up good receiver socket with address /ff0e:0:0:0:0:1:2:2
binding mcast socket to address:/ff0e:0:0:0:0:1:2:2:64000
setting up bad receiver socket with address /ff0e:0:0:0:0:1:2:3
binding mcast socket to address:/ff0e:0:0:0:0:1:2:3:64000
Listening on address /ff0e:0:0:0:0:1:2:2
Listening on address /ff0e:0:0:0:0:1:2:3
Sending 'Hello' on /ff0e:0:0:0:0:1:2:2:64000
/ff0e:0:0:0:0:1:2:2:64000 -- Received Hello
Good news. Did not detect the Promiscuous Traffic problem.
and that if we prefer the IPv4 stack with an IPv6 mcast address, we get the exception
above:
$ java -Djava.net.preferIPv4Stack=true -jar promiscuoustraffic.jar 3ffe:ffff:100:f101::1
3ffe:ffff:100:f101::1 ff0e::1:2:3 ff0e::1:2:4 64000 0
setting up sender socket with address /3ffe:ffff:100:f101:0:0:0:1
setting up good receiver socket with address /ff0e:0:0:0:0:1:2:3
binding mcast socket to port:64000
java.net.SocketException: Invalid argument
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
at
org.jboss.test.cluster.test.PromiscuousTrafficTester$MulticastReceiver.<init>(PromiscuousTrafficTester.java:222)
at
org.jboss.test.cluster.test.PromiscuousTrafficTester.setUpSockets(PromiscuousTrafficTester.java:144)
at
org.jboss.test.cluster.test.PromiscuousTrafficTester.<init>(PromiscuousTrafficTester.java:67)
at
org.jboss.test.cluster.test.PromiscuousTrafficTester.main(PromiscuousTrafficTester.java:191)
Promiscuous traffic does occur if we bind to multicast port only:
$ java -jar promiscuoustraffic.jar 3ffe:ffff:100:f101::1 3ffe:ffff:100:f101::1 ff0e::1:2:3
ff0e::1:2:4 64000 0setting up sender socket with address /3ffe:ffff:100:f101:0:0:0:1
setting up good receiver socket with address /ff0e:0:0:0:0:1:2:3
binding mcast socket to port:64000
setting up bad receiver socket with address /ff0e:0:0:0:0:1:2:4
binding mcast socket to port:64000
Listening on address /ff0e:0:0:0:0:1:2:3
Listening on address /ff0e:0:0:0:0:1:2:4
Sending 'Hello' on /ff0e:0:0:0:0:1:2:3:64000
/ff0e:0:0:0:0:1:2:4:64000 -- Received Hello
/ff0e:0:0:0:0:1:2:3:64000 -- Received Hello
Bad news. Detected the Promiscuous Traffic problem. Received Hello on undesired address
/ff0e:0:0:0:0:1:2:4
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
11:16 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
May want to change the error message to:
16:35:20,231 WARN [UDP] could not bind to /ff02:0:0:0:0:1:2:3 (IPv6 address); make sure
your mcast_addr is of the same type as the IP stack (IPv4 or IPv6), by checking the value
of the system property java.net.preferIPv4Stack. Will ignore mcast_addr, but this may lead
to cross talking (see http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking for details).
Exception was: java.net.SocketException: Invalid argument
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
11:16 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
The confusing error message which is generated when we try to bind to IPv6 multicast
address is:
16:35:19,970 INFO [DefaultPartition] Initializing partition DefaultPartition
16:35:20,231 WARN [UDP] could not bind to /ff02:0:0:0:0:1:2:3 (IPv6 address); make sure
your mcast_addr is of the same type as the IP stack (IPv4 or IPv6).
Will ignore mcast_addr, but this may lead to cross talking (see
http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking for details).
Exception was: java.net.SocketException: Invalid argument
16:35:20,289 INFO [STDOUT]
---------------------------------------------------------
GMS: address is fe80:0:0:0:215:17ff:fe2d:6821:44270 (cluster=DefaultPartition)
---------------------------------------------------------
It turns out that this message is confusing, but entirely accurate. This exception occurs
when three conditions are present:
(i) we pass an IPv6 multicast address
(ii) we try to bind to the multicast socket formed from multicast address and multicast
port
(iii) we prefer the IPv4 stack using java.net.preferIPv4Stack=true
After the exception
java.net.SocketException: Invalid argument (i.e. you're trying to bind
an IPv6 mcast address to an IPv4 stack)
the code will then try to bind only to the multicast port and it is indeed the case that
when we bind to the multicast port only in IPv6, we do get crosstalk.
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
11:49 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
On Brian's suggestion, changed to:
16:35:20,231 WARN [UDP] could not bind to /ff02:0:0:0:0:1:2:3 (IPv6 address); make sure
your mcast_addr is of the same type as the preferred IP stack (IPv4 or IPv6), by checking
the value of the system properties java.net.preferIPv4Stack and
java.net.preferIPv6Addresses. Will ignore mcast_addr, but this may lead to cross talking
(see http://www.jboss.com/wiki/Edit.jsp?page=CrossTalking for details). Exception was:
java.net.SocketException: Invalid argument
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
11:51 a.m.
New subject: [JBoss JIRA] Closed: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz closed JGRP-956.
------------------------------------
Fix Version/s: 2.4.7
2.6.11
Resolution: Done
Changed error message in 2.6.11 - need to change for Branch 2.4 and Branch 2.8
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.4.7, 2.6.11, 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
10:19 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
There is another error message which can arise in this multicast binding situation.
When we try to bind to a IPv4 multicast address using an IPv6 stack, we get the following
exception:
java.net.BindException: Cannot assign requested address
It appears that binding to an IPv4 multicast address using an IPv6 stack is outlwaed.
Binding to an IPv6 multicast address using an IPv6 stack works fine as described above.
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.4.7, 2.6.11, 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
2:18 p.m.
New subject: [JBoss JIRA] Commented: (JGRP-956) Binding to mcast address in UDP.java is not working on Linux with IPv6
[
https://jira.jboss.org/jira/browse/JGRP-956?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-956:
------------------------------------------
Updated Branch_2_4 and HEAD (JGroups 2.8).
Binding to mcast address in UDP.java is not working on Linux with
IPv6
----------------------------------------------------------------------
Key: JGRP-956
URL: https://jira.jboss.org/jira/browse/JGRP-956
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 2.4.7, 2.6.11, 2.8
On Linux and Solaris platforms, when setting up the main multicast receiver socket, Bela
allows binding the socket to its multicast address, like this:
InetAddress group_addr = ...
InetAddress bind_addr = ...
SocketAddress group_sock_addr = new InetSocketAddress(group_addr, port) ;
MulticastSocket s = new MulticastSocket(group_sock_addr) ; // funny
s.joinGroup(group_addr) ;
Binding to the multicast address on Linux and Solaris was done in order to avoid the
promiscuous traffic problem. A detailed discussion on the matter can be found in the
bugzilla report:https://bugzilla.redhat.com/show_bug.cgi?id=231899.
This works on Linux with IPv4 but is not working on Linux with IPv6 for the
multicast-address ff02::1 - an error message is being generated (SocketException, invalid
argument) and the code then tries to create the same multicast address in the usual way:
InetAddress group_addr = ...
InetAddress bind_addr = ...
MulticastSocket s = new MulticastSocket(port) ;
s.setInterface(bind_addr) ;
s.joinGroup(group_addr) ;
This is only a problem in that it generates a confusing error message about using mixed
IPv4 / IPv6 stacks, but the socket continues to work correctly as far as I can tell.
Haven't confirmed this, but I believe the promiscuous traffic issue does not arise
with IPv6 multicast sockets.
--
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
6160
days inactive
6314
days old
11 comments
2 participants
participants (2)
-
Bela Ban (JIRA) -
Richard Achmatowicz (JIRA)