On 2017-02-20 13:41, Per Jessen wrote:
cagsm wrote:
Hi there,
learning some IPv6 the hard way and trying to make sense of it all.
Some soho/router has dualstack ipv6 and ipv4 internet connection via some XDSL ISP. The router provides some LAN with apparently partly ipv6 LAN via dhcpv6. It offers DNS information to LAN clients via dhcpv6.
Sounds good. What does "partly" mean here?
All machines, the windows7 (multiple) and the router/gateway have additionally fe80::...... addresses (link local?) as well.
Yes, that is required.
On the linux machine, /sbin/ip -f inet6 neigh doesnt yield any entries for any fd00::.... addresses and according to my scarce knowledge about ipv6 i dont see why the ipv6 stack is even able to make use of and to know what to do with fd00:: addresses at all?
Any pointers and takers on this matter?
Any chance you could summarize the matter in 2-3 lines? If there is a Windows issue, you're probably on the wrong list, and I couldn't see any Linux problem? Your fd00 addresses are probably being dished out by the dhcpv6 server, but that is a bit odd. It ought to dish out from a real /64 network, allocated to you by your ISP.
Windows has its own system for getting IPv6 even on IPv4 networks, behind your back. https://en.wikipedia.org/wiki/Teredo_tunneling It is used for things like sharing updates, I believe. Not sure. It is not very clear. I don't have Windows running now to guess what kind of addresses it gets. Teredo has its importance in Linux/Windows networks, because it is a network beyond the control of the network admin. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))