RFR: JDK-6458027 - Disabling IPv6 on a specific network interface causes problems
Chris Hegarty
chris.hegarty at oracle.com
Mon Sep 16 05:53:50 PDT 2013
On 16/09/2013 12:11, Michael McMahon wrote:
> ...
> yep. Forget that as well. I thought it was being called from common
> code. So, I'm missing how this
> code is relevant then on Vista, which should be using the dual stack
> implementation then ?
Multicasting on Windows still uses the two stack implementation :-(
http://hg.openjdk.java.net/jdk8/tl/jdk/file/tip//src/windows/classes/java/net/DefaultDatagramSocketImplFactory.java#129
-Chris.
>
> Michael
>
>
>> -Chris.
>>
>>>
>>> Michael
>>>
>>>
>>>
>>> On 15/09/13 12:34, Mark Sheppard wrote:
>>>> Hi
>>>> please oblige and review the webrev below which addresses the issue
>>>>
>>>> problem:
>>>> https://bugs.openjdk.java.net/browse/JDK-6458027
>>>>
>>>> webrev:
>>>> http://cr.openjdk.java.net/~msheppar/6458027/webrev/
>>>>
>>>> the core of the issue is that a windows platform may be IPv6
>>>> enabled, but
>>>> an individual adapter/interface may not be configured with for IPv6.
>>>> This causes a problem with the MulticastSocket.setNetworkInterface()
>>>> and MulticastSocket.getNetworkInterface() methods.
>>>>
>>>> The solution focuses on adding and additional check on the
>>>> individual interface for IPV6 enabling.
>>>>
>>>> The fallback position when an adapter is not configured for IPV6, is to
>>>> handled it as IPV4, only.
>>>>
>>>> It should be noted that setting an Interface which does not have a
>>>> valid IP address bound to it will result in a SocketException. As
>>>> such, i
>>>> the onus in on the application to supply a validly configured
>>>> NetworkInterface object to the MulticastSocket.setNetworkInterface().
>>>>
>>>> With this in mind, the set of Interfaces constructed for the
>>>> associated test
>>>> is based on the interface being up, multicast, and valid IP address
>>>> configured.
>>>>
>>>> regards
>>>> Mark
>>>
>
More information about the net-dev
mailing list