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. 😉
It's been perfect still. Every test passes except briefly as I explained a browser may temporarily report preferring IPv4 (but IPv6 is still working fine) - and that reverses to IPv6 preference in a minute or 2. If you read my explanation, that's a temporary thing based on response times. Browsers tested/platform:
MacOS
Safari √
Chrome √
Windows 11 and Windows 10
Edge √
iOS
Safari √
iPadOS
Safari √
That's all I got 😇
Kewl. Wondering if still there was an ISP service side issue along with browser handling changes.
If I remember correctly, this all started in January with users reporting a problem between Netgear and Comcast. It seems my recollection is that some thing changed on the Comcast side, but not that it was a bug or something like that. It was some sort of an upgrade or improved compliance or something, that Netgear was not handling. That was never substantiated though. so we really don’t know if it was Comcast, Netgear, or both.
Well last year CC/XF started doing this mid-split thing. I presume there was some of this involved as well as I had seen others, not with IPv6 issue, just bad services here and there in general after they started rolling this new configuration out. I presume this may have caused other issues like IPv6 operation to be effected as well. Hard to say where it all comes down too. Seems like if maybe the ISP has corrected there side and browsers maybe have been updated to better handle IPv6 testing, could have been root cause all along. Though there still maybe some NG handling as well in IPv6 protocols. Still probably haven't updated the core framework since 2016 from what we know.
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. 😉
Done 😁
Any updates on this?
So it's probably been about 6 weeks and IPv6 has been working perfectly!