[
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