we 've had similar problems with completely other systems (I mean nothing related with radius but the source IP was important as well). It seems not so easy to force the traffic leaving a unix-like machine on the "right" (logical) subinterface. Alternatives are : define static routes in the machine or use the same IP address above both subinterfaces (like IPMP can do with solaris) (but I see in your email that you are probably using linux ;-). I can imagine that both solutions here might not fit you set-up... If someone knows about other alternative(s), I would be interested as well...
Regards. Benoit -----Original Message----- From: lance [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 2:40 AM To: [EMAIL PROTECTED] Subject: Binding to multiple ip's I need to have radius bound to two ip's on a server, one for an internal network and one for external, but run up against a problem. With bind_address * , if a request comes in on the 2nd ip, freeradius sends the response out of the 1st ip, eg :- eth0 10.0.0.1 eth0:1 10.0.0.2 Request on eth0:1 response gets sent with source ip of eth0 :( This causes the proxy to reject the packet as coming from the wrong place. Also - is it a bug or a feature that unless debug_level is set to 0 in radiusd.conf all logging stops ??? Regards Lance - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Subscribe to REALISE - the online magazine from BT Ignite http://www.ignite.com/realise - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
