ER605 ACL Permit rule takes network down

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

ER605 ACL Permit rule takes network down

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 ACL Permit rule takes network down
ER605 ACL Permit rule takes network down
2023-03-01 02:41:14 - last edited 2023-04-14 03:20:57
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2.3

I recently updated to the beta version of the ER605 (V1) from 1.2.1 to 1.2.3. After trying to set  up a gateway ACL rule of Permit Home to IoT, it took down my home VLAN. I was not able to connect to it on any other device. 

 

I am running the software controller v5.8.4, ER605 V1, and firmware version 1.2.1 (previous) updated to 1.2.3

  0      
  0      
#1
Options
6 Reply
Re:ER605 ACL Permit rule takes network down
2023-03-02 02:40:11

Hello @shivamg42 

 

shivamg42 wrote

I recently updated to the beta version of the ER605 (V1) from 1.2.1 to 1.2.3. After trying to set  up a gateway ACL rule of Permit Home to IoT, it took down my home VLAN. I was not able to connect to it on any other device. 

 

Do you mean that after you add the gateway ACL rule of Permit Home to IoT, your devices connected to the Home VLAN networks are unable to communicate with each other, or your devices connected to other VLAN networks are unable to communicate with the devices connected to the Home VLAN networks?

 

Does it work after you delete the gateway ACL rule of Permit Home to IoT?

Could you please upload a screenshot to show your ACL rule settings for checking?

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options
Re:ER605 ACL Permit rule takes network down
2023-03-02 05:27:48

  @Fae Here is a screenshot of the ACL rule that I applied: https://imgur.com/It8Dzav.

 

After applying this rule, all devices on the Home VLAN were unable to communicate with any other VLAN. Home VLAN is connect to VLAN 10. After that home VLAN was no longer able to communicate to my Lan network on VLAN 1. I did not test if I was able to communicate to the IOT VLAN or the Guest VLAN (VLAN 20 or VLAN 30).

 

I was able to log in to my IoT network and connect back to the controller to delete the ACL rule. After deleting the rule I was able to communicate with all other networks as needed. 

 

 

 

 

 

 

 

 

  0  
  0  
#3
Options
Re:ER605 ACL Permit rule takes network down
2023-03-03 03:30:01 - last edited 2023-03-03 03:30:34

Hello @shivamg42 

 

Could you please tell us your purpose of creating the ACL rule so that we can better understand the issue? 

Except for the Permit ACL rule, do you have any other ACL rules configured in your network?

 

Please kind note that VLAN networks can communicate with each other once the Interfaces are created on ER605. If you want to allow the Home VLAN to communicate with IoT VLAN or other VLANs, there is no need to add a permit ACL. Only when you need to block the communication from one VLAN to another, would a deny ACL be required.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#4
Options
Re:ER605 ACL Permit rule takes network down
2023-03-03 03:51:47

  @Fae I was working on setting up mDNS with the beta 1.2.3 firmware on the ER605. I was following this video tutorial on how to do it, which is why I created the rule of permit home VLAN to IoT VLAN. I did see the note of it not being needed as this was a simple network, however I was still confused as to he outcome of what happened when I set the rule.This was a new rule that I created with the 1.2.3 beta firmware. 

 

I do have other ACL rules setup on my network. Here are screenshots of my ACL rules that I have setup on my network.

  0  
  0  
#5
Options
Re:ER605 ACL Permit rule takes network down
2023-03-09 07:01:42 - last edited 2023-03-09 07:01:53

Hello @shivamg42 

 

Thank you for the information. Sorry that we cannot reproduce the issue. To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230314902, please check your email box and ensure the support email is well received. Thanks!

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#6
Options
Re:ER605 ACL Permit rule takes network down
2023-04-14 03:20:37

Hello @shivamg42,

 

I'd like to update the post here.

 

TP-Link has released the Beta firmware ER605 V1_1.2.3_Build 20230413 which is fully adapted to SDN controller v5.8.
ER605 V1_1.2.3_Build 20230413 Beta For Trial (Released on Apr 14th, 2023)

You may take your time to upgrade the 1.2.3_Build 20230413 Beta firmware and confirm the issue you encountered has been resolved.

 

If the issue still exists, please don't hesitate to reply to the support email whose case ID is TKID230314902 for further follow-up.

If your concern was resolved, welcome to update this topic thread and share your solution so that others may benefit from it.

 

We are looking forward to hearing from you again.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  1  
  1  
#7
Options