NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
IPv6 Activation With Verizon FiOS
With the Orbi router (and previous Netgear routers) I found the only way to activate IPv6 is first use Auto Config. This will then default to 6to 4 Tunnel and give you a Router's IPv6 Address On LAN. Then do Auto Config and you will have IPv6. This may work on other Fiber systems. I also found for my Android phone (Galaxy S25) I needed to Enable RIPng to get IPv6 to work.
32 Replies
Kewl, glad thats working. Thank you for the tip info. Hopefully helps others.
Slight error: first you need to use Auto Detect.
FYI, when you first mentioned the RIPng 'trick' a few weeks ago, I researched RIPng, that's not a solution - maybe a bandaid of some sort. RIPng is a router-to-router distance-vector protocol. Once enabled, the router and satellites start (1) sending/receiving RIPng updates every 30 seconds to FF02::9 (UDP 521). and (2) advertising a hop-count metric (max 15) for every IPv6 prefix they know.
But Apple devices don’t run an RIPng client, so they ignore the multicast updates the Orbi would start sending. Apple phones, iPads or Macs rely on SLAAC / DHCPv6 plus Neighbor Discovery to get their addresses. (Androids do too, for example they ignore UDP 21/FF02::9, they reply on Router Advertisements + SLAAC like Apple devices for IPv6, etc.)
What probably helped was an indirect side-effect: enabling RIPng restarts the router’s IPv6 stack, forcing new Router Advertisements (RAs) and prefix-delegation to the satellites. That can temporarily patch over the firmware bug that’s causing IPv6 to vanish. However, I tried it today, and within 2 hours my iPhone 16 lost IPv6 - and it didn't even move off its charging stand!
So I am happy it works for ou at least - for now..
That RIPng setting does nothing for my Samsung s24+, I was losing ipv6 after a bit of time either way.
This maybe a work around for some and maybe not so much for others. May depend on ISP as awell. Over all this is a IPv6 issue that NG needs to resolve. If you need Ipv6 then use what works for you, older FW or configurations that may help. Otherwise users may need to disable IPv6 until NG gets something in FW that fixes all this.
It's Comcast's fault as well as NG. Aside from the setup of IPv6 with Verizon I had had zero problems.
Just curious though after you have been home for a while are you running random ipv6 tests on your phone?
My Samsung is Wi-Fi 7. Does switching to mobile and back to Wi-Fi get IPV6 back?
With my devices, I’ve never found a reliable way to get it back. Sometimes even a hard reset fails to work, although most times that does. Sometimes switching automatic Wi-Fi 6E off, forcing it to 5 GHz, does it.
I have, as a backup phone, the Motorola G 2025. I usually leave it off, but as a test I left it on. After 20 hours, it still retains IPv6. I this phone uses 802.11ac (Wi-Fi 5). So it appears the problem lies with Wi-Fi 6E and 7 implementation. I have had the Orbi since it was first available and with my Galaxy S21 I never lost ipV6 which I checked frequently since I was in the beta program. The S21 had Wi-Fi 6 (not 6E).
I have an older moto phone I think 2021. It did stop ipv6 as well on builds after 10.5.10.10 till about build 10.5.18.4. I do not recall it happening on 10.5.19.5 but I was getting no ipv6 on my fire stick 4k max uses wifi 6e and my laptop using qualcomm wifi 7 card after a while which was new. The previous builds I had no issues at all with those devices.
Try Cloudflare WARP (free) on your smartphone. So far after 20 hours I still have IPv6.
Is this an app or service for Android and Apple?
Try Cloudflare WARP (free) on your smartphone. So far after 20 hours I still have IPv6.
Its cloudflares app to change dns easily for those that do not know how to do. Its on both stores from what I remember.
Dont need warp I have the dns on my phone changed to use cloudflare already. one.one.one.one Warp is great for users who don't know how to do that. I already tried with my own dns and without on the phone as well. Still happens where it will lose ipv6 on newer builds.
As a test I yesterday installed the WARP app on my wife's Galaxy S25, but I did not enable WARP so it just changed the DNS to 1.1.1.1. Her phone lost IPv6 while my phone which had WARP enabled did not.
Seems like a good test comparison. Seems like the app helps where no app doesn't. Would be good to monitor this and let us know how it goes in 3 days.
Thanks for the details.
PaulGo another test you could try if you want to - it does appear there is a way to manually add an IPv6 address to an Android device. I have no Android expertise, so I include the link I found here:
If that makes sense to you and is doable, could you try adding a manual/static IPv6 address and manual 1.1.1.1 DHCP on one of your devices and see if IPv6 keeps working? I forgot to mention before, from my checking of message traffic, at least with Apple products there are a LOT of DHCP request messages, even in an hour despite whatever the lease time is! Devices are requesting DHCP much more frequently - at least every time they flip to a new mesh device, but even more. That certainly lends some credence to the possibility that the IPv6 IP address determination is getting messed up and therefore IPv6 is dropping.
To me there seems to be some evidence this is about just getting the NG router's DHCP and maybe DNS out of the way - but it could just be the DHCP.
