Hello Ivan -
>
> Greetings,
>
> We here have a radiator server running, and for certain realms, it queries
> other radius servers... ok fine, thats do'able.
>
> However, the machine has multiple IP addresses configured onto its only
> network interface... ok fine...
>
> AuthBy RADIUS allows for a LocalAddress config option that is used in a bind
> call, so that the request will come from that address... ok fine...
>
> actually no, its not fine... It doesn't work.
>
> The machine queries other radius servers, and all the AuthBy RADIUS has a
> LocalAddress keyword (most of them being the same as the global setting, but
> thats alright).
>
> What I have seen is that the requests were coming from the global
> LocalAddress, rather then the AuthBy RADIUS LocalAddress. So I stuck in some
> debug lines into AuthRADIUS.pm.
>
> I can see it parse the LocalAddress correctly in the keyword function, but in
> the classInit function, it was getting some other object...
>
> However, one time, it _did_ get the right object. And indeed, the requests
> went out the right ip address. But the radiator server has been restarted
> since then, and again, its not working.
>
> Ideas?
>
I will need some more information please. I need to know the platform you are
running on (hardware and software), what version of Radiator, and I will need
to see examples of the configuration file that works and the one that doesn't.
And if you also have debug output and print statement output, that would be
useful too.
thanks
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.
