jkj860The Final Frontier join:2002-01-10 Valparaiso, IN |
jkj860
Member
2013-Jan-23 7:35 pm
[IPv6] IPv6 and Netgear WNDR 3700-100NAS issuesWhen I run the test it always fails. I have a sb6121 and a Netgear WNDR3700v3 router with stock firmware. The modem says IPv4 only but in the routers IPv6 tab I show this. Router's IPv6 Address On WAN 2001:............./64 Router's IPv6 Address On LAN 2601:............./64 Internet connection type is set to DHCP and IP address assignment is set to Auto config. |
|
|
owlyn MVM join:2004-06-05 Newtown, PA |
owlyn
MVM
2013-Jan-23 7:59 pm
Set the Internet Connection Type to Auto Detect. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
to jkj860
said by jkj860:When I run the test it always fails. I have a sb6121 and a Netgear WNDR3700v3 router with stock firmware. The modem says IPv4 only but in the routers IPv6 tab I show this. Router's IPv6 Address On WAN 2001:............./64 Router's IPv6 Address On LAN 2601:............./64 Internet connection type is set to DHCP and IP address assignment is set to Auto config. It sounds is if your router is properly getting the IPv6 information from Comcast and is properly setting up its LAN. What OS are you running on your PC(s)? If Windows, open a command prompt and post the results of "ipconfig /all" and "netsh int ipv6 show addr" commands. If it is *nix based, try opening up a terminal window and post the results of "ifconfig" or "ip addr" commands. Assuming that you do have IPv6 configured and active on at least one PC, can you ping the 2601:xx:xx:xx:xx LAN IP address of the router? If you do a ping to an IPv6 Internet site (such as ipv6.speedtest.comcast.net) do you see a response from the router's LAN interface? Actually posting the results of the ping and traceroute tests would be helpful, and just for good faith, here are my results for all of the above from the Windows XP workstation I am currently using:
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : rws-wks
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dcs-net
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : dcs-net
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Physical Address. . . . . . . . . : E0-91-F5-95-B6-9D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.9.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2601:5:c80:90:20f5:ccf:8074:c30c
IP Address. . . . . . . . . . . . : 2601:5:c80:90:e291:f5ff:fe95:b69d
IP Address. . . . . . . . . . . . : fe80::e291:f5ff:fe95:b69d%4
Default Gateway . . . . . . . . . : 192.168.9.254
fe80::1e7e:e5ff:fe4c:e6ff%4
DHCP Server . . . . . . . . . . . : 192.168.9.254
DNS Servers . . . . . . . . . . . : 192.168.9.2
75.75.75.75
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Monday, January 21, 2013 18:33:04
Lease Expires . . . . . . . . . . : Monday, January 28, 2013 18:33:04
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . : dcs-net
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-09-64
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.9.100%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
C:\>netsh int ipv6 show addr
Querying active state...
Interface 5: Teredo Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::ffff:ffff:fffd
Interface 4: Local Area Connection 2
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Temporary Preferred 23h37m8s 20h6m39s 2601:5:c80:90:20f5:ccf:8074:c30c
Public Preferred 23h37m8s 23h37m8s 2601:5:c80:90:e291:f5ff:fe95:b69d
Link Preferred infinite infinite fe80::e291:f5ff:fe95:b69d
Interface 2: Automatic Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::5efe:192.168.9.100
Interface 1: Loopback Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Loopback Preferred infinite infinite ::1
Link Preferred infinite infinite fe80::1
C:\>tracert ipv6.speedtest.comcast.net
Tracing route to ipv6.speedtest.g.comcast.net [2001:558:1030:8:69:252:23:68]
over a maximum of 30 hops:
1 5 ms <1 ms <1 ms 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff
2 * 35 ms 29 ms 2001:558:4013:19::1
3 10 ms 24 ms 9 ms 2001:558:162:32::1
4 10 ms 10 ms 12 ms xe-2-0-10-0-ar03.nashville.tn.nash.comcast.net [2001:558:160:94::1]
5 41 ms 23 ms 24 ms pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f76f::1]
6 36 ms 34 ms 35 ms pos-0-11-0-0-ar01.roseville.mn.minn.comcast.net [2001:558:0:f707::2]
7 54 ms 52 ms 52 ms te-0-0-0-4-ar01.crosstown.mn.minn.comcast.net [2001:558:30:75::1]
8 49 ms 47 ms 48 ms te-2-1-ur02.roseville.mn.minn.comcast.net [2001:558:30:16::2]
9 48 ms 50 ms 49 ms 2001:558:1030:8:69:252:23:68
Trace complete.
C:\>ping 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff
Pinging 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff with 32 bytes of data:
Reply from 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff: time<1ms
Reply from 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff: time<1ms
Reply from 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff: time<1ms
Reply from 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff: time<1ms
Ping statistics for 2601:5:c80:90:1e7e:e5ff:fe4c:e6ff:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
And FWIW, my SB6121 shows as IPv4 too, but that is only for the management interface and has nothing to do with payload traffic (if it did, your router would not be getting IPv6 information). |
|
jkj860The Final Frontier join:2002-01-10 Valparaiso, IN |
jkj860
Member
2013-Jan-23 11:35 pm
>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : homeoffice-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.0) Physical Address. . . . . . . . . : 00-........-BD DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.1.16(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, January 22, 2013 1:27:07 AM Lease Expires . . . . . . . . . . : Thursday, January 24, 2013 1:27:10 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : Enable |
|
jkj860 |
to NetFixer
C:\Users\home office>netsh int ipv6 show addr
Interface 1: Loopback Pseudo-Interface 1
Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite ::1
C:\Users\home office>
|
|
jkj860 |
to NetFixer
Oops...double post. |
|
owlyn MVM join:2004-06-05 Newtown, PA |
to jkj860
My suggestion above takes about 10 seconds and should work. Worked on my Netgear router, where, like yours, setting it to DHCP didn't work. Don't know why you haven't tried it. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
|
to jkj860
Are you sure that you have the MS TCPIP6 protocol stack installed and enabled for that NIC? As a test, I just disabled IPv6 in my Netgear WNR1000v2-VC guest router, and connected my notebook to it. Shown below is the NIC properties screen showing that the MS TCPIP6 protocol is installed and enabled, and also what I get for the "ipconfig /all" command under those conditions:
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : RWS-6325
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.18
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::21a:73ff:fe67:2cdc%9
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:31:48
Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:31:48
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-0A-12
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.10.18%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
Please note from the above, that the NIC still gets a link-local IPv6 address [fe80::21a:73ff:fe67:2cdc%9] even with no IPv6 enabled in the router. Also the pseudo IPv6 tunnels are still showing (but they do not appear in your post). Next, I disabled the MS TCPIP6 protocol for that NIC and reconnected it to the Netgear router. Shown below is the NIC properties screen showing that the MS TCPIP6 protocol is installed and disabled, and also what I get for the "ipconfig /all" command under those conditions:
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : RWS-6325
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.18
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:36:03
Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:36:03
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-0A-12
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.10.18%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled
Please note from the above, that the NIC no longer gets a link-local IPv6 address, but the pseudo IPv6 tunnels are still showing (but they do not appear in your post). The only way I could duplicate the "ipconfig /all" results you posted was to uninstall the MS TCPIP6 protocol stack as shown below.
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : RWS-6325
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-1A-73-67-2C-DC
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.18
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Thursday, January 24, 2013 07:44:32
Lease Expires . . . . . . . . . . : Friday, January 25, 2013 07:44:32
|
|
jkj860The Final Frontier join:2002-01-10 Valparaiso, IN |
jkj860
Member
2013-Jan-24 9:28 am
|
|
jkj860 |
to owlyn
said by owlyn:Set the Internet Connection Type to Auto Detect. I tried that. Thats how I have it set now but it still fails on the test. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
|
to jkj860
Well, since you do seem to have the MS TCPIP6 protocol installed and enabled, I have no definite explanation for why you are not at least seeing a link local [fe00::xx:xx:xx:xx] IPv6 address for that NIC. I don't think that you have a chance for getting IPv6 connectivity until you get that resolved.
You might start by looking at the Symantec firewall setup (look for something related to ICMPv6, since that might block even setting up basic IPv6 for the NIC). If you don't find anything in the Symantec firewall that is blocking IPv6, then uninstalling the MS TCPIP6 protocol stack, rebooting, and then reinstalling it would be the next step. |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL |
NetDog
Premium Member
2013-Jan-24 1:53 pm
said by NetFixer:Well, since you do seem to have the MS TCPIP6 protocol installed and enabled, I have no definite explanation for why you are not at least seeing a link local [fe00::xx:xx:xx:xx] IPv6 address for that NIC. I don't think that you have a chance for getting IPv6 connectivity until you get that resolved. I would agree with this.. You need to see the FE80 before IPv6 will work, it is how all the starting traffic works.. Link-local IPv6 Address . . . . . : fe80::708a:eeee:5566:1234%12 Maybe uninstall the stack and reinstall it, what OS was this on? |
|
jkj860The Final Frontier join:2002-01-10 Valparaiso, IN |
to NetFixer
Ok i will give that a try. Edit. Vista OS |
|