On 12/05/2014, at 9:37 pm, Mark Foster
I can't directly simulate either case persistently... the workstation case was several days ago for me at home, and I can't for the life of me remember what the hostname was that I was having trouble with. FWIW I was on my RFC1918 IPv4 address, so it wasn't a 'public' ipv4 address on the box.
Out of interest though I looked at both the ipconfig and the netsh syntax you suggested, here it is:
Tunnel adapter Local Area Connection* 12:
Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:28d2:7f6:3f57:fdae Link-local IPv6 Address . . . . . : fe80::28d2:7f6:3f57:fdae%18 Default Gateway . . . . . . . . . : ::
I was actually looking for the whole thing, but from this I can see that Teredo thinks that your public IPv4 address is 192.168.2.81, which is obviously bogus. I’m not actually sure how it could do that, as you’re using a Microsoft hosted Teredo server, so it should be getting your public IPv4 address correctly. Perhaps you can boot the machine, and while it’s booting (until this network adapter shows an IPv6 address) get a packet capture from somewhere inline for all traffic to/from 3544/UDP? I’m curious about what exactly is happening here.
C:\Users\markf>netsh interface ipv6 show prefix Querying active state...
Precedence Label Prefix ---------- ----- -------------------------------- 50 0 ::1/128 40 1 ::/0 30 2 2002::/16 20 3 ::/96 10 4 ::ffff:0:0/96 5 5 2001::/32
This shows IPv4 having less preference than IPv6, but only if you have a non-Teredo IPv6 address. If you also have a 6to4 tunnel or native, you’ll use IPv6. This is an older version of the address selection table - is this Windows 7?
Additional factoid for the workstation instance; i'm with Snap (native v6) but my workstation has v6 disabled on both wired and wifi NIC's. To be honest I had no idea that there was a tunnel interface coming up by default, despite the physical NIC's having v6 disabled.
Yeah, that doesn’t disable the IPv6 stack.
I'm going to look into the above tomorrow including the RFC referenced, and I will also see about the Windows Server instance and its precise circumstances as they relate.
Thanks very much to those who've responded to this thread, i've learned a bit already.
-- Nathan Ward