I have freeradius running on a machine with 2 IPs. I have it binding to all available IPs. xxx.xxx.xxx.44 is the main IP of the machine xxx.xxx.xxx.26 is the secondary IP. (eth0:1) When a request comes in on .26 freeradius processes it and THEN sends the reply out .44! Is this the way it is suppose to be acting?
Matt wrote:
I have freeradius running on a machine with 2 IPs. I have it binding to all available IPs.
xxx.xxx.xxx.44 is the main IP of the machine xxx.xxx.xxx.26 is the secondary IP. (eth0:1)
When a request comes in on .26 freeradius processes it and THEN sends the reply out .44! Is this the way it is suppose to be acting? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Matt, Use the "bind_address" directive: bind_address = ip.add.res.s Regards --jm -- Jacques Marneweck http://www.powertrip.co.za/ http://www.powertrip.co.za/blog/
On Thursday 15 June 2006 13:20, Matt wrote:
I have freeradius running on a machine with 2 IPs. I have it binding to all available IPs.
xxx.xxx.xxx.44 is the main IP of the machine xxx.xxx.xxx.26 is the secondary IP. (eth0:1)
When a request comes in on .26 freeradius processes it and THEN sends the reply out .44! Is this the way it is suppose to be acting?
Did you build freeradius with the --with-udpfromto configure option? Another suggestion would be to have listen directives for each individual IP on your box, instead of the * catchall entry in radiusd.conf. I currently have one radius server setup with the second option, as the version it's running didn't have the udpfromto portion enabled (yeah yeah... time to rebuild). Kevin Bonner
AHHHA! I did *not* use with-udpfromto... DOH! On 6/15/06, Kevin Bonner <keb@pa.net> wrote:
On Thursday 15 June 2006 13:20, Matt wrote:
I have freeradius running on a machine with 2 IPs. I have it binding to all available IPs.
xxx.xxx.xxx.44 is the main IP of the machine xxx.xxx.xxx.26 is the secondary IP. (eth0:1)
When a request comes in on .26 freeradius processes it and THEN sends the reply out .44! Is this the way it is suppose to be acting?
Did you build freeradius with the --with-udpfromto configure option? Another suggestion would be to have listen directives for each individual IP on your box, instead of the * catchall entry in radiusd.conf. I currently have one radius server setup with the second option, as the version it's running didn't have the udpfromto portion enabled (yeah yeah... time to rebuild).
Kevin Bonner
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Jacques Marneweck -
Kevin Bonner -
Matt