I've had this working in the past, so there should be no reason why it wouldn't.

Have you run the servers in debug mode so you can see exactly what they are doing? This should be your first step.

Are you sure the two servers are reading different configuration files? You may need to specify the -d flag to radiusd.


regards, Mike


Tariq Rashid wrote:
is there an issue with freeradius proxying to a home radius server which is
in fact on the same IP address that the proxy is listening on, but on a
different port.

that is the proxy and backend servers are on the same hardware listening on
the same interface.

the proxy (using a realm in proxy.conf, specifying ip and ports) works fine
if the target is elsewhere but no traffic appears when the target is the
same ip as it is listening on.

tcpdump shows no traffic on the interface, nor the loopback lo0.

this is running on freebsd 4.10. perhaps its an OS issue? i say this because
when i use a test client to query the listening target directly, the traffic
actually is sent over lo0, despite being specified as the address of the
interface.

google of archives didn't help.

tariq

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html




- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to