IPv6 multicast binding (Bugs: JDK-8210493 JDK-8215294)
Alan Bateman
Alan.Bateman at oracle.com
Thu May 2 08:25:32 UTC 2019
On 02/05/2019 08:44, Andre Naujoks wrote:
> Hello all.
>
> I just noticed, that the fix from Bug JDK-8210493 was reverted for Java
> 12. With a new bug JDK-8215294 taking over the issue.
Yes, it caused problems so had to be reverted. In addition to
JDK-8215294 there is also JDK-8216417 which we expect to set the scopeID
when binding a TCP socket to an IPv6 link-local address.
>
> Just to let you know, the issue is not linux specific (as the new bug
> states). A test on a windows machine resulted in the same behavior.
The portability recommendation in the javadoc is to bind to the wildcard
address. Yes, you might have issues on several platforms when trying to
bind to an IPv6 multicast address when the scopeID is not set.
(If I recall correctly, the original issue that Hendrik brought up here
was binding to the multicast address to avoid interference on Linux. We
thought we had that addressed with IP_MULTICAST_ALL but it turns not to
be effective with IPv6 sockets. I believe there is a patch for that or a
proposal to introduce an equivalent IPV6_MULTICAST_ALL).
-Alan.
More information about the net-dev
mailing list