Hi @steve_togo,

hm, are you sure? I did install 2.6.0 last few days, too. So far I can't see a problem - all clients active before the update did connect successfully again after the update. This screenshot is from one of our most active site using no VLANs, updated just yesterday, seems to be ok so far:

Not that I claim that the firmware couldn't have a problem, but if so I would have to downgrade the EAP225 ASAP ...

Which clients can't connect? All devices/brands? Or only certain brands?

steve_togo wrote

Can you try creating multiple SSID's one with a VLAN Enabled checkbox = true and another with False.

I have set up following testbed, works fine with firmware 2.5.0 and 2.6.0:

Did you set the Management VLAN in your Controller? Are you using a VLAN-aware switch or a Linux kernel-based SW VLAN?

AFAIK, UniFi use the default VLAN 1 for AP management, but I don't own UBNT switches, so I can't tell you how they process traffic on ports which are member of a tagged and an untagged VLAN at the same time. Definitely in the new EAP firmware a bug regarding untagged packets has been fixed - they were errorneously forwarded to VLAN-tagged SSIDs before.

May be it helps to check the VLAN setup once again. The Primary VLAN ID (PVID) of the port the EAP is connected to needs to be set to the VLAN ID for untagged traffic, so Ethernet frames from the untagged SSID will be tagged by the switch (and later become untagged on egress or not). The port then needs to be member of both VLANs, the untagged one and the tagged one.

Personally, I would not mix tagged and untagged VLANs on the same switch port. But this is just policy, technically it is possible. Anyway, inside a VLAN-aware switch Ethernet frames always will become tagged, even if coming in/going out untagged.

steve_togo wrote

I think it is better to have everything as tagged. Do you see any downsides with that?

No downsites, it rather has many advantages. I use only tagged links between the ISP's router and every other VLAN-aware devices (switches, servers, OC200, EAPs etc.). Only end-point devices go untagged, but even my laptop can dynamically be switched to any VLAN using profiles aka »locations« in MacOS. I completely avoid a default VLAN and even untagged traffic wherever possible.

For example, to set up my testbed above I just had to configure the port assignments of the switch, almost no cable connections had become necessary. That's the big advantage of VLANs: you can re-wire your network on the fly without having to change physical wires.

@ChrisK619, can't see a problem with EAP225-Outdoor either:

Do you also use VLANs or any special setup?