WAX206 - Shelly not able to keep state

[murdof]

I'm having issue with 2xWAX206 that I bought and using as APs.

I have about 80 Shelly and smart wifi devices and while I have a cheap AX1800 Xiaomi that can handle all of them on 2.4 GHz - I can't get the WAX206 to work.

It seems that clients connect - work for a while with high latency and then they get kicked off and try to connect again.

Seems like the 2.4 Band Radio is crashing.

I tried it with 1.0.4.0 and downgraded to 1.0.3.0 just in case.

Could there be any tweaks I could make to the 2.4 radio to make this work.

On Xiaomi I have 2-4 ms ping times - while if it works on WAX206 I get 2-5000ms.

It seems that as devices start to connect to it, latency increases and eventually all of the connections crash.

Can I get logs to validate that ?

[murdof · Accepted solution]

It turns out I had to change authentication to WPA2-Personal

WPA3 wasn't backwards compatible.

I also moved 2.4 GHz WiFi network to Wireless 1 instead of 2.

In case anyone else faces similar problems.

Latency / pinging all seems to work ok now...

[michaelkenward]

---

@murdof wrote:

I'm having issue with 2xWAX206 that I bought and using as APs.

---

While many questions about routers are generic and could be answered anywhere, some things need specialist knowledge.

You might get more help, and find earlier questions and answers specific to your device, in the appropriate section for your hardware. That's probably here:

Business Wireless - NETGEAR Communities

You might like to search there for messages related to your problem.

I will ask the Netgear moderator to move your message.

In the meantime you could visit the support pages:

Support | NETGEAR

Feed in your model number and check the documentation for your hardware. Look at the label on the device for the model number.

Check for various troubleshooting tips.

You may have done this already. I can't tell from your message.

I mention it because Netgear stopped supplying printed manuals and CD versions some years ago and people sometimes miss the downloads.

[murdof · Accepted solution]

It turns out I had to change authentication to WPA2-Personal

WPA3 wasn't backwards compatible.

I also moved 2.4 GHz WiFi network to Wireless 1 instead of 2.

In case anyone else faces similar problems.

Latency / pinging all seems to work ok now...

[michaelkenward]

So, more a wifi client issue than a router thing.

Nice research Sherlock..

[murdof]

Yes the fact that a $30 Xiaomi router can work in WPA2/WPA3 auto mode and NETGEAR can’t was also a surprise for me.
Why some clients would authenticate with WPA3 mode and then disconnect after a while is also puzzling…