[JBoss JIRA] Created: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
2:50 p.m.
Bind multicast send socket to specific IP when using IPv6 and NIC aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to filter
the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Bela Ban updated JGRP-1207:
---------------------------
Fix Version/s: 2.10
I'll take a look in 2.10, might backport to the 2.4 branch
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:14 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Bela Ban commented on JGRP-1207:
--------------------------------
{Email Dennis]
The fix that works for this customer is bind()'ing the multicast socket on creation to
the correct IP, instead of relying on setInterface.
Do you think that will cause issues on any other OS's?
That's easy enough on 2.4.x. But on 2.6.x and above, I think the separate
send/receive sockets would need to be restored, so receive can bind to the multicast IP
and send can bind to the bind_addr. Do you agree?
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 p.m.
New subject: [JBoss JIRA] Commented: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Dennis Reed commented on JGRP-1207:
-----------------------------------
Fixed for 2.4.x branch.
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Bela Ban commented on JGRP-1207:
--------------------------------
IMO, IPv6 should use the IP address passed to it in MulticastSocket.setInterface() as
*source* address. If it doesn't do that, then I suggest we talk to our IP gurus to see
why not !
MulticastSocket.setInterface() sets the interface, but as I understand it, the kernel can
pick any address on that interface.
I cannot use the MulticastSocket() constructor taking a SocketAddress and pass in the bind
address, as we pass in the multicast address to prevent promiscuous traffic ! e.g. new
MulticastSocket(new InetSocketAddress("224.5.6.7", 7500)); Check
Util.createMulticastSocket() for details. BTW: there's a bunch of JIRAs on this.
I suggest you write a simple program which creates a MulticastSocket as described above,
and calls setInterface() with an IPv6 address. Then we create a couple of aliases on the
same interface as the IP address and observe that the src address is different every
time.
Someone from Red Hat (preferably Neil Horman) should take a look...
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:03 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Dennis Reed commented on JGRP-1207:
-----------------------------------
The issue is caused by the design of the IPv6 system call API (ioctl IP_MULTICAST_IF or
IPV6_MULTICAST_IF options).
For IPv4, it takes an IP address. The IPv6 version only takes the index of a NIC (no way
to specify an IP here if the NIC has multiple).
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/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-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Bela Ban commented on JGRP-1207:
--------------------------------
what do you want me to do then ?
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:05 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Dennis Reed commented on JGRP-1207:
-----------------------------------
The only idea I've come up with so far to solve it is to go back to the separate
send/receive sockets so they can bind to different IPs.
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 a.m.
New subject: [JBoss JIRA] Resolved: (JGRP-1207) Bind multicast send socket to specific IP when using IPv6 and NIC aliases
[
https://jira.jboss.org/browse/JGRP-1207?page=com.atlassian.jira.plugin.sy...
]
Bela Ban resolved JGRP-1207.
----------------------------
Resolution: Rejected
Bind multicast send socket to specific IP when using IPv6 and NIC
aliases
-------------------------------------------------------------------------
Key: JGRP-1207
URL: https://jira.jboss.org/browse/JGRP-1207
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4.8
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 2.10
The OS-level API calls used to bind a multicast socket to a network interface are
different when java.net.preferIPv4Stack is on or off.
With preferIPv4Stack on, MulticastSocket.setInterface sets the source IP on outgoing
multicast messages (IP_MULTICAST_IF ioctl option).
With preferIPv4Stack off, it only sets the outgoing interface (a NIC index instead of an
IP) (IPV6_MULTICAST_IF ioctl option).
This becomes an issue when there are multiple aliases for the same NIC, because the OS
decides which one of the IPs to set as the source.
This doesn't break anything in JGroups, but makes it difficult for firewalls to
filter the packets.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5850
days inactive
5863
days old
8 comments
2 participants
participants (2)
-
Bela Ban (JIRA) -
Dennis Reed (JIRA)