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. Stuc...
Hi RJU064
Could you please share the debug logs?
Go to https://<ip address of Orbi 6>/debug.htm
Click on start capture and save debug logs.
Please upload debug logs into google drive and send me link via PM.
Thanks,
Raghu
Hi RJU064
Thank you for sharing the logs. We are fixing your first issue in our upcoming releases. And thank you for mentioning the workaround.
And we are looking into your second issue and update here.
Thank you for choosing Orbi Pro 6. Your feedback is helping make product better. Keep your feedback coming in.
BR
Raghu
Hi RJU064
Your second issue will also be addressed in our next release. For now you can stay on V3.1.1.102.
Thank you for your patience.
Raghu
I think twice I've tried to upgrade past 3.1.1.102 and each time I've had to revert back. Very frustrating.
Upgraded to V3.2.1.102 this morning. Can confirm that all DNS requests are still being intercepted by the Orbi:
root@SXR80:~# iptables -nvL -tnat Chain PREROUTING (policy ACCEPT 2195 packets, 457K bytes) pkts bytes target prot opt in out source destination 184 11855 REDIRECT udp -- br-lan * 0.0.0.0/0 !172.16.1.4 udp dpt:53 redir ports 53 1358 91328 REDIRECT udp -- br3 * 0.0.0.0/0 !192.168.10.81 udp dpt:53 redir ports 53
root@SXR80:~# netstat -lntp | grep 53 tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 19606/dnsmasq tcp 0 0 :::53 :::* LISTEN 19606/dnsmasq
My Orbi is in bridge mode (i.e. it's acting as an access point, not a router). There is absolutely NO reason that it should be touching packets above layer 2, much less actively intercepting and logging all DNS requests (are these logs being sent back to Netgear servers for data collection?)!
Netgear, this is unacceptable and unwanted behavior for a device that is meant to be used in a business setting. Please fix ASAP.
I tried flushing the iptables nat table and unloading the ipt_dnshijack kernel module (and others), but the only result was completely breaking DNS for everyone on wireless. The aclhijackdns process was also running but I'm not sure if it has any affect.
routerRCE9, thank you for confirming the DNS hijacking problem still exists in this new firmware release as I'm unable to risk an outage by testing myself in my production environment.
I'm very disappointed this new firmware was released to the public without addressing both major issues. In fact, the DNS issue is not even mentioned as a "known issue" in the release notes. At least provide notice to everyone running this device in AP Mode that this DNS problem is a known issue in this firmware release.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
