Orbi Pro 6 SXR80 - Firmware Update V3.2.0.108 is a Disaster

This thread has multiple questions asked. Let me try to address one by one.

lets start with easier once.

1) Netgear does not tracks or uses DNS lookups.

On Orbi Pro. The RA feature in Orbi pro is very watered down and mainly collect things like how many satellites are connected. It does not go into user network details. Here is offical answer for Router Analytics. 

https://kb.netgear.com/000038663/What-router-analytics-data-is-collected-and-how-is-the-data-being-used-by-NETGEAR

2) Orbi pro allows user to control automatic firmware update ON/OFF.

users can use (optional) Insight manager (first year subscription is normally included ) for setting rules for firmware update

or use Local UI   in following page : Advance->Adminstration->Firmware update

By default automatic firmware update is DISABLED.

3) Insight Instant Mesh (currently supported on WAC540, WAC564, WAX610, etc) is good alternative for power-users who want special settings with mesh backhauls.

4) We acknowledge there is issue with AP mode and static IP address used for Base and Satellites (in 102 firmware). 

Team is coming up with a patch release soon. We have launched a beta program. If you would like to particate, please sign up for this forum to get bleeding edge software releases. Sometimes, we will have  new features and almost always bug fixes few days or weeks ahead of the offical scheduled release to support portal.

https://community.netgear.com/t5/Orbi-Pro-Beta/bd-p/en-business-orbiprobeta

I agree with the DNS getting hijacked.  I've rolled back to 3.1.1.102 so I could see my client IPs on my DNS server instead fo the AP.

The suspect URL hijacking is most likely related to the URL filter (blacklist) feature* [plain text DNS based, 53/UDP and 53/TCP] available on Insight and active certainly on each WAC5xx and WAX6xx which spans now out to the Orbi Pro systems, too. The standalone configured WAC5xx and WAX6xx also offer the URL filter with a URL and keyword blacklist fwiw. 

Based on observations, the WAC5xx and WAX6xx have this unlucky iptable config shown above (not retaining the original wireless client source IP on DNS queries) on access points with the URL filtering enabled only. 

Afraid, have neither Orbi Pro nor a Orbi Pro WIFI 6 at hand to compare. 

*NETGEAR Insight Basic and Premium mobile app and Insight Cloud Portal User Manual p.113 (also available on Netgear Insight Pro for the VAR and MSP arena)

There was a Beta firmware made available today -> SXK80 Beta Firmware Version 3.2.3.100 with some interesting bug fixes:

Bug Fixes

This firmware addresses the following bugs:

• Fixes DNS issues that DNS request is hijacked when clients configure static DNS server
• 512 DHCP clients support in LAN1 setting
• Fixes wrong IP assignment in VLANed networks
• Fixes wired satellite is showed disconnected in Insight webportal

Has anyone tried the beta firmware yet?

https://community.netgear.com/t5/Orbi-Pro-Beta/SXK80-Beta-Firmware-Version-3-2-3-100/m-p/2062014#M6 

Installed the v3.2.3.100 firmware last night.  Haven't checked for the "resolved" issues.  Initial observations is that roaming and changing the wireless connections between wireless 1/VLAN1, wireless 2/VLAN2, etc. is much faster that with previous firmware revision, impressably so.

As to issues...

1- ethernet backhaul does not work with MAC ACL security enabled.  All firmware revs have been dodgy with this but previously have been able to get the satellite to sync after 4 or 5 attempts.  With MAC ACL turned off the satellite syncs very fast, with it on, not at all.  And sync'ing first and then enabling MAC ACL breaks the link.

2-when using port 2 for the WAN connection my 1G download speed is cut in half.  (this is corrected in beta v3.2.2.101)

3-the attached devices are shown, but it takes a long time before they are reported correctly.  For instance after a reboot all my google home devices show up as "wired" then 20 to 30 minute later they'll get reported correctly as a wireless device.

Hi stevethompson 

Could you please share the debug logs for your (3) issues?

Thanks,

Raghu

sending now

Hi stevethompson 

We have made some improvement on your issues 1 & 2 .Would you be interested in trying it out and provide your feedback?

Thanks,

Raghu