[RADIATOR] BindAddress question

[Dyonisius Visser]

Well, I installed a second instance on a dual stack host, and I tested
various combinations:



BindAddress 192.87.30.31,ipv6:2001:610:148:dead::31
    I.e. hardcoded addresses - this works, both IPv4 and IPv6 clients work

BindAddress ipv6:::
   IPv4 blocked (NOTICE: Request from unknown client 192.87.30.32: ignored)

BindAddress 0.0.0.0
  This is the default. IPv4 clients work. IPv6 clients DO NOT work,
and worse, nothing is logged by radiator, no "request from unknown
client 2001:610:blah:blah"

BindAddress ipv6:::,0.0.0.0
  Startup gives some errors, and only IPv6 works:
Thu Jun  9 16:25:54 2011: DEBUG: Finished reading configuration file
'/etc/radiator/radius.cfg'
Thu Jun  9 16:25:54 2011: DEBUG: Reading dictionary file
'/etc/radiator/db/dictionary'
Thu Jun  9 16:25:54 2011: DEBUG: Creating authentication port ipv6::::1812
Thu Jun  9 16:25:54 2011: DEBUG: Creating accounting port ipv6::::1813
Thu Jun  9 16:25:54 2011: DEBUG: Creating authentication port 0.0.0.0:1812
Thu Jun  9 16:25:54 2011: ERR: Could not bind authentication socket:
Address already in use
Thu Jun  9 16:25:54 2011: DEBUG: Creating accounting port 0.0.0.0:1813
Thu Jun  9 16:25:54 2011: ERR: Could not bind accounting socket:
Address already in use
Thu Jun  9 16:25:54 2011: NOTICE: Server started: Radiator 4.8 on radius
Thu Jun  9 16:25:55 2011: NOTICE: Request from unknown client
145.100.98.42: ignored

BindAddress 0.0.0.0,ipv6:::
  Also some errors, only IPv4 works, and also nothing logged when an
IPv6 client connects:
Thu Jun  9 16:27:42 2011: DEBUG: Finished reading configuration file
'/etc/radiator/radius.cfg'
Thu Jun  9 16:27:42 2011: DEBUG: Reading dictionary file
'/etc/radiator/db/dictionary'
Thu Jun  9 16:27:42 2011: DEBUG: Creating authentication port 0.0.0.0:1812
Thu Jun  9 16:27:42 2011: DEBUG: Creating accounting port 0.0.0.0:1813
Thu Jun  9 16:27:42 2011: DEBUG: Creating authentication port ipv6::::1812
Thu Jun  9 16:27:42 2011: ERR: Could not bind authentication socket:
Address already in use
Thu Jun  9 16:27:42 2011: DEBUG: Creating accounting port ipv6::::1813
Thu Jun  9 16:27:42 2011: ERR: Could not bind accounting socket:
Address already in use
Thu Jun  9 16:27:42 2011: NOTICE: Server started: Radiator 4.8 on radius


So the only way I can radiator to accept requests from both protocols,
is to hardcode the interface addresses.

Would it be possible to have radiator listen to 4+6 without hard coding?

I think that option (whatever it looks like) should be the default.

If possible, can the behavior of the current default ('BindAddress
0.0.0.0') be changed so that it actually logs ignored incoming
requests?
I've spend quite some time figuring out what is going on, and only
tcpdump revealed that requests are actually reaching my box.

Thanks :-)

-- 
Dyonisius Visser
System & Networking Engineer
TERENA Secretariat
Singel 468 D, 1017 AW Amsterdam
The Netherlands
T +31 20 530 44 88 F +31 20 530 44 99
visser at terena.org | www.terena.org