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 tried to add another listening interface with the IP from interface B, but no difference (shot in the dark really). How can I force FreeRadius to use another IP for the proxying? Cheers, Jørn
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 control this. Read radiusd.conf, and look for the documentation in the "listen" section.
I'm running FreeRadius v2.1.1. I've tried to add another listening interface with the IP from interface B, but no difference (shot in the dark really).
Did you set the listen type to "proxy"? Alan DeKok.
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 if I'm proven wrong on that). The only way to accomplish this is to force freeradius to listen on only a single IP address (which I think is what Alan is suggesting). This will cause freeradius to use that IP as the source for anything it sends. I have run into this issue on multihomed servers and it's the only way I found to solve it. --Greg
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).
Perhaps you could try reading what I said? Or, if you're not running 2.x, .... upgrade.
The only way to accomplish this is to force freeradius to listen on only a single IP address (which I think is what Alan is suggesting). This will cause freeradius to use that IP as the source for anything it sends. I have run into this issue on multihomed servers and it's the only way I found to solve it.
This is documented. It works. It does what I said. Alan DeKok.
participants (3)
-
Alan DeKok -
Greg Woods -
Jørn Kostøl