Greetings.
I have been unpleasantly surprised by Radiator 2.14.1 during a medium-sized
renumbering project on BSDI 4.1: Radiator binds to 0.0.0.0 (any address),
with the machine having a primary IP number on an interface, and a secondary
one via an alias IP (BSD-style).
When radius clients (PM3's, here) contact the server on the alias IP,
Radiator authenticates them ok, but then sends the answer using the return
address of the PRIMARY interface IP! Naturally, the PM3's ignore this
answer.
Have any provisions been made to actually make use of "bind 0.0.0.0"
in a proper way? In a more recent version of Radiator?
Thanks,
bye,Kai
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
