NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RAX35/38/40/42/43/45/50 Firmware Version 1.0.12.120 Released
New Features: 11/09/2022
Support Japan MAP-E and DS-Lite IPv6 feature
Support manually configure DNS sever option when SPC enabled.
Bug Fixes:
Fixes the issue where IPv6 DHPC r...
What mode had yoru modem been working in? Bridge or Router mode? Your ISP Modem already has a built in router and wifi. This would be a double NAT (two router) condition which isn't recommended. This would be a double NAT condition which isn't recommended. https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NAT
Couple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the NG router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the NG router gets from the modem. https://kb.netgear.com/25891/DMZ-on-NETGEAR-routers
https://kb.netgear.com/24086/How-do-I-set-up-a-default-DMZ-server-on-my-Nighthawk-router
You might try a manual FW load of v.120 using a wired PC and web browser. Then factory reset and setup from scratch. I would ensure the ISP Modem is bridged or use option#2 for the RAX. As you factory reset the RAX, power OFF the ISP Modem for 1 minute then back ON as well.
Ensure your using CAT6 LAN cabling between the modem and router.
I recommend seeting the DHCP IP address pool to .100 thru .200
What channels are you using? Auto? Try Auto and 48 on 5Ghz. Or try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
I would disable the FW Auto Update feature as well if seen under Advanced Tab/FW update.
NavierIsStoked wrote:
This update was pushed to my router and numerous disconnect issues started happening immediately. I thought I just needed to reboot the router and when that didn’t work, I started looking at the router settings from a hardwired computer.
The wireless networks were reset to the defaults, but my custom MAC address for the router did persist (I use a dumb switch connection method for AT&T fiber). I put the wireless networks back to what I had previously, but the internet was still getting serious pauses and lags. Even my hardwired computer suffered from the same issues.
I did a hard reset of the router, reconfigured the networks and MAC back my hand (not a config file backup) and the issues persist.
I then reflashed the 1.0.11 firmware, did a hard reset, configured router by hand and all devices still have lag and pauses in data flow, both wireless and Ethernet.
I am been forced to go back to using the AT&T pace modem and non of my devices have issues.
This firmware update seems to have messed up the router enough that reflashing older firmware and factory resetting doesn’t fix the issues.
What the hell am I supposed to do now? Buy a new router? That’s unacceptable.
I use the dumb switch method. You put a dumb 5 port Gigabit switch between the router and fiber oan.
Turn on the OAN, turn on the AT&T provided router and let everything get up and running. You then turn on your netgear router, let it fully start up and configure the MAC address to be the same as the AT&T router.
Unplug the AT&T from the network switch and plug in the netgear modem to the switch. The netgear modem will take over and your should be connected to the Internet.
The AT&T modem is powered down and is only needed again if the OAN loses power or loses its connection to AT&T. The AT&T router has the authentication certificate that AT&T uses to authenticate the device (through the MAC address). But it only does it one time. If AT&T reauthenticated on a regular basis, the dumb switch method wouldn’t work. I have been using this method for 5 years now.
TLDR, the issues started immediately after 1.0.12 was pushed to my netgear router. Factory resetting and flashing an older firmware and factory resetting have not fixed the issue.
Turn on the OAN, turn on the AT&T provided router and let everything get up and running. You then turn on your netgear router, let it fully start up and configure the MAC address to be the same as the AT&T router.
Unplug the AT&T from the network switch and plug in the netgear modem to the switch. The netgear modem will take over and your should be connected to the Internet.
The AT&T modem is powered down and is only needed again if the OAN loses power or loses its connection to AT&T. The AT&T router has the authentication certificate that AT&T uses to authenticate the device (through the MAC address). But it only does it one time. If AT&T reauthenticated on a regular basis, the dumb switch method wouldn’t work. I have been using this method for 5 years now.
TLDR, the issues started immediately after 1.0.12 was pushed to my netgear router. Factory resetting and flashing an older firmware and factory resetting have not fixed the issue.
How about using the ATT modem in router mode then using the modems DMZ for the RAX router?
NavierIsStoked wrote:
I use the dumb switch method. You put a dumb 5 port Gigabit switch between the router and fiber oan.
Turn on the OAN, turn on the AT&T provided router and let everything get up and running. You then turn on your netgear router, let it fully start up and configure the MAC address to be the same as the AT&T router.
Unplug the AT&T from the network switch and plug in the netgear modem to the switch. The netgear modem will take over and your should be connected to the Internet.
The AT&T modem is powered down and is only needed again if the OAN loses power or loses its connection to AT&T. The AT&T router has the authentication certificate that AT&T uses to authenticate the device (through the MAC address). But it only does it one time. If AT&T reauthenticated on a regular basis, the dumb switch method wouldn’t work. I have been using this method for 5 years now.
TLDR, the issues started immediately after 1.0.12 was pushed to my netgear router. Factory resetting and flashing an older firmware and factory resetting have not fixed the issue.Interesting method. I put my ATT router on a different subnet, turn on IP pass-through mode, turn off the wifi radio, and hook ethernet between port 1 of ATT to the internet port of the RAX. ATT router does the handshake with ATT and passes the WAN addressing to the RAX. Great solution to atrocious ATT wifi while avoiding double natting.