Re: [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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sep 18, 2016, at 2:29 PM, Jouni Malinen <j@xxxxx> 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?

  Yes.

> 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.

  Yes.

  Alan DeKok.


_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux