NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RAXE500 Firmware Version 1.0.10.82 Released
New Features:
Supports QoS
Supports Smart Parental Control (SPC)
Supports WPA2/WPA3 mixed mode
Security Fixes:
Fixes security vulnerabilities.
For more information about secu...
I would try a reset and also try Firefox or Opera browser on Mac.
I'll check this as well with mine. Also use Monterey as well.
If the original issue with SSID broadcast reoccurs, other weirdness, or signs of instability occur, I’ll reset the router. Setting values for the guest networks resolved the problem, they were greyed out defaults previously.
Right now, I’m more interested in the DHCP lease time issue, older Netgear routers such as the R9000 and similar ones have the ability to set lease time, but RAX series ones don’t. It’s an odd omission.
I checked mine yesterday. Set Guest Network to enabled for a 3 radios. With and with out smart connect on the main WLAN and rebooting he router each time resulted in seeing correct SSIDs enabled. Disabled GN and rebooted. Main LAN SSIDs were good.
Possible that lease time is all automatic now and NG probably set a specific time lease. We see this on most newer FW and newer products. Orbi as well.
I’m sure there’s a default lease time, there has to be when the router handles DHCP, but as I’ve mentioned, a lease time of 24 hours isn’t appropriate for a non commercial setup. What ends up happening is the DHCP service starts to refuse connects, the device ends up getting a non functional APIPA address instead, and can’t connect to the normal network, and the device correctly shows that it can’t connect to the internet.
Even with IP address reservations?
Tonkinite wrote:
I’m sure there’s a default lease time, there has to be when the router handles DHCP, but as I’ve mentioned, a lease time of 24 hours isn’t appropriate for a non commercial setup. What ends up happening is the DHCP service starts to refuse connects, the device ends up getting a non functional APIPA address instead, and can’t connect to the normal network, and the device correctly shows that it can’t connect to the internet.