[PATCH] Use a random initial value for next_radius_identifier so that the identifier is less likely to be reused when multiple hostapd instances are running that will appear to a RADIUS server as being from the same NAS.

Alan DeKok aland at deployingradius.com
Sun Sep 18 17:20:17 PDT 2016

On Sep 18, 2016, at 2:29 PM, Jouni Malinen <j at w1.fi> wrote:
> I'm not sure I really understand the point of this change.. What is the
> case where this could help in making it less likely for RADIUS messages
> to look as if being from the same NAS? If there are multiple hostapd
> instances running, wouldn't each get their own UDP source port?


> The
> RADIUS identifier is of importance when there are multiple parallel
> requests from the same IP address and UDP port, but that shouldn't
> really be the case for the multiple instances case mentioned in the
> commit message. This is regardless of whether the kernel selects a
> random source port for the UDP socket.


  Alan DeKok.

More information about the Hostap mailing list