I’ve been having some issues getting IPv6 stateless autoconfiguration working reliably with a RB750G with 5rc6. Dont think it particular to 5rc6 as I’ve previously observed the same results on 4.13 & 4.16, but since 5rc6 is the latest IPv6 updated, thought I’d post here.
The Win7 laptop I’m testing with has all the MS privacy (Temp addr) & addr randomization nonsense turned off, and all native OS v6 tunneling disabled (teredo, 6to4, ISATAP). Also same results via wireless (external AP) or directly connected via Ethernet to RB750G.
LAN side v6 addressing on the RB750G as follow (global addr obfuscated) …
# ADDRESS INTERFACE ADVERTISE
0 G 2001:xxxx:xxxx:xxxx:20c:42ff:fe70:d61/64 ether1 Yes
3 DL fe80::20c:42ff:fe70:d61/64 ether1 No
and ND settings at default as follows …
0 interface=ether1 ra-interval=3m20s-10m ra-delay=3s mtu=unspecified reachable-time=unspecified retransmit-interval=unspecified ra-lifetime=30m hop-limit=64
advertise-mac-address=yes advertise-dns=no managed-address-configuration=no other-configuration=no
1 D prefix=2001:xxxx:xxxx:xxxx::/64 interface=ether1 on-link=yes autonomous=yes valid-lifetime=4w2d preferred-lifetime=1w
Now if I boot the RB then start the Win7 laptop, I get this …
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-24-D6-07-5F-AE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::224:d6ff:fe07:5fae%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.168.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 28 December 2010 10:33:15 PM
Lease Expires . . . . . . . . . . : 31 December 2010 10:33:15 PM
Default Gateway . . . . . . . . . : 192.168.168.1
DHCP Server . . . . . . . . . . . : 192.168.168.1
DHCPv6 IAID . . . . . . . . . . . : 218113238
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-6C-8D-98-00-24-E8-BC-7D-69
DNS Servers . . . . . . . . . . . : 192.168.168.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Note, no IPv6 global addr or default route recieved. Performing a ‘ipconfig /renew6’ does not help (with Wireshark see the Router Soliciations being sent by Win7 but RB not responding). The strange items above are the DHCPv6 entries (5rc6 doesnt support DHCPv6 yet?).
The Win7 laptop is using the RB for v4 DHCP with a static binding, maybe somehow this is where is confusion is coming from? I did find a way to force it to work, if I add ether1’s local-link IPv6 addr with ADVERTISE=Yes, Win7 immediatedly updates with the correct/desired configuration …
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-24-D6-07-5F-AE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:xxxx:xxxx:xxxx:224:d6ff:fe07:5fae(Preferred)
Link-local IPv6 Address . . . . . : fe80::224:d6ff:fe07:5fae%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.168.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 28 December 2010 10:12:19 AM
Lease Expires . . . . . . . . . . : 31 December 2010 10:17:27 PM
Default Gateway . . . . . . . . . : fe80::20c:42ff:fe70:d61%12
192.168.168.1
DHCP Server . . . . . . . . . . . : 192.168.168.1
DNS Servers . . . . . . . . . . . : 192.168.168.1
NetBIOS over Tcpip. . . . . . . . : Enabled
So my question is, has anyone else experienced such IPv6 stateless autoconfig anomolies between ROS & Win7? Are there any workarounds or is this possibly a bug (ROS or Win7)?