NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi 970 FW 9.13.1.2 - IPv6 LAN Issues
FURRYe38, BedfordHome, donawalt (tagged you all because I wanted to provide an update on my system/setup/internet). I’ve had a lot going on this year, so had to put this on the back burner for a bit, but since the last time I posted I have switched ISPs after being with my former for over 10+ years. Their new equipment must do soon incredibly weird voodoo that the Orbi system hates and then combat that with crappy performance after their honeymoon period, that also didn’t help either. Even with upgrading my PTP link to Ubiquiti Wave Picos to completely rule out interference with the Orbi system, any time I would add a wirelessly backhauled satellite into the network, entire network would slow down. Additionally, I updated my system to 9.13.1.2 since then.
Now, fast forward to current, my new ISP is Starlink and man has it been bliss. No weird wireless backhauled slowdowns and random slow performance on WAN in general. I push 300-500DL, 50-80up. Ping is 20-25. Doesn’t matter if connected device is wired or wireless, I always get whatever WAN pushes. However, this only works if I leave IPv6 disabled. Starlink does support IPv6 natively, but although the WAN reports always getting an IPv6 address from Starlink when enabled, over time the entire network is unable to have IPv6 traffic routed despite all of my devices seeing and reporting IPv6 address and the IPv6 DNS servers (Cloudflare). If I reboot the Orbi system, IPv6 test website reports 10/10 on test scores, but then eventually over time, it’ll report 0/10 and only IPv4 will be utilized a crossed the entire network. Factory resetting the system also does not fix this permanently. It’s not a Starlink issue, but an Orbi firmware issue as it only affects LAN and not WAN itself. I have to also leave it disabled because it makes the speeds take a nose dive the minute IPv6 traffic on LAN stops being routed.
As for the beta access of firmware, Netgear made a ticket, I responded, and to this day, got no response. I followed up, still got no response. Anyone else out here seeing IPv6 issues on the current firmware?
6 Replies
Replies have been turned off for this discussion
Without a delegated /56, Orbi cannot assign additional /64s to LAN clients. So your devices get an address (likely via temporary leftover routes), but IPv6 routing is broken or incomplete, which is why websites fail to load.
Now, from Starlink’s website:
Starlink will allocate:
- One public IPv4 address for the customer’s wide area network (WAN), provisioned via Dynamic Host Configuration Protocol (DHCP) for routers/firewalls using IPv4.
- One IPv6 /64 prefix for the customer’s wide area network (WAN), provisioned via Stateless Address Auto Configuration (SLAAC) for routers/firewalls using IPv6.
- One IPv6 /56 prefix for the customer’s local area network (LAN), provisioned to routers capable of issuing a DHCPv6-PD request.
Freaking Netgear, here we go again! Fix… your… firmware… again!
Its a known issue with ipv6 not just on the 970 but on the 770 as well. It has been like this for months now. Latest firmware with 770 they disabled ipv6 by default which does not help people that need it.
Figured. Netgear is a bug fest. Next system I buy won’t be a Netgear. I’m done with their now lousy customer service and extremely unnecessary long lead times at fixing issues.
Sure has been quiet in here. How is everyone doing? Anyone heard any updates with ipv6?
After discussing the issue with higher management, we have determined that this is not a router-related problem but rather an ISP-related issue. Since the WAN port is receiving a public IP address from Starlink, we recommend configuring your router in Access Point (AP) mode, which will allow it to function as part of the existing network infrastructure.
Regards,
NETGEARThis is why nothing gets fixed.
FYI, all this is beyond forum help. We've already passed this on to NG and NG is already aware of the IPv6 issues and also involves the at the ISP level as well.
NG recommends disabling IPv6 for now until all parties get this issue resolved. Not idea when that will be.
I've had IPv6 disabled on my BE systems as my ISP doesn't support native IPv6 so I don't experience this issue.
If you can get working IPv6 at the ISP level then use there router system and use the Orbi system in AP mode. If nothing seems to work for you then you may need to find something else that does.
Otherwise everyone will need to wait for NG and the ISP to resolve all of this. Nothing else we can do here in the forums.
