NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Pro 6 SXR80 - Firmware Update V3.2.0.108 is a Disaster
Orbi Pro 6 SXR80 running in AP Mode.
Firmware Update V3.2.0.108 is a Disaster. Two major issues:
First Issue
Updated to latest firmware V3.2.0.108 and the unit would not boot back up. Stuck at slow fade-in/fade-out white LED and the unit would not boot-up no matter how many times I tried power-cycling it. I even let it sit overnight but it never came back up. I finally discovered the unit will boot-up if all network cables are disconnected from the LAN Ports. If any network cables are connected to the LAN Ports, the unit will not boot. Once the unit is up, the network cables can then be reconnected to the LAN Ports and everything seems to be functioning normally except for the Second Issue below.
Second Issue
DNS queries from all wireless clients are now being hijacked/intercepted by the unit's built-in DNSmasq daemon. A transparent proxy now appears to be running on the base unit which intercepts all DNS queries on UDP Port 53 from all wireless clients. We use our own DHCP and DNS Servers for local LAN name resolution. The wireless clients can no longer contact our DNS Servers for local name resolution because the DNS queries are being hijacked and processed by DNSmasq on the base unit instead. This makes the AP's unusable because wireless clients can no longer connect to our local DNS Servers to resolve the names of our local servers, and therefore they cannot connect to any of the servers on our network.
I reverted back to firmware V3.1.1.102 and everything is back to normal. The unit boots-up normally with all network cables connected to the LAN Ports, and DNS queries from wireless clients can reach our local DNS Servers for name resolution.
Please advise and fix these bugs in the new firmware.
Thank you.
25 Replies
I've had EXACTLY the same experience as RJU064 this morning. The auto-firmware update downloaded v3.2.0.108 to my SXR80+SXS80 deployment (running in AP Mode) and after several hours of inconvenience (thanks NetGear), I found this article.
To add to the remedial steps RJU064 stated in their 'fix' (aka downgrade to v3.1.1.102 asap), I also recommend watching https://www.youtube.com/watch?v=6N1atnfZGYE to disble the auto-update feature; which natively appears to be ghosted/locked in the routers' web admin 'Firmware Update' section.
NOTE: The YouTube video misses a config line though... there are 4 you need to modify:
> nvram set orbi_auto_upgrade=0
> nvram set auto_check_for_upgrade=0
> nvram set auto-update=0
> nvram set orbi_auto_upg=0 (not shown in the YouTube video)
NetGear - I think this firmware update should be retracted until stablised; since EVERYONE is going to reboot their kit as part of the upgrade and I strongly doubt whether folks will know to remove all LAN cables everytime a device is power cycled.- I left eero because I wanted a real network company for my Wi-Fi. Orbi seems all around more sloppy with upgrades. Just one more thing to add to the constant could not apply configuration change messages.
I concur. This update should not still be live on your servers.Hi Madquis
Are you managing Orbi 6 via Insight or it is a standalone? Please clarify if you are seeing the upgrade failure issue with 3.2.1.102 firmware?
What is the error message? Also send the debug logs config failure issue.
Go to https://<ip address of router/satellite>/debug.htm
Click on start capture ( just this nothing else on this page). Then recreate the issue.
Wait for 2-3 mins before saving the debug logs.
Upload into google drive and send me the links to download the debug file via PM.
DarienAL please send your debug files too.
Thanks,
Raghu
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
