@ChandlerBing I was confused by the rule you show in post #1. That is default behaviour so why create a rule and possible problems. Your second forwarding rule should work, assuming the 192.168.x.x...

@nRayAffair I think the problem is bigger than that. The issue appears to be with the 5.13 controller (@Hank_21 to confirm), as the 1.2.3 firmware is fine if loaded manually. So 5.13 needs to get...

@Destor That's a lot of firepower for one apartment, but regardless, the ceiling APs can mesh with each other as long as you have a controller like the OC200 (or a software instance running on a Pi,...

@ChandlerBing If you forward ALL the ports, it won't forward specific ones. I would use the DMZ feature as a catchall to forward unspecified ports, and then specific port forwarding rules for each...

@SteveMann Try a manual upgrade after downloading the firmware from the 'generic' site...ie if you have a /us/ or /ca/ or /eu/ etc in the URL, replace it with /en/ and reload the page.

@stanward No. But you aren't really designing with the Omada philosophy in mind either. Thought #1: The EAPs can each broadcast multiple SSIDs and map those to unique VLANs, while using another VLAN...