Thomas Fagart wrote:
The server where it is located has two IP interfaces and even worse on
one of the interface we're using IP aliasing :-)
I've notice that freeradius always use the same IP to proxy from inner
tunnel.
I know that I could use the listen directive in radiusd.conf (and that's
what I've done) to force freeradius to choose the correct IP to proxy.
Even better, use the latest version of the server. It supports a
"src_ipaddr" for each home server. This forces the server to open a
socket using a particular address.
That looks great, but 2.1.10 is not working properly on my environment
(you've corrected something in git commit 5849d7aa69)
Then I would wait for 2.1.11, or do you thing it's ok to use git
"release" in Production
branch.
But this does not seems to work for inner-tunnel proxyfication.
That might be true for 2.1.6. For later versions, probably not.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html