FR 3.1 access-accept

Alan DeKok aland at deployingradius.com
Wed Nov 30 15:12:46 CET 2016


On Nov 30, 2016, at 4:26 AM, Chris Howley <C.P.Howley at leeds.ac.uk> wrote:
> 
> In using eapol_test against FreeRADIUS 2.2.3 and 3.1 (3.1.0-dead (git #4870102)) I noticed that the following attributes are NOT included in the Access-Accept sent by FR 3.1: EAP-MSK, EAP-EMSK and  EAP-Session-Id. Are these attributes required in the Access-Accept? If so, how can I copy them from the inner-tunner server to the Access-Accept?

  Those are "server-side" attributes, and do not go into any RADIUS packet.

  The packet encoder in v3.1 only prints out the attributes it puts into RADIUS packets.

  And why is this a problem?  Are you just surprised that the attributes aren't there?  Or do you have networking equipment which requires the EAP-MSK in a packet?

  ... which is impossible, because they never went in a packet.

  Alan DeKok.




More information about the Freeradius-Users mailing list