Sorry to disturb.
This is my simplified problem, Which I can't change the machines I don't
admin.
I admin a proxy radius which queryies (for want of a better word) a master
radius, I send the request and get back a response from a totally
different master radius machine, obviously with
On Thu, 21 Feb 2002, Rainer Clasen wrote:
stuartc wrote:
I admin a proxy radius which queryies (for want of a better word) a master
radius, I send the request and get back a response from a totally
different master radius machine, obviously with different IP. I am sure by
now most of
stuartc [EMAIL PROTECTED] wrote:
No it has to be done aboveSend a request one ip and get a response
from one of two different masters... so I could infact send a request to
one master and get a response from there other, there is no way round it.
I'm *amazed* that this works for any
On Thu, Feb 21, 2002 at 11:44:02AM -0500, Alan DeKok wrote:
stuartc [EMAIL PROTECTED] wrote:
No it has to be done aboveSend a request one ip and get a response
from one of two different masters... so I could infact send a request to
one master and get a response from there other, there
Steve Langasek [EMAIL PROTECTED] wrote:
Is this a good time to inquire whether Freeradius CVS fixes the bug
where the server doesn't set the source address in its response packets,
causing problems if radiusd is running on a server with multiple IP
addresses? :)
The server doesn't set the
Alan DeKok [EMAIL PROTECTED] wrote:
Hmm... if 'bind_address' is set, then the proxy fd *should* be bound
to that IP address, too. That currently isn't done. Luckily, it's a
~5 line patch.
Never mind... I read a little more of the code, and it *is* done.
So if you set 'bind_address =
Steve Langasek [EMAIL PROTECTED] wrote:
Freeradius receives a request from a NAS sent to IP address a.b.c.d;
it handles the request, and sends back a reply without explicitly
choosing a source IP address for the socket -- it may be the right IP
address, it may be (depending on what the kernel
