nothing to do with your post except for one detail: like alan i asked
myself what a "stack trace" could be? i thought about some special
network sniffer device or even some jargon talking about switches
(perhaps from baystack?) etc. :-)
funny, i've always been subconsiously defining "strace" as "system call
trace" or something like that because that is what it does - under
linux.
as a matter of fact debian defines it this way in its man-page: strace -
trace system calls and signals.
history out of the man page:
The original strace was written by Paul Kranenburg
for SunOS and was inspired by its trace utility. The SunOS
version of strace was ported to Linux and enhanced by
Branko Lankester, who also wrote the Linux kernel support.
Even though Paul released strace 2.5 in 1992, Branko's work
was based on Paul's strace 1.5 release from 1991. In 1993,
Rick Sladkey merged strace 2.5 for SunOS and the second
release of strace for Linux, added many of the features of
truss(1) from SVR4, and produced an strace that worked on
both platforms. In 1994 Rick ported strace to SVR4 and
Solaris and wrote the automatic configuration support. In
1995 he ported strace to Irix and tired of writing about
himself in the third person.
simultaneously, SunOS 5.9 defines it as "strace - print STREAMS trace
messages". i am not familiar with SunOS but a fast look to "man strace"
seemed to explain that it doesn't actually do the same thing.
others?
ciao
artur
Michael Komitee wrote:
>
> 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
--
Artur Hecker
artur[at]hecker.info
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
