@Hank21 

What do you mean with please try to setup the SSID for EAP225 and test is the same issue would happen again or not.

SSIDs are up and running a longer time already and are applied to the EAP225 devices (5 devices) and EAP653 1 device and EAP225Outdoor - 1 device

Here are the screenshots of the used SSID setup.

Firmwares are as follows:

EAP225 with 1.3.1

EAP653 with 1.3.5

ER605 with 2.3.2

Omada Controller 6.1.0.19

added the topology as well

  @Hank21 

I just disabled all WiFi, except one, on one EAP225.

only one client was connected:

But the error is still existing. No connection can be esatblished.

  @Compumark If you create a new SSID that is set to connect to VLAN 1, and try connecting to the server from that newly created SSID, do you get the same error? 

If no, it might be an issue with your settings on VLAN30, otherwise, we might need to look a little deeper into your configs. 

  @NeilR_M 

Hi,

I wanted to add the VLAN1 to the new SSID - but VLAN 1 is not allowed by Omada.

I entered then my VLAN10

and its working to connect with a client

switched to VLAN30 its not

So I started checking the VLAN Config between 10 and 30.

VLAN10 config:

VLAN30:

I can not find any difference in this config.

  @Compumark 

UDP data can be very tricky to cross vlan boundaries, and for some services it isnt possible.  Can you switch the server to TCP mode ?

  @GRL 

I just checked, I didnt found a possibility to switch. 

But as the VLAN10 is working, but no other it must be there in some config/data routing.