@thekwasti 

If your camera are on a specific Port range you could createan IP Port group to ALLOW those ports then apply it via a Switch ACL, set this as a higher priority than the block VLAN and that should work

For example i have a IOT VLAN that is totally blocked from my main VLAN, however i also have cameras on that IOT so can access via ports 4455 and 4456 those specific IPs used for the cameras..  

That help?

@Philbert Thanks for the reply. That would work of course, but I don't think it is a good solution. Esp. IP cameras never have to be allowed to initiate connections themself (except for NTP for time sync).

I even tried to run both, the switch as well as the gateway in standalone mode, and even there it is not possible. I just really wonder, how a router in the business tier does not allow a simple firewall rule based on the established state.

Probably I will just step away from the whole omada ecosystem and get something like an edgeswitch (I already have an edgerouter running). The centralized management is super nice, but if fundamentals are just not available, then it does not really help. :(

Thank god I saw this forum post. That doesn't sound good.

Are there any news regarding this topic? This is a total knock out for our plans to migrate to Omada. Even Unifi offers this functionality.

Without that, a additional firewall is required and I don't see a reason for using a Omada gateway.

Are there any updates about this? This feature is a dealbreaker for me because it would make it a pain to configure an IoT network, block devices from that network to initiate connections but allowing replies (e.g. connecting to a TV or a Chromecast from a smartphone).

I guess this would have to be processed in the gateway because it's basically stateful rule between VLANs, but since Unifi gateways allow this I thought it was going to be present in Omada.

Hi,

I am new user of the omada ecosystem (router, switch, ap) and I was very unpleasantly surprised that this feature is missing. All reviews I managed to go through said this system is a 1-1 copy of unifi features but sadly it is not. 

This is very needed for clean home network segmentation (secure lan vs IoT devices), please add this to your roadmap. 

@thekwasti 

+1 for this.

This and mDNS are two big things missing.

I came here hoping to see that this issue had been fixed, just to find out that nothing has been done to address this issue.

Mabye 2022 will be the year Omada can become competative.

I would have not bought into this echo system knowing this up front.