I just want to add a comment that the reason for the problem itself is that both the IPv4 and IPv6 stacks receive a pointer to the same DNS server using both an IPv4 address and an IPv6 address.
Once I disabled IPv6 name servers in both radvd and isc-dhcp-server6 configurations and only used an IPv4 address to point to the DNS server the error disappeared from my logs. Not having IPv6 DNS servers will obviously affect IPv6-only clients. I would argue that pointing to the same DNS server using both IPv4 and IPv6 on a dualstack machine is the correct thing to do, so the message shouldn't really trigger any error. I'm not sure how the DNS server is determined to be the same, I'm assuming ARP or some identifier sent from the DNS server validates that claim. If so, the simple workaround might be to return a different identifier from the DNS server based on IPv4 or IPv6 connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996032 Title: Constant _ip6_config_add_nameserver: assertion `IN6_ARE_ADDR_EQUAL (nameserver, &nameservers[i]) == FALSE' failed messages in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/996032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
