Comcast XFINITY → [IPv6] Netgear retail router IPv6 issues..

Ok I am going to open this can please be nice, I want to get these issues fixed..

If your having issues with IPv6 PD dropping after a couple of days or having odd issues please post about them.. I would like to hear about what issues Netgear retail routers have.

So far I have heard the below models will drop the PD after a couple of days:

Netgear R7000 Nighthawk
Netgear R6200
Netgear R6300 v1
Netgear 3700v4
WNDR4500
WNDR4000

The Netgear WNDR3700 v4 has the problem. I've taken to setting up a daily cron task to reboot the router. The PD allocation changes each time but at least the router has a working PD allocation.

BTW. Thanks for looking into this. The problem is driving me crazy.

Thanks added to the list

I have mentioned several times before that the WNDR3400 has the problem. (I had what I guess is the WNDR3400V1, as it is not a V2, but I believe they both have the problem.

The Comcast supplied Netgear WNR1000v2-VC also loses IPv6 connectivity (apparently during the IPv6 lease renewal process) with either the original V1.2.2.56NA IPv6 firmware release or the newer V1.2.2.72NA firmware.

Yes, from this this thread from back in December »[IPv6] ipv6 stops working after a few days

There's a list of models in that thread:

Hey NotDog, I was unable to get an ipV6 address after having recently upgrading my WNDR4500 to the latest firmware update. I couldn't figure out for the life of me why I was unable to get IPV6 anymore and I was ready to make a angry post on the Comcast forums about it until I decided for the heck of it, to revert back to the previous firmware update and low and behold, I got an ipV6 address right away so this is clearly an issue with Netgear's latest firmware update that they just pushed out about a week or so ago. Hope this helps.

I should also mention that I do ocassionaly lose IPV6 and have to disable and then reenable it on my router but the issue I just posted about prevented me from getting ipv6 period.

WNDR3700v2 gets no native IPv6 address at all with firmware 1.0.1.14 (latest version).

It gets an IPv6 address, but cannot renew the lease, with firmware 1.0.0.36 (previous version).

My Netgear router is already listed. WNDR3700V4 and I have the latest firmware installed with no improvement. Firmware: V1.0.1.52 GUI Language Version: V1.0.0.173

I'm content to wait for a cure before I worry about it. I can cruise the web just fine on IPv4 for now.

FWIW The 6300v2 and R7000 share same core FW so they both would have same bugs.

That said the R7000 (and past Netgears) I have worked with the only issues I have seen is the initial request of IPv6 sometimes fails but disabling and re-enabling it resolves it. Normally it has issues if I do a change which causes some of the services to restart it won't grab the IPv6 back on it's own.

Once I have an address I have gone weeks without issues though.

I do know they don't support the /60 that I am aware and have pointed this out to the engineer to look into.

You might be interested how I solved the problem of loss and restoration of IPv6 after an upgrade of the firmware of my Zoom 5341 modem connected to a Netgear WNDR 3700 V1 with the latest firmware:

»[IPv6] Evidence of Comcast IPv6 CPE Dual Stack (CPE and CPEPD)

See page 8 near the bottom of the page for a couple of posts. This discussion may be irrelevant unless you just can't get IPv6 rather than just restore lost IPv6 access. Some folks may find it useful, though.

Also, the booting sequence of the WNDR 3700 I use I obtained from another thread in these forums which was slightly modified:

1. I found after the new modem firmware that the following worked: on the IPv6 router page set WAN to disable and LAN to Auto Config Secured. This is somewhat different from the original post where instructions were to set the WAN to Auto Detect with LAN to Auto Config Secured. In the latter case you would see DHCP with an IPv6 Address on WAN and LAN. This latter case (Auto Detect on WAN) was the usual method and always worked until the firmware change.
2. Turn off all computers on the network
3. Unplug modem & router
4. Unplug WAN cable on router
5. Wait 2 minutes
6. Plug in modem
7. Wait until modem completely syncs. ~1.5 - 2 minutes
8. Plug in router
9. Router power light will be amber
10. Wait for router power light to turn green
11. Plug in WAN cable to router
12. If in step 1 I had set WAN to disable, I returned to the router's IPv6 page and set WAN to Auto Detect and IPv6 was restored. Before the modem firmware upgrade, I had left the IPv6 setting to Auto Detect and didn't need to go back to the router to check it.

Prior to the modem firmware upgrade the only time I would lose IPv6 was when there was a power failure or some other act of god. My IPv6 access stayed up for several thousand hours then without any trouble. Now my system has been able to do "pure" IPv6 for about a week without any trouble as indicated in the linked post. I have gone through one lease renewal as far as I can see from the modem's pages w/o loss of IPv6.

Now, I have the V1 of the WNDR 3700, so as usual YMMV.

NetDog-
As you and I discussed, it also is affecting the WNR 1000 v2. (Sorry - just saw this was already mentioned - but, another case of it).

This is the router that was previously given out for Xfinity Home. As others mentioned - it'll hold the v6 address 2-3 days max, then gone.

I have a WNDR3400v2 with the same issue --> I am on Firmware V1.0.0.38_1.0.61

Thanks

My R7000 Nighthawks firmware is V1.0.2.194_1.0.15 which is the latest and still has the IPV6 issues.

Ok I just have to say this is a great community to work with..

If you are seeing something other then IPv6 dropping PD I need you to go into more details please.. Feel free to PM me.. Netgear is taking a look at these issues and now I that I their attention I want to give them a full list of the issues and devices..

Please keep in mind I will be testing what the issues are before I report them to NetGear.. So if I ask a lot of questions it is just that I am tring to recreate and confirm it.. So bottom line the more details the better..

Please add the Netgear WNR3500L and WNR3500LV2 to your IPV6 drop list as well.

Thanks

I am running this router with no drops.

I am running the latest firmware and have Comcast as a provider and my IPV6 address drops every few days on my Netgear WNR3500Lv2

I run Tomato on mine as this router was built with that in mind. I guess when you guys refer to retail you mean firmware that came with it?

Yes they do as in using Netgear Genie but my WNDR4000 is doing this every 2 day's on the older firmware, as the latest one makes my 5GHZ band not show up on any of my devices

While you have Netgear's ear, it would be great if you could convince them to make the IPv6 information a first-class citizen on their displays. All the main status screens only show IPv4 information. (Leases, dns servers, uptime etc). Especially with the PD drop issue, it would be great to have the IPv6 info easily accessible. Having this info hidden also explains how Netgear never noticed the problem -- they don't use or test IPv6 very much.

Moderator Action
The post that was here (and all 1 followups to it), has been moved to a new topic .. »[IPv6] ASUS IPv6 router issues..

My bad. Running WNR3500L on Shibby's Tomato Firmware 1.28.0000 MIPSR2-116 K26 MiniIPv6

With no drops.

my experience with the R6300v1 was it would get an IPv6 address fine via DHCP but then after a day or two it would start to degrade to the point in a few days you couldn't even browse anything even on IPv4..... remove ipv6 and it went back to normal again

Your point is a good one for both modems and routers as Netgear also makes modems as well as routers. Same for my Zoom modem. The earlier firmware had a table with a columns for IPv4 and IPv6 with data for IPv4 but no IPv6 data. The New firmware doesn't even have the blank table.

My R7000 does exactly the same thing with IPV6 enabled. I think the R6300 uses the same firmware as the R7000.
I am so glad Netdog started this thread and is looking into the problem for all of us with the Netgear routers.
Dealing with Netgear tech support is like banging your head a against a brick wall, all you get is a headache and wasted time.

Another Netgear issue is that they appear to generate a different DHCP6 DUID every time they boot. The RFC mandates that they use the same DUID for the life of the product.

I can't see the DUID, so I can't be 100% sure that it changes each time the router boots, but the fact that the Comcast DHCP6 is giving the router a new PD allocation on each boot hints strongly that the DUID changed.

I have the same FW On my R7000 and I'm not having any issues with IPv6.