NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
pointsToNull
Jul 31, 2020Aspirant
RAX40s lose WAN internet when switched to AP mode
I am trying to connect multiple RAX40s as APs for a R8000P base router with a switch in between. However, it seems I can only get one of them switched to AP mode and working. The rest work just fine ...
schumaku
Aug 02, 2020Guru - Experienced User
Up front, I can't see anything obvious wrong on the config based yon the description.
pointsToNull wrote:However, it seems I can only get one of them switched to AP mode and working.
Only one RAX40 does work as an access point any all other RAX40 are not workable AP under the same conditions?
pointsToNull wrote:The rest work just fine when booted from a factory reset,
Not really relevant for the AP mode - as the factory default is router mode, and all clients wil get IP addresses from the RAX40 router where they are connected to (LAN port) or associated to (wireless).
pointsToNull wrote:however when they reboot from being switched to AP mode they either lose their WAN connection (LED goes amber),
The Netgear consumer routers in AP do not maintain a WAN connection in the classic definition. In AP mode by definition it's just a L2 bridge between the port designated "Internet"/"WAN". This could have an impact on how the device does check the Internet connection - I suspect the amber LED is a false indication only as I've experienced this on some earlier tests and remember having read similar reports several times.
pointsToNull wrote:..."steal" the WAN connection from the other working RAX40.
How does this appear to you resp. the systems you connect to that router supposedly in AP mode? What comes into my mind is that one RAX40 went to router mode, and started to issue local IP addresses on the LAN/WLAN (using a different subnet like 10.0.0.0/24 with the WAN on 192.168.1.0/24 (default on your R8000P).
pointsToNull wrote:How come the RAX40s lose their WAN internet connection when switched to AP mode, but work just fine when creating their own network?
Not convinced this observation is correct - see above. The IP stack on the RAX40 is active for local maintenance, and should have the IP address configured from the primary router DHCP with reservation or being manually configured accordingly (IP address according to a plan, correct mask, correct default gateway). This IP stack on these routers in AP mode does not make the wireless clients associated to the WiFi radios to reach the Internet, leaving alone Netgear does implement ugly things sometimes, like a L2 DNS capture "relay" which can lead to strange issues...
pointsToNull wrote:I have also had BestBuy Geek squad come check it out and they couldn't figure the issue out either. They just kept repeating how I should have bought a mesh system.
Well, in my opinion consumer routers make awful bad or very limited feature wireless access points. When putting up money and time in such a set-up - long before looking into consumer Mesh systems - I tend to suggest looking into Netgear's Insight product offerings.
pointsToNull
Aug 05, 2020Aspirant
pointsToNull wrote:..."steal" the WAN connection from the other working RAX40.
How does this appear to you resp. the systems you connect to that router supposedly in AP mode? What comes into my mind is that one RAX40 went to router mode, and started to issue local IP addresses on the LAN/WLAN (using a different subnet like 10.0.0.0/24 with the WAN on 192.168.1.0/24 (default on your R8000P).
By losing WAN I mean they have a self assigned IP and no internet connection when directly plugged into that router via ethernet.
I'd have the R8000P set up in Router mode. Connect the first RAX40 as AP mode, and all works well. Sometimes even the second RAX40 connects fine as an AP. But the next RAX40 I set up either doesn't get a WAN connection or runs fine but when I go to check on the other RAX40 APs one or more of them loses WAN and shows amber color on WAN LED.
The RAX40s definitely don't unexpectedly switch back to router mode since they never give themselves or any clients an IP. But when they truly are in router mode they work just fine.
Why would only one, sometimes two, RAX40s be able to act as AP but as soon as more are connected it because an issue? Theoretically I should be able attach as many APs as I would like as long as they fit in the IP address space.
- schumakuAug 05, 2020Guru - Experienced User
pointsToNull wrote:Theoretically I should be able attach as many APs as I would like as long as they fit in the IP address space.
Something badly broken on either the R8000P or the RAX80 AP mode implementation, or both.
pointsToNull wrote:Theoretically I should be able attach as many APs as I would like as long as they fit in the IP address space.
Of course - also practically - can't agree more. Afraid, can't help much as I don't have any of these devices for testing.