1 edit
1 recommendation |
RightHere
Premium Member
2014-Oct-10 10:15 pm
[IPv6] IPv6 Problems with routers other than NetgearWell aware of the current thread for IPv6 issues on Netgear routers. Starting a new one since my problem isn't happening on netgear.
I replaced my WNDR3700v1 with a Tmobile TM-AC1900 (rebadged ASUS RT-AC68U). After a short period of time (a couple of days), it stops working.
Comcast - If we are experiencing this problem with a NON-Netgear router, what can we do to help you investigate further? Are there some sorts of traces that we can provide? |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL
1 recommendation |
NetDog
Premium Member
2014-Oct-10 10:56 pm
Re: [IPv6] Problems with routers other than NetgearDetails would be nice.. What is the problem? |
|
iNick Premium Member join:2012-12-11 Joliet, IL
1 recommendation |
to RightHere
said by RightHere:Well aware of the current thread for IPv6 issues on Netgear routers. Starting a new one since my problem isn't happening on netgear.
I replaced my WNDR3700v1 with a Tmobile TM-AC1900 (rebadged ASUS RT-AC68U). After a short period of time (a couple of days), it stops working.
Comcast - If we are experiencing this problem with a NON-Netgear router, what can we do to help you investigate further? Are there some sorts of traces that we can provide? I have the same router, How do you get IPv6 Working on this Router? I don't remember how I did it on my old N750 Netgear router. |
|
2 recommendations |
to RightHere
Here's how I have it setup. IPv6 has been working well from what I can tell. What problems are you experiencing? |
|
1 recommendation |
to NetDog
Ugh, I suck.
The problem is very similar to what I and others observed on the Netgear device. I can get an IPv6 address, it's working fine for a short period of time (days), and then it stops working.
The normal way I notice this is by trying to run the Comcast speedtest. If I have an IPv6 connection, I'll get a map of the whole country when I launch the page (then when I click on a server, my IPv6 address is displayed on the screen). If I have an IPv4 connection, I'll get a map that shows just the Northwest region. After that, I'll try going to the Comcast test-ipv6 site, and I verify that the ipv6 tests fail. |
|
RightHere
1 recommendation |
to CCNnorthcali
» test-ipv6.comcast.net/Do those tests all pass for you? |
|
owlyn MVM join:2004-06-05 Newtown, PA Netgear CM2050V Netgear RBRE960 Netgear RBSE960
1 recommendation |
to RightHere
I have the RT-AC66, which is very similar to yours. I use the Merlin firmware. Once I get IPV6 working, it stays. There is a bit of a trick to get it to work, and even then it may be just my configuration, as I have not seen other reports. Anyway, try it out, and if you have IPV6 problems, let me know, and I'll post my instructions to get it to work. Only takes about a minute to implement. |
|
cp Premium Member join:2004-05-14 Wheaton, IL
2 recommendations |
cp
Premium Member
2014-Oct-11 11:14 am
Having similar issues with my RT-N66U. IPv6 will work fine for a week or so, then IPv6 addresses will disappear from all of my devices. Takes a power cycle to bring it back to life. I figured it was just a quirk with RT-N66U since I didn't have any issues like this with my home brew router. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 edit
1 recommendation |
to RightHere
Does that test pass for you? If not, what OS are you using for the test? If I test at » test-ipv6.comcast.net/ on an openSUSE PC it fails, but if I test at » test-ipv6.com/ it passes with no problems (my results shown below):
If you test at both sites and post the results here (and perhaps also post your router's IPv6 config), that might provide a clue for your problem that someone might recognize.
|
|
grod46 join:2012-11-25 Fresno, CA
2 recommendations |
to RightHere
I have the Exact same T-Mobile ASUS AC router and i get the same problem, i would get a V6 address for a short period of time then it will just stop working, using the router with a SB6141 with the .14 software |
|
1 recommendation |
I'm glad to see that I'm not alone! |
|
owlyn MVM join:2004-06-05 Newtown, PA
1 recommendation |
owlyn to cp
MVM
2014-Oct-11 2:47 pm
to cp
Once I get ipv6 working, it stays. We've had power failures, and that's when I have the problem, but I know how to fix it. |
|
3 edits
2 recommendations |
to RightHere
CCNnorthcali I also have Comcast and when I first powered up my Tmobile router and turned on the ipV6 I wound up with a different configuration than you. I have everything the same as you except on the the line where it says ipV6 Lan Settings/ Autoconfig/stateful or stateless mine says stateful and has a lot of information in that box. I didn't fill it in it just happened that way. I have had a constant ipV6 address for over 2 weeks with no problem. I have an Arris eMTA and when I received the Tmobile router I shut down my whole network, booted the eMTA then the router and then my computer. At this point the ipV6 wasn't working so I rebooted the router again and then I noticed all the statefull information was filled in and I haven't lost ipV6 in over 2 weeks. That's when I first got the Tmobile router. I really like that router. Price was right too. |
|
|
RightHere
Premium Member
2014-Oct-23 10:42 pm
Re: [IPv6] IPv6 Problems with routers other than NetgearAnything we can do to help Comcast troubleshoot further? |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL
1 recommendation |
NetDog
Premium Member
2014-Oct-23 10:55 pm
said by RightHere:Anything we can do to help Comcast troubleshoot further? I would be the one that would look into it on the Comcast side. Been watching in the back ground a little. So your losing v6 on the ASUS router as well? With the latest code? |
|
1 recommendation |
RightHere
Premium Member
2014-Oct-23 11:56 pm
SB6120 SB_KOMODO-1.0.6.14-SCM01-SH TM-AC1900 3.0.0.4.376_2827 Windows 8.1 x64 with all of the latest updates Intel NUC D54250WYK with latest drivers
The ipv6 page on the router currently displays the same info as in CCNnorthcali's screenshot above.
When I try to go to test-ipv6.comcast.net, it reports that I have no IPv6 address. The symptom I described above re: the speedtest also exists.
This config works for a while, and then stops. |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL |
NetDog
Premium Member
2014-Oct-24 1:28 am
Check your ipconfig, does it show a global v6 address? can you traceroute to google.com via v6? |
|
iNick Premium Member join:2012-12-11 Joliet, IL |
to RightHere
I have the same problem as you do with the same router from T-Mobile |
|
owlyn MVM join:2004-06-05 Newtown, PA Netgear CM2050V Netgear RBRE960 Netgear RBSE960
1 recommendation |
to NetDog
I don't lose IPv6 unless I need to reboot the router or the modem. When that happens, the only repeatable way to regain IPv6 is to plug the computer directly into the modem, bypassing the router. After doing that, I plug the modem back into the router, and the router instantly obtains IPv6, and retains it. There was only one time I lost IPv6 without rebooting the modem or the router, and that may have been due to a Comcast outage on my street. This is an ASUS RT-AC66, running the latest Merlin firmware. Ubee modem: DVM3203B, Download Revision: dvm3203b_7.20.3105.cdf.csg, Software Version: 7.20.3105 |
|
1 edit |
to NetDog
This is the non-working case. Will post a working case later. C:\Windows\system32>tracert -6 google.com
Unable to resolve target system name google.com.
C:\Windows\system32>ipconfig /all
Ethernet adapter vEthernet (Intel(R) Ethernet Connection I218-V Virtual Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : <deleted>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8488:<deleted>(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.29.168(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2014 7:22:44 PM
Lease Expires . . . . . . . . . . : Saturday, October 25, 2014 4:24:00 AM
Default Gateway . . . . . . . . . : 192.168.29.1
DHCP Server . . . . . . . . . . . : 192.168.29.1
DHCPv6 IAID . . . . . . . . . . . : 146816981
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-83-D8<deleted>
DNS Servers . . . . . . . . . . . : 192.168.29.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Internal Ethernet Port Windows Phone Emulator Intern
al Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
Physical Address. . . . . . . . . : <deleted>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d07f:<deleted>(Preferred)
IPv4 Address. . . . . . . . . . . : 169.254.80.80(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : :<deleted>
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-83-D8-:<deleted>
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
From System Log -> IPv6 page on Router
IPv6 Connection Type: Native with DHCP-PD
WAN IPv6 Address: 2601:8:9c00:<deleted>
WAN IPv6 Gateway: fe80::21b:d5ff:<deleted>
LAN IPv6 Address: 2601:8:9c00:<deleted>:ea48/64
LAN IPv6 Link-Local Address: fe80::7a24:<deleted>:ea48/64
DHCP-PD: Enabled
LAN IPv6 Prefix: 2601:8:<deleted>::/64
DNS Address: 2001:558:feed::1 2001:558:feed::2
IPv6 LAN Devices List
-------------------------------------------------------------------
Hostname MAC Address IPv6 Address
Edit: Working case C:\Windows\system32>tracert -6 www.google.com
Tracing route to www.google.com [2607:f8b0:4001:c01::69]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms TM-AC1900-EA48 [2601:8:9c00:<deleted>]
2 10 ms 10 ms 9 ms 2001:558:<deleted>
3 11 ms 10 ms 9 ms te-0-2-0-4-sur03.bellevue.wa.seattle.comcast.net
[2001:558:a2:7f::1]
4 12 ms 12 ms 11 ms 2001:558:a0:f6c3::2
5 13 ms 15 ms 14 ms he-1-3-0-0-10-cr01.seattle.wa.ibone.comcast.net
[2001:558:0:f769::1]
6 12 ms 11 ms 12 ms be-11-pe03.56marietta.ga.ibone.comcast.net [2001
:558:0:f8b9::2]
7 13 ms 11 ms 12 ms 2001:559::962
8 19 ms 12 ms 12 ms 2001:4860::1:0:610
9 12 ms 12 ms 12 ms 2001:4860::8:0:6999
10 38 ms 38 ms 38 ms 2001:4860::8:0:79e5
11 47 ms 48 ms 48 ms 2001:4860::8:0:4cde
12 48 ms 49 ms 48 ms 2001:4860::2:0:59ad
13 * * * Request timed out.
14 48 ms 47 ms 47 ms 2607:f8b0:4001:c01::69
Trace complete.
C:\Windows\system32>
Ethernet adapter vEthernet (Internal Ethernet Port Windows Phone Emulator Intern
al Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
Physical Address. . . . . . . . . : <deleted>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d07f:<deleted>(Preferred)
IPv4 Address. . . . . . . . . . . : 169.254.80.80(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : <deleted>
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-83-D8-<deleted>
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Intel(R) Ethernet Connection I218-V Virtual Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : <deleted>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:8:9c00:<deleted>(Preferred)
Temporary IPv6 Address. . . . . . : 2601:8:9c00:<deleted>(Preferred)
Link-local IPv6 Address . . . . . : fe80::8488:fedb:<deleted>(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.29.168(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, October 14, 2014 7:22:44 PM
Lease Expires . . . . . . . . . . : Sunday, October 26, 2014 5:24:28 AM
Default Gateway . . . . . . . . . : fe80::7a24:afff:<deleted>
192.168.29.1
DHCP Server . . . . . . . . . . . : 192.168.29.1
DHCPv6 IAID . . . . . . . . . . . : <deleted>
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-83-D8-<deleted>
DNS Servers . . . . . . . . . . . : 2601:8:9c00:731:<deleted>
192.168.29.1
NetBIOS over Tcpip. . . . . . . . : Enabled
|
|
neufuse join:2006-12-06 James Creek, PA
1 recommendation |
to RightHere
I have a pfSense router set up (2.1.5-RELEASE (amd64)) and it will obtain an IPv6 /64 delegation. but after a few days the leases will just vanish also and I go right back to having no IPv6 access until I reboot it again. I already disabled gateway monitoring thinking maybe that would be it but nope |
|
NetDog Premium Member join:2002-03-04 Hollywood, FL
1 recommendation |
to RightHere
said by RightHere:From System Log -> IPv6 page on Router
IPv6 Connection Type: Native with DHCP-PD WAN IPv6 Address: 2601:8:9c00: WAN IPv6 Gateway: fe80::21b:d5ff: LAN IPv6 Address: 2601:8:9c00::ea48/64 LAN IPv6 Link-Local Address: fe80::7a24::ea48/64 DHCP-PD: Enabled LAN IPv6 Prefix: 2601:8:::/64 So it looks like your getting v6 to your router from Comcast but the router isn't assigning v6 via DHCP or SLAAC to the OS's behind it.. |
|
NetDog
1 recommendation |
to neufuse
said by neufuse:but after a few days the leases will just vanish also and I go right back to having no IPv6 access until I reboot it again. Anyway to stop and restart the DHCPv6 process without rebooting it? |
|
mikev Premium Member join:2002-05-04 Leesburg, VA
1 recommendation |
to neufuse
You might try just release/renew the WAN interface on the Status > Interfaces page and see if that at least removes the need to reboot. |
|
tshirt Premium Member join:2004-07-11 Snohomish, WA
1 recommendation |
to neufuse
I'm also seeing something similar at the 2nd lease renewal with with a 6120 and a DIR-655 ver.B-1 the router still sees the IPv6 address but the rest of the network stops using it, assorted windows desk and laptops, sony TV, android phones and tablet ALL exihibit the same behavior. So I assume the lease renews on v4 and sometimes v6.
On the DIR-655 I can go to the v4 page /release, switch QUICKLY to the v6 page release and renew, and return to the v4 to renew that and it fixes the problem MOST of the time, Occasional full power cycle required. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
NetFixer
Premium Member
2014-Oct-24 4:11 pm
said by tshirt:I'm also seeing something similar at the 2nd lease renewal with with a 6120 and a DIR-655 ver.B-1 the router still sees the IPv6 address but the rest of the network stops using it, assorted windows desk and laptops, sony TV, android phones and tablet ALL exihibit the same behavior. So I assume the lease renews on v4 and sometimes v6.
On the DIR-655 I can go to the v4 page /release, switch QUICKLY to the v6 page release and renew, and return to the v4 to renew that and it fixes the problem MOST of the time, Occasional full power cycle required. I used to occasionally see that symptom on my DIR655, but all I had to do was to release/renew the IPv6 lease to wake everything up again. However, I have not seen that symptom in a very long time since I implemented an IPv6 keep-alive script file on my Windows server (I chose that PC because it is always up). Here is the code for my IPv6-KeepAlive.cmd file: :start
ping -6 www.comcast.net
D:\apps\reskit\sleep 120
ping -6 my.yahoo.com
D:\apps\reskit\sleep 120
ping ipv6.google.com
D:\apps\reskit\sleep 120
goto start
I decided to implement the IPv6 keep-alive script after noticing that the IPv6 loss seemed to occur during idle periods when little (if any) IPv6 traffic was present on my network. And because based on the contents of the syslog daemon that I use to capture log entries from all of my routers, it did not consistently seem to happen after a DHCP lease renewal on the router (unlike my semi-retired Netgear WNR1000v2-VC guest router). |
|
tshirt Premium Member join:2004-07-11 Snohomish, WA 1 edit
1 recommendation |
tshirt
Premium Member
2014-Oct-24 4:33 pm
So running it on one device keeps it working for all? That would jibe with one experiment I tried>> an ipconfig / renew that worked twice (I think) but I've been unable to repeat reliably. As it remember their is a timer on v4/v6 DHCP if one responds and the other doesn't within 3 (???)seconds it is ignored I could guess the occasionly "pauses"/ timeouts some people are having problem with is waiting for the server to respond, though mine is timed at the second renewal (end of first lease) so maybe the renewal is actual lost earlier or not passed through promptly enough? |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
NetFixer
Premium Member
2014-Oct-24 6:03 pm
said by tshirt: So running it on one device keeps it working for all? That would jibe with one experiment I tried>> an ipconfig / renew that worked twice (I think) but I've been unable to repeat reliably. As it remember their is a timer on v4/v6 DHCP if one responds and the other doesn't within 3 (???)seconds it is ignored I could guess the occasionly "pauses"/ timeouts some people are having problem with is waiting for the server to respond, though mine is timed at the second renewal (end of first lease) so maybe the renewal is actual lost earlier or not passed through promptly enough? The only IPv6 problems I have had with my DIR655 did not seem to be related at all to DHCPv4 or DHCPv6 lease renewals (at least not that I could confirm by looking at the router logs). What I used to occasionally see was that both the router and its clients all reported that they had valid IPv6 addresses, but there was no actual IPv6 throughput between the router's LAN and WAN interfaces (IPv6 traceroutes to the Internet from a PC would stop at the router's LAN interface). When I would see this, I would also notice that the router's IPv6 status page would show no attached IPv6 devices (I could however ping IPv6 sites on the Internet from within the router's System Check page). It appeared that the router had simply started to ignore LAN IPv6 traffic. After simply doing a release/renew on the router's IPv6 status page, LAN traffic would once again start working -- there would be no change in the PD prefix, but the router's WAN interface (as I recall) would (sometimes, but not always) get a different IPv6 address. I have not seen that symptom since I implemented the IPv6 keep-alive script. I started doing that several DIR655 firmware revs back, but I have continued doing it because even if it may no longer be required, it doesn't hurt anything (and if I open the associated window to see the ping activity, it does provide a warm fuzzy feeling that IPv6 is still alive). I do occasionally see IPv6 glitches (which usually involve the router itself losing IPv6 connectivity), but they are always a result of either me mucking around with the router settings and/or the Ethernet cables, or Comcast mucking around in the CMTS. |
|
tshirt Premium Member join:2004-07-11 Snohomish, WA
1 recommendation |
tshirt
Premium Member
2014-Oct-24 6:16 pm
Your former problem sounds similar enough, Could I get you to temporarily disable the script to see if it returns, and I'll add the scripted to one computer that is almost always on, to see if it helps. |
|
NetFixerFrom My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU
1 recommendation |
NetFixer
Premium Member
2014-Oct-24 6:31 pm
said by tshirt:Your former problem sounds similar enough, Could I get you to temporarily disable the script to see if it returns, and I'll add the scripted to one computer that is almost always on, to see if it helps. In my case, I doubt that stopping the IPv6 keep-alive script would make any difference because I am now also running a DynDNS IPv6 DDNS client on that server, and on several PCs. Those DDNS clients frequently poll » checkipv6.dyndns.org/ to get the current Internet visible IPv6 address and to verify IPv6 connectivity. |
|