Looking for a little help here. I have two routers, an Asus RT-N66U which runs great, IPv6 is fine on it, and it reboots with no problem with IPv6 enabled.
On the other hand, I have a new Netgear R7000 that loses its internet connection when rebooted or power-cycled only when IPv6 is enabled and in use. IPv6 itself works fine, but if the router needs to be rebooted and/or power-cycled, then when it comes back up it has no internet connection. There are two ways of getting the internet connection back when this happens, either doing a factory reset and manually reconfiguring the router, or resetting my cable modem. If IPv6 is disabled, no problems with reboots and/or power-cycling, the internet connection is never lost.
I have an Arris TM722g cable modem that is working really well, no problems with it. And, like I said, the Asus RT-N66U doesn't have this problem at all, IPv6 works very well with it.
Just wondering if anyone else has seen this problem, since Netgear says this is an unknown problem, and this is the second R7000 that I've had that shows the same problem. Which leads me to believe that I'm probably not the only person to experience it. I can work around it, but IPv6 should just work without needing to perform gymnastics *smile*.
Any help out there? Anyone else experience this problem, or a similar one?
Hey, thanks...my problem has nothing to do with expiring IP address leases. My problem is only related to power-cycling or rebooting my router with IPv6 enabled. I don't know if all Comcast users experience this, but I've had this confirmed by other Comcast users with R7000 routers, so it isn't just me *smile*.
And Comcast IPv6 worked just fine with my Asus RT-N66U for about a year with no problems, other than one or two firmware versions that screwed up IPv6 functionality, but I could always go back to a working version.
Right now I'm using DD-WRT firmware, and that's working really well for me. The lack of CTF (hw acceleration) is not a problem for me at the download speeds that we get from Comcast here in Santa Cruz (slow compared to most other areas), and IPv6 isn't implemented yet, which is okay for the time being. But DD-WRT is very fast on the R7000 for wired connections and routing, and the wireless coverage and speed is great. And the web admin interface is much better than Netgear's, as well. Highly recommended at this point!
Netgear is rumored to finally be releasing new firmware at the end of the month (February), so we'll see how that looks when and if it arrives. Until then, no complaints about DD-WRT firmware.
When rebooting these routers all with latest FW and using SW_REV: 7.6.59M.SIP.PC20 MODEL: TM722G
I also brought this up to Netgear while BETA testing these for Netgear.
The problem I see or have Is when a router is rebooted or Power cycled for any reason You no longer are able to pull A public IPV4 or IPV6 until you remove WAN cable for a few seconds then reconnect.
I first reported this to Netgear durring the WNDR4700 Beta test. They responded with some lame answer blaming too many request to comcast server.
I then reported same as above with R6300V2 in January 2013 durring it's beta test and nothing from them. Once again in Jan 2014 with another dual core FW test and still nothing.
I also contacted them again in late December 2013 when I bought a R7000 and HAD EXACT SAME problem.
This Sunday I bought a Linksys WRT1900AC guess what? No Problem with this issue. You could reboot or power cycle and be back on line with IPV4 and IPV6 with in minutes.
I've since dumped my R7000 and just yesterday returned the WRT1900ac only because of it lacking some features I was use too and now using a R6300v2 with latest FW and same problem once again.
I would suggest someone at Cable Labs and or Comcast Corperate Take Note and Light a Fire under Netgear and Or remove their products like their gateways from your supported list until such time as you both come up with a solution.
Not trying to hijack, but rather tell you the problems I have with IPV6 enabled.
I also have the R7000 with the same firmware you have. Am using a Motorola 6141 modem.
After that firmware update I still can't have IPV6 enabled for over 3 days as everything associated with the internet starts to degrade to the point the internet is almost unusable until I disable IPV6, then everything is back to normal. I have tried every way possible listed in the drop down menu with the same results.
NetDog, one of the Comcast engineers is in contact with Netgear so they are aware of the problem, but like everything else Netgear support does, there may be a lot of deaths from old age before Netgears gets anything done. They are by far the worst tech support I have ever delt with.
I really like everything about the R7000, features, range, the way it looks etc.
Just hope Netgear gets their head out of the sand or wherever they have it and get this thing fixed. It's been many many months and so far nothing has been done about this problem
I know it's not just the R7000 having problems as I have friends who have the R6300, R6200, R6250 79AV and older routers with the same problem, which shot down the theory about it could be a Modem to router thing. There are 3 differernt brand modems that I know of, so the only common thing is the Netgear routers.
I am glad someone with a Netgear is not having these problems, you are very lucky.
I have had the IPV6 set for auto detect, DHCP, auto config and about everything in between, still the same problem.
As far as any hardware connected wireless, I have a HP printer, Droid cell phone, iPad2, Visio smart TV and they all work fine with IPV6 enabled for about 3 days. After that, anything that has to do with the internet degrades to where it's almost impossible to use. Disable IPV6 and all is golden again.
I use only Cat6 cable for the modem, router and computer wired connections.
What the last firmware update did was fix a problem I had with my smart TV and Netflix. Before when IPV6 was enabled, I couldn't access Netflix. I called Visio tech support told them the problem and the tech said "you are using a Netgear router aren't you" He said they were in contact with Netgear about the problem. The last update from Netger fixed that problem.
My neighbor was away for 2 weeks so I borrowed his Asus router (don't remember the model) and hooked that up to my system and enbled IPV6. Worked great for those 2 weeks, not one problem.
When he got back I hooked up the R7000 and the trouble returned.
This is not only happening on the R7000, it did the same thing with the two previous Netgear routers. A R6200 and a 79AV router so it is a firmware problem with Netgear routers which they have known about for a very long time and don't really care about it all that much. After all,they already have our $$$.
I am going to wait a couple more months and if Netgear doesn't get their act together and give me what I paid for, I will sell the R7000 to someone who doesn't care or even know about IPV6 and buy a new Asus brand router.
I have been a fan and user of netgear products for many years, but that loyalty will end unless they get something done to fix this problem. The net is full of complaints about this problem, so I know it's not just me.
Thanks for your input and as I said before, you are very lucky you don't have the problem that most of the users on Comcast have with the Netgear routers when enabling IPV6.
This is a link to a Netgear thread I started describing the on-going problem with Netgear Routers & IPV6. It makes no difference which IPV6 setting is selected pick one, enable it, reboot netgear router and wait until the cows come home and you never get a IPV4 IP or IPV6 IP. YET a Linksys WRT1900ac works out of the BOX.
Same thing here, but with a Netgear R6300 v1. We had IPv6 enabled so our Xbox Ones didn't give the "couldn't get Teredo address" error. Ever since we enabled it, we were having to send refresh signals to our modem several times a week. Comcast thought it was a modem issue and long story short, we're on our 4th modem (3 different types) and they all do it. Finally did some digging and found that it's a Netgear issue, and that just yanking the WAN cable for a few seconds would get it working temporarily. Disabled IPv6 on the R6300 and haven't had a problem since... but no more IPv6 addresses on our Xbox Ones now.
I really don't want to have to do it, but I'm considering dropping the money on that Linksys or the Asus RT-AC68U. It's crazy that on Netgear's forums, they seem to be completely ignoring this problem, which seems to cover a pretty broad range of their routers. Other than that, I've been pretty happy with their products.
I do set my router just like you said you set yours up with "auto Config" for IPV6 and the box checked for "use router as DHCP server" and it works fine for a few days. I have also set the IPV6 to "auto Config" and "DHCP" with the same results.
I can actually tell ahead of time when it's going to start acting up before it does, by going into cmd and ipconfig /all and see when Comcasts lease expires. If it says it expires at 0815 and so many seconds you can count on it starting to act weird a few seconds after that time. I have done that 3 different times to make sure. I can set the router to disable IPV6 and everything works fine again.
I can also pull the cat6 cable from the SB 6141 modem to the router for 5 to 10 seconds to reset the router and it's fine again until the lease expires, then it's back in the weird cycle again.
Is this all a Netgear problem? maybe not, but Netgear is the only one that seems to be avoiding trying to get a handle on the problem and getting it fixed. Comcast engineers have been in contact with Netgear, but they seem to be having the same problem the rest of us are having.
One thing that really has me confused is it's not just the R7000 having the problem. From the forums and threads I have read it's almost every model router that Netgear has made with the IPV6 feature that has the exact problem. Wheres the connection?
As I said before I really like this router. I get range and features that I didn't think was possible with a home router.
I hate to dump it, but when something is advertised to work and doesn't for as long as this problem has been going on it makes me wonder if they will ever get it fixed.
It's a firmware bug when the IPv6 lease expires for some reason the router is unable to obtain another one. A reboot should get you a new lease but only to expire again and IPv6 is again lost. There was a issue with the Asus N66U doing that awhile back but has since been fixed with new firmware. I would agree though Netgear is dragging there feet with a fix not cool for the ones that have spend $200.00 on a flagship router that don't work right.
Thanks for that explanation as that is eactly what's happening.
I hope Netgear does get their priorities straight and get this problem fixed.
I guess the IPV6 problem is a lower priority than say, being able to turn the LEDs on and off, getting Netflix to work on some smart TVs, they had a firmware update V188.8.131.52_1.1.20 about a month ago that fixed those problems, So it's not that Netgear isn't listening to someone.
The R7000 Nighthawk is a great router, Netgear support not so much.
I gave up waiting for Netgear to get their act together. Picked up an Asus RT-AC68U and it has been rock solid, with open NAT and IPv6 on all three Xbox Ones and zero freezes thus far. I'm glad to see that they may be updating the firmwares for the older units though... so maybe I can sell the R6300v1 that I have with a clear conscience.
Just have a question on updating firmware. It says you need to reset the router to default after the firmware update. You would then re-enter all your settings manually. I had never done that or even knew it should be done. I also see where the firmware 184.108.40.206 fixes the IPV6 problem problem, but don't see it on the NETGEAR download site. Am assuming it's still in Beta. That would be nice if the IPV6 problem has been fixed because that problem has lingered around much too long with no action being taken by NETGEAR.
I was using a debug version of the Netgear stock firmware (220.127.116.11...) where I can both reboot and keep my internet connection with IPv6 enabled, and my mobile devices get IPv6 (which they didn't with previous debug versions). Unfortunately, the full IPv6 fix set didn't make it into the latest (18.104.22.168...), maybe next time.
I have the same problem with the asus rt-ac66r and comcast. Ever since i enabled ipv6 my computer and router dont work right. The same issue with the lease i believe. It expires and i have to reset everthing.
Similar problem here to this day with a WNDR4500v2 and latest firmware. Whenever the IPv6 lease renews, the router temporarily interrupts the internet connection or reboots itself. Was supposed to be fixed a couple firmwares ago, but looks like it never will.