Vincent-TP wrote For security reasons, shell access is no longer supported on EAP devices. This is disappointing to see. Shell access is already secured by access to the Oamada Controller interface...

Thanks, this seems to work fine. I didn't expect the ACL to work without an Omada router but it indeed applies to the EAPs directly. It would still be nice if we could see the default rules...

Hello, I recently deployed a custom captive portal implementation for our guest network of six Omada APs, unfortunately clients were unable to access the landing page running on a 10.x.x.x IP after...

I connected to the EAP783 via SSH as I wanted to see the kernel version and other characteristics that weren't documented (glad to finally see a 5.x kernel!). I ran "iw phy" with 3 SSIDs configured...

When checking iw phy for the device, I see there is only 1 stream supported for EHT (Wi-Fi 7) on both the 5 and 6 GHz radios, this limits theoretical throughput to 2882 Mbps on a 360 MHz channel, far...

I was very surprised to see my new EAP783 automatically create a TP_TX_VAP SSID that I don't seem to have any control of. I read that this SSID is automatically created for compatibility with some...