Access-Request Identifier field
Hello! First of all, sorry for posting to the devel list, but my question is quite technical, I think this list suits better than "freeradius-users". I'm developing a limited, minimalistic "implementation" of a RADIUS client for an embedded system. (Basically it's just sending an Access-Request, receiving a reply, and acting upon it) I have a question about the Identifier field of the Access-Request packet. According to RFC 2865: "The Identifier field MUST be changed whenever the content of the Attributes field changes, and whenever a valid reply has been received for a previous request. For retransmissions, the Identifier MUST remain unchanged." OK, that means I have to generate a random octet for this field, that is different from the Identifier of the previous request. But, do I have to preserve the value of the last Identifier between client reboots? What happens, if the server receives a packet, with the same Identifier, as the previous, but with different authentication data (the random number generator gives the same value as the previous Identifier)? It gets treated as a retransmission, without actually processing the new data? Does the official freeradius client preserve the previous Identifier value between server restarts? I'm using freeradius version 2.0.4. regards, Peter
Peter Molnar wrote:
I'm developing a limited, minimalistic "implementation" of a RADIUS client for an embedded system. (Basically it's just sending an Access-Request, receiving a reply, and acting upon it)
This is the 'freeradius' list. If you are developing your own client, you have our best wishes. Alan DeKok.
participants (2)
-
Alan DeKok -
Peter Molnar