We are migrating our RADIUS server from a Cisco ISE to a FortiAuthenticator (FAC) for our Meraki equipment.   A packet capture shows a successful Access-Accept in a packet capture, however the wireless client behind the Meraki doesn´t get DHCP nor network connectivity when authenticating against the FAC. When authenticating against the ISE, it works instantly.   The difference in the packet capture between ISE and FAC are that the ISE returns a rewritten User-Name value and a Class while the FortiAuthenticator doesn´t:   ISE: Access-Request: User-Name = host/W10CLIENT.company.local Access-Accept: User-Name = W10CLIENT$@domain Class (25) AVP   FortiAuthenticator: Access-Request: User-Name = host/W10CLIENT.company.local Access-Accept: User-Name = host/W10CLIENT.company.local No Class (25) AVP   My question now is, what does the Meraki MR12 Access Point expects as the minumum required RADIUS attributes (AVP) packets for allowing the user onto the network? ... View more