Bug - Deleting a network that is used in EAP ACLs results in broken EAP ACLs until rebuilt
Problem:
If you delete a network (on the LAN management screen) that is used in the Destination side of an EAP ACL - it does get removed from the ACL, but the ACL is left in a broken state resulting in configuration failures, and the inability to disable or delete the offending ACL (error banner at top of page when trying to do so)
To rectify this, you can edit the ACL, click select all networks, then click it again to de-select them, then select the networks required. This "repairs" the ACL and it can then be deleted or disabled successfully.
I dont know if the same happens on the software controllers.
Hi @GRL
I had tested this locally, on a software controller and an OC300, both work correctly.
This is my LAN settings and EAP ACL settings:
Then I go to LAN page to delete Network 2, I will get a notice like below:
I click Delete and will get a succeed notice and the network 2 is deleted:
Then I go to EAP ACL page and the network 2 is deleted correctly:
Please try this again on your OC300, maybe it was an accident when you posting this.
The issue isnt that it doesnt get deleted from the ACL, the issue is that the ACL is then in some kind of broken state.
For example, in your test, one you deleted the network - try and delete or disable that ACL, and you will see the message. Eventually, the controller will pop up a configuration failure as well for the access points.
OH, i wonder if this was also the difference - in my case the EAP ACLs were set source side as an SSID, not a network, please check that as well!
