[patch] bind to own_ip_addr for RADIUS communications

[Matt Brown]

Hi,

The attached patch forces hostapd to bind to the own_ip_addr specified
in the configuration file for all RADIUS auth and acct traffic. This is
desirable as many RADIUS servers authenticate clients based on an (ip,
shared secret) tuple. If the hostapd machine has multiple interfaces
with redundant connections to the RADIUS server it is possible that
source IP address that the RADIUS server sees will not be consistent.

The patch also fixes what appeared to be a minor bug with v6 in
radius_client_init_acct. The v6 socket was never opened, but code later
in the function tried to use it regardless.

I had to rearrange where the own_ip_addr parameter is stored in the
config structures so that it was available to the radius_init routines.

I hope you find this useful.

Cheers

-- 
Matt Brown
matt at mattb.net.nz
Mob +64 21 611 544 www.mattb.net.nz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hostapd-bind-own_ip_addr.diff
Type: text/x-patch
Size: 7892 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061219/cc29abbb/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20061219/cc29abbb/attachment.pgp