NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi 872, IPv6 & Gigaclear
Is there anyone on a Gigaclear service using IPv6 on this model Orbi and can help with the settings needed? I've a case open with Gigaclear at the moment. I have a fixed IPv4 address. Using a...
Ok so UK region.
NG is aware of current FW issues happening with IPv6. I recommend keeping IPv6 disabled for now until next FW update appears. Should be a v12 version that could have this fix included. Not sure when this new FW will be coming to your region. My region NA already has it and if all goes well, should be coming to the 870 series as well.
Might open a support ticket with NG support as well to let them know about this if you feel the need.
>> Might open a support ticket with NG support as well to let them know about this if you feel the need.
I'm not sure how long the support ticket is supposed to take but it was raised via my account in the portal on 3rd June and despite a couple of chasers, there's been nothing but crickets so far. Is this normal for NG?
Netgear are refusing to re-open the case they closed by mistake and they now claim that the router is out of warranty. And still no sign of the promised firmware update to get IPv6 working on my 871 model.
They really are complete crap, aren't they?
NG is working on the IPv6 issue. Still waiting on FW. Newer FW is working better along with ISP and client side improvements as well.
As you see, your ISP and the other 770 series user is now working which seems to have been an ISP side change. Not FW change.You might try configuring your RBR to what the 770 series user on your ISP to see if anything changes. If not, keep IPv6 disabled for now until next FW update appears.
The same IPv6 from Gigaclear worked on my previous router (a Linksys) and their tech team have confirmed that the IPv6 traffic hasn’t changed and is still coming down the wire towards the WAN port (as you’ll see in previous posts I’ve made here); which still, today, doesn’t see it, so I’m pretty sure Netgear need to fix this… :)