Hello Chris -
On Tue, 17 Oct 2000, Chris wrote:
> I'm trying to load balance radiator across three seperate servers
> with an Extreme Summit 7i switch. All servers respond correctly to
> requests out of the server farm. However when put in the server farm they
> respond to the authentication request with the ethernet ip even though the
> request was sent to an ip on the loopback. Because it is responding with
> a different ip than what the request was sent to, my portmasters are
> ignoring the response. I noticed the 6.27.11 LocalAddress tag but seems
> to only work with AuthBy Radius. Is there a way to have radiator respond
> with the ip that the request was sent to with AuthBy Unix? The manual
> implies that this is default but it doesn't seem to be doing it. (perhaps
> because the address is on the loopback?)
>
You should use the "BindAddress" global parameter to set the address to your
loopback. If the outbound packet has a different IP address, I would suspect
that it is the operating system that is using the ethernet source IP address
rather than Radiator. What system are you running on?
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.
