That's my point - I'm not exactly sure what I can do with the access list... and maybe if I did some overcomplicated packet mangling... no, I don't have a clue yet.Check out the access list within CAPsMAN.
Maybe this is some misunderstanding, but I'd like to stress for a random reader of this topic that a standalone Mikrotik can do eduroam. I've been running ~100 units.Mikrotik can't do eduroam at the moment. Use ubiquiti or openwrt.
Excuse me, I haven't tried it yet (still playing with the L3 provisioning), but wouldn't eduroam setting be done with CAPsMAN by setting security.authentication-types=wpa2-eap and security.eap-methods=passthrough ? Could you please explain the problem with eduroam more?Capsman doesn't support 802.1x
vlan-mode and vlan-id can be only specified from the MAC RADIUS response. From the EAP RADIUS response it isn't specified.
+1When do we expect that to work?
Dynamic vlan assignment based on the user.fow what purposes you would use that vlan-id if we would try to add that to the EAP RADIUS response?
Testing this.vlan-mode and vlan-id can be only specified from the MAC RADIUS response. From the EAP RADIUS response it isn't specified.
you should use our MikroTik attributes:
MIKROTIK_WIRELESS_VLANID = 26, /* integer */
MIKROTIK_WIRELESS_VLANIDTYPE = 27, /* integer */
VLANIDTYPE:
0 - 802.1q tag
1 - 802.1ad tag (service tag)
I can see it did not....did it make it there?
Some news? Did you manage to set up authentication with a RADIUS server? I'm trying it, the user is verified, but obtains an IP address. Thanks for reply.I can see it did not....did it make it there?
I didn't even dare to try to assign an IP address from RADIUS server. I am going to assign it from a DHCP server once a user is properly authenticated - even when a fixed IP is required for the client. However, I still need that VLAN desperately in this scenario.Did you manage to set up authentication with a RADIUS server? I'm trying it, the user is verified, but obtains an IP address. Thanks for reply.
I strongly agree, I'm going to be involved in some projects in which that feature will be a requirement....[cut] .. the need of easy per-user separation of VLANs became more important, by an order of magnitude. Seriously. It is now the game changer for indoor installations
you should use our MikroTik attributes:
MIKROTIK_WIRELESS_VLANID = 26, /* integer */
MIKROTIK_WIRELESS_VLANIDTYPE = 27, /* integer */
VLANIDTYPE:
0 - 802.1q tag
1 - 802.1ad tag (service tag)
Thanks!
Those don't show up in any of the radius dictionaries I've seen, including your wiki.
Are there any other undocumented attributes?
Frinstance.. I have 1-22 in a standard free radius dictionary.. you gave me 26,27.. what are 23-25?
.. http://wiki.mikrotik.com/wiki/Manual:RA ... dictionary ..Any change you can also provide us with RADIUS attributes numbers 23 to 25 so I can submit an updated dictionary.mikrotik to the freeradius repository?
Mikrotik_Wireless_VLANID =* ANY,
Mikrotik_Wireless_VLANIDtype =* ANY
Tue Feb 9 08:58:53 2016
Packet-Type = Access-Accept
Proxy-State = 0x313839
Mikrotik_Wireless_VLANID = 743
Mikrotik_Wireless_VLANIDtype = 0
[...]
received Access-Accept with id 189 from [...]
Unknown-Attribute(vendor=MT, type=26) = 0x000002e7
Unknown-Attribute(vendor=MT, type=27) = 0x00000000
Signatue = [...]
Framed-MTU = 1300
EAP-Message = [...]
MS-MPPE-Send-Key = [...]
MS-MPPE-Recv-Key = [...]
Message-Authenticator = [...]