NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Apr 23, 2022Guru - Experienced User
New - RAX200 Firmware Version 1.0.6.138 Released
New Features and Enhancements:
Adds support to EU SKU for Router Analytic (RA) opt-in, opt-out feature
Removes support from China SKU for gaming VPN Funjsq
Security Fixes:
Fixes sec...
CD_router_888
Apr 27, 2022Guide
Hi adm1r4lj crjohnson Crash83K nicoimages
Can you check when the issue is happened, the openvpn function is enable or not?
I know there is a DNS proxy crash issue when enabling the openvpn.
adm1r4lj
Apr 29, 2022Star
CD_router_888 FURRYe38 crjohnson Crash83K nicoimages -
These are my findings from yesterday:
- The DNS proxy crash issue triggers on 1.0.6 when we enable OpenVPN and reboot the RAX200.
- If we enable OpenVPN on 1.0.6 and do not reboot the RAX200, the DNS issue does not trigger. Tested working fine for approx. 2hrs.
- Reverting back to 1.0.5 eliminates this bug while maintaining VPN and DNS functionality after a reboot.
Hopefully a bugfix will be made available soon.
- FURRYe38Apr 29, 2022Guru - Experienced User
Is the DNS issue seen if OpenVPN not used at all? Just the router and default DNS settings?
adm1r4lj wrote:
These are my findings from yesterday:
- The DNS proxy crash issue triggers on 1.0.6 when we enable OpenVPN and reboot the RAX200.
- If we enable OpenVPN on 1.0.6 and do not reboot the RAX200, the DNS issue does not trigger. Tested working fine for approx. 2hrs.
- Reverting back to 1.0.5 eliminates this bug while maintaining VPN and DNS functionality after a reboot.
Hopefully a bugfix will be made available soon.
- adm1r4ljApr 29, 2022Star
FURRYe38 - not in our testing. When we disabled OpenVPN and rebooted the RAX200 under 1.0.6, the issue went away. When we enabled OpenVPN and rebooted, the issue resurfaced. Also if we disabled OpenVPN under 1.0.5 and then upgraded to 1.0.6, the issue did not resurface. So I'd say there is a pretty strong connection linking the DNS issue to having OpenVPN be enabled on 1.0.6 and something loading at boot-time which triggers this issue.
- Maike13May 01, 2022Guide
I don't see any way of reporting firmware bugs so I thought I'd post this here in the hope that someone from Netgear sees it and passes it on to whoever develops the firmware.
My RAX200 router recently automatically updated to Firmware Version 1.0.6.138 and this resulted in a huge drop in wi-fi speed on my laptop. I reverted it to the previous Firmware Version 1.0.5.132 and my speeds instantly went back to where they were before.
The update didn't make any difference if I connected the laptop directly to the RAX200 LAN port, only wi-fi was affected
Speeds with Firmware Version 1.0.6.138 - 53 Mb/s download and 77 Mb/s upload (Ookla Speed Test)
Speeds with Firmware Version 1.0.5.132 - 473 Mb/s download and 669 Mb/s upload.
Speeds hardwired to an RAX200 LAN port - 937 Mb/s download and 943 Mb/s upload.
(We have 1Gb/s asynchronous fiber optic internet)
I have a slightly unusual setup, as I am using a 2019 16" MacBook Pro in dual boot mode, so I can either boot into macOS Monterey or Windows 10. Since Macbooks of this age use Intel hardware, they are really just like any other Windows PC and can run Windows natively given the right hardware drivers. Apple provides these drivers in a package they call Boot Camp. This is not the same as running Windows in a virtual environment like Parallels or VMWare, which slows performance. When booted into Windows it runs just like it would on any other Intel based PC.
The firmware update only affects the wi-fi speed in Windows, wi-fi speed in macOS Monterey is not affected. Both OS's are fully updated.
I experienced this problem previously with two other routers. the RAX120, which I exchanged for the RAX200 for this very reason, and the Amazon eero Pro 6, which our daughter has. At the time I thought this was because both those routers use Qualcomm chip sets, but perhaps it was a similar firmware issue.
I suspect the Apple provided Windows wi-fi driver may be part of the problem too.
Anyway, for now I have turned auto updating off and will stick with Firmware Version 1.0.5.132