Adoption Loop- Stuck in Configuring when ACL are enabled on gateway ER605 V1_1.2.3_Build 20230413
On ER605 V1_1.2.3_Build 20230413 beta build. it's getting stuck on Configuring and not getting adopted.
Can only readopt after removing all ACL rules from gateway.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Guys. I had to first add this rule. let the gateway configure after setting this and get connected. Following this I was able to get all ACL rules working.
Setting up all rules at once before it's configured is a no-go and results in an adoption loop.
There is however a heartbeat missed at the initial start. And takes longer to provision with ACL rules enabled. But it works! Great work on the beta firmware guys!
I have shared my logs on the support ticket, in case some issues can be spotted with the initial adoption delay/heartbeat missed.
mDNS and everything run smoothly with ACL. Finally, the full potential of the device is unlocked!
- Copy Link
- Report Inappropriate Content
Hello @nilava,
Thanks for reporting this issue to our community.
May I know how many Gateway ACL rules you set in total?
Let me confirm if it doesn't work if you reboot the router or the controller, it doesn't work either if you forget the ER605 and adopt it again.
But it will be fixed once you delete all Gateway ACL rules, am I right?
Can you reproduce this issue stably?
- Copy Link
- Report Inappropriate Content
@Hank21
Started with 1 rule to deny IoT VLan to other networks. It resulted in device configuration failure.
Eventually, I tried adding in some precautionary Allow ALL rules, Like LAN to ALL network, LAN to WAN and WAN to LAN, Allow All rules in hopes it might fix it.
it won't get adopted, until and unless I deleted every ACL rule from the controller. The only solution was to hard reset it for me.
Yes. I can reproduce the same every time I add a rule to deny IoT networks to others.
P.S. https://community.tp-link.com/en/business/forum/topic/605320 - Seems like a similar issue. I didn't try restricting to only one network. I was restricting IoT VLAN to every other network.
- Copy Link
- Report Inappropriate Content
Hello @nilava,
Thank you so much for taking the time to post the issue on TP-Link community!
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 TKID230429905, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Guys. I had to first add this rule. let the gateway configure after setting this and get connected. Following this I was able to get all ACL rules working.
Setting up all rules at once before it's configured is a no-go and results in an adoption loop.
There is however a heartbeat missed at the initial start. And takes longer to provision with ACL rules enabled. But it works! Great work on the beta firmware guys!
I have shared my logs on the support ticket, in case some issues can be spotted with the initial adoption delay/heartbeat missed.
mDNS and everything run smoothly with ACL. Finally, the full potential of the device is unlocked!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 810
Replies: 4
Voters 0
No one has voted for it yet.