Hugh, There is actually a typo in the manual: the -h printout example does not show bind_address ;-) /Ingvar > -----Original Message----- > From: Hugh Irvine [mailto:[EMAIL PROTECTED]] > Sent: den 20 juni 2000 01:52 > To: Kai Schlichting; [EMAIL PROTECTED] > Subject: Re: (RADIATOR) problems /w 2.14.1 on multihomed hosts > > > > Hello Kai - > > On Tue, 20 Jun 2000, Kai Schlichting wrote: > > 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? > > > > You can set the BindAddress parameter to specify a particular > IP address, and > if you want to handle Radius requests on multiple interfaces > you can run > multiple instances of Radiator. Have a look at section 6.3.6 > in the Radiator > 2.16.1 reference manual. > > hth > > Hugh > > -- > Radiator: the most portable, flexible and configurable RADIUS server > anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, > Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc. > Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X. > > > > === > 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. > === 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.
