NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Jhab
Apr 11, 2025Aspirant
WAX630 connection problem after changing management from Insight to local
Hi, I have 3 WAX630 with expired Insight subscription. I want to manage them locally. I log into the web-admin and change the management mode to local. On Save the box says it is applying the cha...
Jhab
Apr 13, 2025Aspirant
Hi again,
some more minutes later, I restarted the WAX that should again be included to insight, while the other offline WAX is off.
Although basically configured, the Setup-WLAN is starting, but it does not give my client an IP… only the 5GHz H LED is lit.
After about 5min, the setup WLAN goes away and all three GHz LED are lit. Device not available on backbone network even the network scanner cannot find it…
Insight also cannot connect to it, unsurprisingly.
I will give it another round with no bad device nearby.
Jhab
Apr 13, 2025Aspirant
tried it once more, making sure only one of the failing WAX is on… trying local configuration once more.
This brought me one step closer probably… After initial setup, the WAX was connected with its default IP 192.168.0.100. It seemed that DHCP client is not working. Setting a config manually worked, but Internet connection is still not available. Not pingable from cable. Scanner does not find the box.
But connected to a WLAN provided by the box, the scanner finds machines connected to the switch the WAX is connected to. Now this looks like a VLAN issue now… the Switch is a MS510TXUP Smart Switch.
- tigo013Apr 14, 2025Aspirant
According to the manual for the AP, you're only able to use Root - Node formation when using the Netgear Insight software.
When managing the devices locally (without the Netgear Insight), you'll need to setup a Wireless Bridge between them. So, you'd consider AP1 to be the root AP. Then, AP2 and AP3 to connect to AP1 with each using it's own wireless bridge.
I recall earlier that when I was switching away from the Netgear insight to locally managing the devices, at times, the config file gets messed up. A proper factory reset should drop all configuration aspects. Seeing that you have assigned an IP address to the APs using the DHCP server, then, that'd be the only aspect to be retained.
It's worth noting that access to the AP config page, is restricted to the Ethernet cable, once you've configured VLANs. By that I mean:
Say you're computers network is VLAN 20.
You're infrasctructure network is VLAN 1, which is your management VLAN for your AP.
You won't be able to access the configuration page of the AP when connected via Wifi on VLAN20 despite routing happening elsewhere. You're able to access the configuration page of the AP when accessing it via ethernet from a computer on VLAN20 connected to the LAN switch. I think it's a precautionary thing that Netgear has so that people don't lose their connection as they're configuring the Wifi using the AP-connection. They want you to be connected via ethernet. If your computer VLAN is 1, and Management VLAN is 1, and AP vlan is 1, - then you won't have that problem.
- JhabApr 25, 2025Aspirant
Hi,
I was able to solve the problem… it was caused mainly by a malfunctioning POE-Switch.
Part of the confusion was caused by the WAX to take its default IP-Adress of 192.168.0.100 although DHCP was available. After I realised this, I was able to connect to the WAX and debug it.
Lastly, I was able to reconfigure all WAXes successfully. Unfortunately, the web interface is not that good. You have to apply every page/dropdown on it's own or you will loose your changes. And applying takes quite some time for most options.
Thanks all for your help, best
Jochen
- JhabApr 25, 2025Aspirant
tigo013 wrote:When managing the devices locally (without the Netgear Insight), you'll need to setup a Wireless Bridge between them. So, you'd consider AP1 to be the root AP. Then, AP2 and AP3 to connect to AP1 with each using it's own wireless bridge.
I don't think that's true. You only need to do this when you want a Mesh network where one Ap is connected by wire and others work as repeater/extender.
Well, I did not do this. I have 4 installed, every one with cable connected to LAN and Internet. I configured the same SSID on each and it seems to work as expected. I configured Load Balancing and it all seems to work as expected. But It will probably need more time to give a final verdict on this.
Best,
Jochen
- schumakuApr 26, 2025Guru - Experienced User
Yes, Jochen is perfectly right*
Jhab wrote:
tigo013 wrote:
When managing the devices locally (without the Netgear Insight), you'll need to setup a Wireless Bridge between them. So, you'd consider AP1 to be the root AP. Then, AP2 and AP3 to connect to AP1 with each using it's own wireless bridge.
I don't think that's true. You only need to do this when you want a Mesh network where one Ap is connected by wire and others work as repeater/extender.
Well, I did not do this. I have 4 installed, every one with cable connected to LAN and Internet. I configured the same SSID on each and it seems to work as expected. I configured Load Balancing and it all seems to work as expected. ...
Correct.
-Kurt.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!