Satish Patel wrote:
> check process ID
> #ps aux | grep radiusd
root 17622 89.6 0.0 4388 2248 pts/1 R+ 02:38 0:02 radiusd
I also found:
# netstat -nlp
udp 1580 0 0.0.0.0:1812 0.0.0.0:* 7579/radiusd
udp 0 0 0.0.0.0:1813 0.0.0.0:* 7579/radiusd
That Local IP 0.0.0.0 can't be a good sign, right?!
Could it be that I'm wrong and the whole thing is not broken after all but
running just fine only listening to a broken local IP?
- why does using -X or -x break with a segfault? (could be a different problem)
- invoking with or without -f just deliver an:
Thu Mar 8 01:50:33 2007 : Info: Starting - reading configuration files ...
and nothing more.
Shouldn't it say something like "service running" and fork to background?
radtest just keeps repeating this request without getting an answer:
# radtest steve testing localhost 10 testing123
Sending Access-Request of id 122 to 127.0.0.1 port 1812
User-Name = "steve"
User-Password = "testing"
NAS-IP-Address = 255.255.255.255
NAS-Port = 10
Shouldn't there be some sort of answer like "password ok" or so?
(Could also be a problem of radtest)
Could this be because of the "0.0.0.0"-adress?
What do you think: Does it run correctly, just with a broken local IP config?
What do you think about this?
Perhaps the whole thing is actualy working and I just didn't realize. That
would be quite embarrassing, wouldn't it? :-)
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html