yes, i didnt need the stack trace, i've been running it in debug mode all along, and never noticed the incorrect ip til i ran the strace.. which i agree wasnt necessary.
i'm using radtest to generate the radius packet, radtest includes a line nas = `hostname` and then includes in the packet NAS-IP-Address = $nas so it's sending my hostname instead of my IP, radiusd wants an ip address and seems to evaluate a string of characters to 255.255.255.255, which i obviously have not included in my huntgroup. I changed the radtest script to send the right IP, and everything seems to be working now. --thanks. -----Original Message----- From: Alan DeKok [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 2:09 PM To: [EMAIL PROTECTED] Subject: Re: users file not using multiple directives "Michael Komitee" <[EMAIL PROTECTED]> wrote: > actually, it's not authenticating anyone. i ran a stack trace on > radiusd, and tried to authenticate. i'm seeing that the packet radiusd > is receiving has a NAS-IP-Address of 255.255.255.255. "stack trace"? What about debugging mode? > That's the problem right there. Somehow, the nas ip address isn't > being properly set, and as a result the request does not match the > huntgroup. The NAS-IP-Address is set to whatever is in the RADIUS packet. Debugging mode will show this. Run 'tcpdump' to see it in another format. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
