Комментарии
-
I had a similar problem and it turned out that one of my dumb (unmanaged) switches did not support VLAN pass-through. It was a TP Link 2.5G switch. When I changed it with a Netgear, all the VLAN's started working. It took me a while to figure it out, but some dumb switched (even new ones) do not support VLAN pass-through.…
-
Thanks David. I use Nebula and found it as well in the AP and Port settings. Good to know where I can change it as well if I decide not to renew Nebula. I assume you have to change it for every AP when web managed? I wish there was a way in Nebula to apply it only to one AP, it changes all of them. George
-
I solved this. There was a Trendnet switch between the AP and the MG-108. The MG-108 actually supports passing through the VLAN tag (apparently the Trendnet does not). I connected the AP directly to the MG-108 and all the SSID are working on all the AP's. This work much better than expected. GeorgeРаздел: One of Four AP's not accepting connections on secondary SSID Комментарий от George993 28 июл
-
Well, I kind of solved my own problem. The MG-108 does support vlan passthrough, that's all I needed. I had a Trendnet switch between my AP and it. I guess the Trendnet does not support vlan passthrough. I removed it from the path and now the vlan's are making it to my router/firewall. No need for a managed switch. George
-
The only difference between the problem AP and the good ones is that the problem AP is connected to a Zyxel MG-108 switch. Does that switch support VLAN's? Thanks, GeorgeРаздел: One of Four AP's not accepting connections on secondary SSID Комментарий от George993 26 июл
-
It's the Zyxel Office AP that's experiencing the issue. My organization is George993 and my site is Home. Mango and Gary are the problem, Frank works fine. I have several items connecting: Alexa, Macbook Pro, Dell Latitude laptop, a Canon MF printer, iPhone 14Pro, SurfacePro, etc. I can connect to that SSID if I go by…Раздел: One of Four AP's not accepting connections on secondary SSID Комментарий от George993 26 июл
-
I believe that's part of the MLO spec. I had to create a second network (SSID) for my old clients with WPA2 security. It works pretty well that way. I actually created a separate vlan for it and just added my IoT devices. GeorgeРаздел: some clients can't connect to WBE660S with firmware 7.00 and MLO enabled Комментарий от George993 25 июл
-
I experienced this as well. The issue is that when you enable MLO, WPA3 is the only supported security. It does not drop down to WPA2. Hope that makes sense. GeorgeРаздел: some clients can't connect to WBE660S with firmware 7.00 and MLO enabled Комментарий от George993 25 июл
-
I confirmed it by noticing that all my 2.4 devices lost connection. Then I used a wifi scan app to see what channels were transmitting around me. I could see the 5GHz channels from my AP's but could not see any of them on the 2.4GHz channels. I need to check the 6GHz channels, I used a machine whose adapter does not…
-
BTW, I just double checked. I'm losing my 2.4 radio when I turn on MLO, 5 and 6 are still sending a signal. George
-
Once I turn MLO on in Nebula, I no longer see any wifi signal from any of the AP's. Can clients that do not support MLO connect to the AP's? Thanks, George
-
Thank you. I just didn't know where to look. George