Omada: Allow internet but block LAN2LAN (untrusted network), and allow local DNS
How to allow internet in untrusted network, but prevent it from accessing other networks, and allow local DNS?
I have 3 rules (in order):
LAN-WAN Network:IoT IpGroup:Any Allow
LAN-LAN Network:IoT Network:A,B,C,D Deny
LAN-LAN Network:A,B,C,D Network:IoT Deny
What I need is to create a rule that allows all local LANs to access 172.16.0.54/32:53 TCP and UDP.
Is this possible
Am I missing something?
When I create a new LAN-LAN rule, I cannot select IP-Port group - only networks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Only some Omada gateways have LAN-LAN rules that work, but the gateways do not support IP_Group for which you need an Omada switch.
- Copy Link
- Report Inappropriate Content
@d0ugmac1 in short, this cannot be done on the gateway.
I have switched to tplink omada because it's everything in one place. I'm really trying, but the routers are missing basic functionality.
Thanks for the answer.
I will work around this by cloning the local DNS and exposing the clone in untrusted network.
- Copy Link
- Report Inappropriate Content
If you have a 7206 or 605v2 with latest firmware you can do LAN-LAN ACLs on the gateway. Not sure about any of the others though.
- Copy Link
- Report Inappropriate Content
you can make lan to lan acl on all the routers but the problem is that you can close everything or open everything but not open or close individual ports. so tp-link has not realized that it must be possible to open certain ports, e.g. dns, guest portal, printer and things like that.
No, here everything is either open or everything is closed.
switc acl is an emergency solution, acl between vlans must be done on the router, not on the switch.
- Copy Link
- Report Inappropriate Content
@MR.S exactly.
That's basic firewall.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 303
Replies: 5
Voters 0
No one has voted for it yet.