Jørn Kostøl wrote:
> I got it working once I upgraded to 2.1.2. Guess
> something was wrong with my 2.1.1 install.
> A pity that it's not possible to have more then one proxy listener as
> this would be very useful.
It's possible to add that feature to the code. But it's not a
priority right n
I got it working once I upgraded to 2.1.2. Guess something was wrong with my
2.1.1 install.
A pity that it's not possible to have more then one proxy listener as this
would be very useful.
I guess I'll have to nest multiple freeradius installs in the future when I
need to proxy to other networks.
Greg Woods wrote:
>> You can control this. Read radiusd.conf, and look for the
>> documentation in the "listen" section.
>
> What this means in a nutshell is that there is no direct way to tell
> freeradius what source IP address to use when proxying(I'll be happy if
> I'm proven wrong on that)
On Thu, 2008-12-04 at 18:07 +0100, Alan DeKok wrote:
> You can control this. Read radiusd.conf, and look for the
> documentation in the "listen" section.
What this means in a nutshell is that there is no direct way to tell
freeradius what source IP address to use when proxying (I'll be happy i
Jørn Kostøl wrote:
> My server has two interfaces, A and B.
> My NAS is on interface A and I'm proxying to another Radius on interface B.
> My problem is that FreeRadius is sending packets to the Radius at
> interface B with the IP of interface A (the listening interface to my NAS).
You can cont
Hi,
My server has two interfaces, A and B.
My NAS is on interface A and I'm proxying to another Radius on interface B.
My problem is that FreeRadius is sending packets to the Radius at interface
B with the IP of interface A (the listening interface to my NAS).
I'm running FreeRadius v2.1.1.
I've
6 matches
Mail list logo
