Windows 7 / IPv6 on PPP Adapter

Liviu Pislaru liviu.pislaru at rcs-rds.ro
Fri Jul 19 08:34:44 CEST 2013


since there's no opinion about this issue here's my viewpoint:
i think this isn't an RFC 5072 compliant implementation and Microsoft 
should fix that on Windows 7.
you can see the impact here on this graph:
http://www.vyncke.org/ipv6status/compare.php?metric=p&countries=ro

--
liviu.

On 07/17/13 15:55, Liviu Pislaru wrote:
> What is your opinion about Windows 7 IPv6 over PPP behaviour that i'm 
> going to describe below ?
>
> if the global IPv6 address of the PPP interface has the last 64 bits 
> different from the last 64 bits of the IPv6 Link Local address 
> (interface identifier negociated  by IPv6CP), then IPv6 is not going 
> to work on that machine.
>
> [this is working on Windows 7 & Linux ...]
>
> PPP Adapter:
> IPv6 Address: 2a02:2f0b:503f:fff::50c:9a9b
> Link Local IPv6 Address: fe80::50c:9a9b
> Default Gateway: fe80::1
>
> [...]
>
> [this is not working on Windows 7 but is working on Linux ...]
>
> PPP Adapter:
> IPv6 Address: 2a02:2f0b:503f:fff::50c:abcd
> Link Local IPv6 Address: fe80::50c:9a9b
> Default Gateway: fe80::1
>
> [...]
>
> you might end up with this config on your PC if the BNG / PPPoE server 
> is using RA with M flag (just for default route) and a DHCPv6 server 
> for IPv6 global address.
>
> is there any RFC that refers this issue ?
>
> thanks,
> liviu.
>




More information about the ipv6-ops mailing list