NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
I manually updated to 10.5.20.3 on my 770
I manually updated to 10.5.20.3 on my 770, and after the update was not able to access some websites via a Mac running MS Edge. Strange that using Safari I could access those sites, but not with Edge. Tried wsj.com and apple.com and they would not load in Edge on multiple computers, but would on the same Mac with Safari.
Downgraded back to 10.5.19.5 and the problem went away and was able to access all sites via Edge.
Tried updating the firmware one more time and still had the issue, so there is some problem with the update, at least for me. Had to downgrade again to get websites working via MS Edge on the Mac.
17 Replies
VINE0001 first, IPv6 is VERY flaky right now. If you don't need it, disable it. NG has acknowledged this and is working on it.
Second - if you want to test it some just for fun, I know that Edge (Chromium) is more “aggressive” about using IPv6 (and HTTP/3/QUIC + DoH) than Safari. So Edge keeps trying the broken IPv6 route and doesn’t fall back cleanly, while Safari usually drops to IPv4 quickly and the sites load.
Here's how it happens, possibly:
• Different DNS paths: Edge may be using Secure DNS (DoH) directly to a provider over IPv6. If that IPv6 path is broken, name lookups fail for Edge, while Safari uses the macOS/system resolver over plain DNS (often IPv4) and succeeds.
• Fallback behavior: Safari tends to fall back to IPv4 faster. Chromium will often “stick” to a v6 AAAA it resolved and not pivot as quickly if the v6 connect stalls.- there is also the potential that Edge jumps to QUIC faster than Safari, with the same result of getting hung as it locks there. - QUIC is an optimized network transport layer protocol that browsers jump to, again Edge might be getting hung there.
A few things you could play around with on one computer: (I am on Edge beta, these should be right based your version)
1. Edge → use system DNS (or turn off DoH)
edge://settings/privacy → “Use secure DNS” Off, or set Use current service provider (not a fixed provider).
Then:
• edge://net-internals/#dns → Clear host cache
• edge://net-internals/#sockets → Flush socket pools
2. Disable QUIC (temporarily)
edge://flags/#enable-quic → Disabled → relaunch Edge → try apple.com, wsj.com, microsoft.com.
3. Per-site data wipe (for the failing sites)
edge://settings/siteData → search apple.com / wsj.com / microsoft.com → Remove.
Do these one at a time and test.Thanks for the suggestions. After more troubleshooting, the router defaults to auto detect for IPv6. If, after disabling IPv6, and re-enable it, and select Auto Detect, it auto selects 6to4. This is when it fails. If I select Auto Config as opposed to Auto Detect, it works. Not sure exactly what that is doing as I am not greatly experienced with IPv6. From what I can tell, I don't think my ISP actually supports IPv6 yet, so not sure I even need to worry about having IPv6 turned on.
It is confusing as to why it would work on the old firmware as opposed to the new firmware. That tells me Netgear changed something in their IPv6 handling.
When I get more time I will try your suggestions, and also install Chrome to see if that works.
Who is your ISP and what is the brand and model # of the ONT your using?
Ya if you know that your ISP doesn't officially support native IPv6, then keep it disabled on the RBR. Mine doesn't and I don't have it enabled.
You could try Hurricane Electrics IPv6 service if you think you wanna check it out:
Hurricane Electric guide to enable IPv6 6rd on NG router | NETGEAR Communities
I only have Edge and Safari installed, but Safari definitely is ok, with only MS Edge being affected on both my Mac computers.
Ok. Wondering if you enabled IPv6 on the RBR and instead of using ISP IPv6 DNS, changed to custom IPv6 DNS like Cloudfare or Quad9, if this would help MS Edge on Mac PCs.
Something to check as well, Try Firefox or Opera browsers for Mac as well. I use these on my Mac machines here.
After troubleshooting this morning, determined that the issue is indeed IPv6. When I disabled this setting after updating the firmware, MS Edge was able to access apple.com and wsj.com with no issues. I am not sure what setting within IPv6 would be causing this, but I am going to leave it off for now and do a bit more research to see if I can determine what exactly is the issue, and why it only affects MS Edge and not Safari browsing.
Thanks to you all for your suggestions and assistance.
Interesting that only IPv6 enabled on the RBR causes this with MS Edge browser. All other browsers were good with IPv6 enabled on the RBR and Mac PC?
FWIW, I tried it on an Orbi 970 router, latest FW, and all 3 of those sites came up fine for me as well.
I’d these on one machine first; if it fixes it, repeat on the others:
1. New InPrivate window → test.
2. Disable extensions (edge://extensions/) → test.
3. Flush Edge networking:
• edge://net-internals/#dns → Clear host cache
• edge://net-internals/#sockets → Flush socket pools4. Also - can you try another DNS, like 8.8.8.8 (Google) or 1.1.1.1 (Cloudfare) manually entered on the Mac?
I might have some other suggestions if these all fail...
ISP DNS, and just going directly into ONT, no modem.
If I update again I will try your suggestions and report back. Looking forward to your testing as well. Thanks for the responses.
Will let ya know.
Ok so all of these pages loaded successfully on my Mac Book Pro 2018 OSX 15.7 with latest MS Edge version for Mac while wireless connected to my 870 series loaded with v10.5.20.4 FW loaded on the system. DNS using ISP DNS with IPv6 disabled since my ISP doesn't support IPv6. Armor and those features disabled since they have expired. 870 series connected to CAX80 cable modem in modem only mode.
Mac mini and MacBook Pro, both running Tahoe
Armor is enabled, and IPv6 was enabled I believe. Didn't try Firefox.
I may try updating again and after the update reset the router to factory settings and setup as new and see if that fixes the problem.
It is strange as I can ping those websites but for whatever reason, Edge will not open them while Safari will with no issues.
I'll try this on my Mac Book Pro with Beta 15.something on it and load MS Edge on it and test with my 870 series.
If you re-update, I would test with Armor and IPv6 disabled, thru Orbi app and on the RBR.
Using ISP DNS or custom DNS?
What brand and model# is your ISP modem or ONT?
Is IPv6 enabled on the RBR after FW was updated?
Happens with FireFox on Mac?
What model computers do you have?
What OS versions are on these computers?
Had Armor or SPC been enabled on the RBR?
I normally don't use MS Edge on Mac, Only Safari or Firefox.
In addition, I still saw the BackHaul SSID visible after the update
Also this will always be visible on BE systems. We've already asked about this. No idea if or when NG will make it hidden. Its locked so nobody can use it. Just ignore it.
