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. Some Windows7 machine retrieves an rfc1918 DNS server address via dhcpv4 and some ULA (fd00::xxxx:xxxx:xxxxx:xxxxx) DNS server ip address (its own router/gateway IPv6 address) via dhcpv6. Every now and then the WIndows7 machine stops being able to even ping that ULA address. All machines, the windows7 (multiple) and the router/gateway have additionally fe80::...... addresses (link local?) as well. I am now trying to figure out, why I can even ping and use those ULA fd00::xxxxxxxxxxx addresses to begin with, how they come about and where the mask (prefix, suffix and stuff) logic comes into the game here and why I can ping and make use of ULA at all, if all I see in routing tables and ip addresses is the fe80::xxxx addresses. I have a linux client on this LAN as well, some leap 42.2 box, and this machine has also only the fe80::xxxxxxxxx addresses as well assigned to itself and this machien never stopped being able to access the ULA address of that router/gateway and use it for DNS queries while at the same time windows trying to access that ULA address simply stopped working :( 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? TIA. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org