NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Very weird IPv6 problem
So I have never seen this before....for reasons of instability documented here in other posts with this current version of firmware, I have IPv6 disabled on my network. However, today I saw something...
OF COURSE. Thats it. Ya, I know, we are last ones to get any information. Awesomeness.
Ya repeating of DHCP requests every few seconds solve that. Yayyyyyyy. 🎉
Mark it solved then. 😉
Release version - never been in a MacOS beta. And it did this on both MacOS 14.1 and 14.1.1 (minor bug/security fix release) which I updated to today to see if that fixed it.
Does FireFox browser show same thing or disabled?
Seems like this maybe a Safari issue that you should post about to Apple. If IPv6 is disabled on the RBR and your devices are not getting any other internet connections from other sources, seems like Safari is reporting something that's inaccurate.
I did post it on an Apple forum. I’ll post back here if there’s a resolution. It does very much seem to be specific to Safari, but isn’t it odd that the IPv6 packets and information are getting through the router to the outside world that sees an IP address and other indications that IPv6 is working properly. We know Netgear routers and Apple products don’t work together 100% don’t we? 😉
No way. 🙄
IPv6 has been working here since Monday! I did one thing different this time; as soon as I made the change to enable IPv6, I rebooted the router/satellites. Can't believe that would make a difference, since in the past I am sure I rebooted and power cycled everything, but not immediately. Anyway - since Monday 10 AM I have tested on 2 MacBook Pro's, iPhone, iPad, Windows 11, and Windows 10, with a combination of Safari, Chrome, and Edge. All have tested perfectly each time I tried - about 4x a day.The only "warning" I saw was from time to time, the browser site reported that all was perfect, however the browser is preferring IPv4 to IPv6 and it shouldn't. I read up and verified that everything these days prefers IPv6 if it's enabled and working. So I read further, and learned also that all modern browsers now employ "happy eyeball test" - they actually send out requests on BOTH IPv4 and IPv6 simultaneously, and whoever responds back first gets the payload. In the old days, they sent out one, waited for a resolution, then if necessary sent the other. So, in my case the IPv4 and IPv6 msgs go out simultaneously, and the result indicates whether things are resolved on v4 or v6. Knowing that, I would try again in a few minutes, and sure enough IPv6 was preferred. The times are very close in tests (I verified this in the test data returned), which is why one beats out the other from time to time. Finally, I activated it with all default settings. Next week I ---may--- turn on my preferred Cloudfare DNS servers, and see if things break. Or I may stick with Comcast DNS lol.
What are your IPv6 test results across other browsers? FireFox, Opera?
Interesting about how the browser is handling this.
So IPv6 has been working better for you since Monday?