Hi, By Dan's request, I just tried the ipunblock branch on my home network. Sending my feedback to the list - also by Dan's request. My home network currently uses SLAAC for IPv6 addressing and Information-Only DHCPv6 for DNS server advertisement (no RDNSS Option present in RAs). Also standard DHCPv4 for IPv4. I connected using Auto for both IPv4 and IPv6 modes, with the «Require IPv(4|6) for this connection to complete» settings both disabled. So what happens is that as soon as the DHCPv4 transaction is complete, the device is reported to be activated by the systray applet as well as in the logs, as expected. The IPv6 activation continues in the background, also as expected, however after it has finished it goes on to report that «RA-provided address no longer valid», and then «failed (reason 'ip-config-unavailable')». The device is then brought down, the transaction restarts, and after a few attempts it successfully stays activated. However, when it does, resolv.conf does *not* contain the IPv6 name servers. The symptoms of this bug is eerily similar to the one I fixed in «[PATCH v2] ip6-manager: Fix SLAAC/DHCPv6 interaction» (which is NOT applied), however in this case stateful DHCPv6 simultaneously with SLAAC, so I kind of doubt they have the same root cause. I've attached the syslog from the initial networking activation until the connection became stable, plus a PCAP of RS/RA/DHCPv6 packets in the same time period. Any ideas what is going on? (The system is F15, and the F15 NM RPM specfile was used - I only replaced the original source tarball with one containing the ipunblock branch). Best regards, -- Tore Anderson
Attachment:
ipv6-init.pcap
Description: application/pcap
Attachment:
messages.gz
Description: GNU Zip compressed data