Gateway ACL rules via Software Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Gateway ACL rules via Software Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Gateway ACL rules via Software Controller
Gateway ACL rules via Software Controller
2022-04-16 15:35:02 - last edited 2022-04-16 16:59:33
Model: ER7206 (TL-ER7206)  
Hardware Version: V1
Firmware Version: 1.1.1 Build 20220117 Rel.59513

Hello,

 

I'm using Omada Software Controller with ER7206 V1.0 gateway and TL-SG2210P v5.0 managed switch .

All works good so far but when i try to disable ports on all protocols from 1057 to 65535 this is where all goes wild.

 

I have several Permit rules to allow traffic from specific devices to specific public IP addresses.

 

I even have a Permit rule locally from let's say 10.0.0.1/24 to ports 1057-65535 on 10.0.0.1/24 on all protocols (TCP, UDP, etc.)

 

Let's say the picture is as follows

 

1. VPN<->VPN

2. IPTV_CLIENT<->IPTV_SERVER

3. MGMT(10.0.0.1/24)<->MGMT_PORTS(10.0.0.1/24 - 1057-65535 All)

 

But when i add the last line

 

4. LAN (ALL VLANs) DENY -> Outbound 1057-65535 on all protocols the gateway is loosing it's adoption (DISCONNECTED) and never goes back while the switch stays CONNECTED.

 

Is there something i'm doing wrong (i don't believe it's the controller host firewall because until the Rule 4 in the Gateway ACL all is connected.

Any tips or ideas would be highly appreciated.

 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Gateway ACL rules via Software Controller-Solution
2022-04-16 16:58:42 - last edited 2022-04-16 16:59:33
No idea what was the issue if there was any but after a while (around 45 mins) it got fixed by itself
Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Gateway ACL rules via Software Controller-Solution
2022-04-16 16:58:42 - last edited 2022-04-16 16:59:33
No idea what was the issue if there was any but after a while (around 45 mins) it got fixed by itself
Recommended Solution
  0  
  0  
#2
Options