-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACL Mikrotik-Switching-Filter does not work on MikroTik RouterOS >7.15 #8251
Labels
Comments
The issue looks to be on the MIkrotik side since <7.10 works and >7.15 doesn't. Have you contacted Mikrotik about that ? |
Not really a PacketFence issue (the warning mean that it's not supported in the code base) but more a Mikrotik issue since you send the radius attribute. So on the other side it doesn't apply it and i don't know why. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Switch Template ACL "Mikrotik-Switching-Filter" does not work with newest RouterOS >7.15.
On RouterOS <7.10 it does work.
We used for the Mikrotik-Switching-Filter "action allow, src-mac-address none action drop".
When this rule is active, the client is not fully authenticated on the Mikrotik switch.
No rule is created, and the client does not appear as active under Dot1X.
When I remove this ACL from the switch template, the authentication works immediately.
We need this rule because Mikrotik cannot handle multiple MAC addresses on a single switch port,
and this ensures that only the first authenticated MAC address works.
Tested on different Mikrotik Switches.
Deleted the ACL - Client connects immediately, create the ACL - Client doesn't connect.
Tried different ACL Commands for Mikrotik-Switching-Filter - none does work.
To Reproduce
1 - Define ACL Mikrotik-Switching-Filter "action allow, src-mac-address none action drop" in Switch Template
2 - Configure RouterOS for Dot1x/MAC-Auth
3 - connect Client
Screenshots
Expected behavior
ACL should be create as Switch Rule in RouterOS and Client access for definded VLAN should be granted.
Packetfence 13.0.0
RouterBOARD CRS354-48G-4S+2Q+
Tested on RouterOS >7.15
The text was updated successfully, but these errors were encountered: