Forums/
Switches
2025-05-14 06:58:11
@Dougie175 Check you have your other networks assigned to the uplink port on your router that connects to your first switch Using the ALL profile on all uplinks between switches and router
0HELPFULS
Forums/
Gateways
2025-05-14 06:52:22
@Clive_A I just tested this Opened up NAT port forwarding TCP 80 + 443 to controller With a wan-in deny ip_any > ip_any rule, was still able to access controller from WAN. Looks like the port forward...
0HELPFULS
Forums/
Controllers
2025-05-14 06:33:08
@Vincent-TP Will test once the hardware controller version is released.
0HELPFULS
Forums/
Gateways
2025-05-13 20:24:00
@Colonic You can still achieve this with IP group ACLs rule 1: allow > wan in > ip_any > internal_ip_address rule 2 deny > wan in > ip_any > ip_any This will block everything getting to your lan...
0HELPFULS
Forums/
Controllers
2025-05-13 20:10:14
@AIT90 Glad it helped you out You can achieve a LOT with switch ACLs if you are smart about how to group things togther and once you realise how the directions work, its pretty easy to build...
0HELPFULS
Forums/
Controllers
2025-05-13 18:09:26
@KimcheeGUN actually, i just realised you can disable the WAN on that port as its a WAN / LAN - do that and it wont cause any problems.
0HELPFULS
