Re: [Help-gnu-radius] Reasons for an Accounting-Response to not be loggIn-reply-to: Your message of Fri, 21 Feb 2003 16:04:10 -0600 (CST) <address@hidden>

[Sergey Poznyakoff]

> Accounting-Response, therefore by showing you the Auth record I was
> proving that the fields (User-Name, Acct-Session-Id, etc) were going to be
> in the Acct record and that was _not_ why it was not being logged.

Oh, yes. I see the point know.

> As for radius.c:
> 
> Feb 21 17:00:30: Main.debug: radiusd.c:1265:rad_spawn_child: adding AUTH 
> request to the list. 1 requests held.
> Feb 21 17:00:30: Main.debug: radiusd.c:1303:rad_spawn_child: started handler 
> at pid 9614

OK, but this is a diagnostics from a different debugging level. With
the debugging level "radius.c" you should see in your log something like:

Jul 10 23:26:51: [14121]: Main.debug: radius.c:367:radrecv: Request
from host d4567890 code=1, id=219, length=154
Jul 10 23:26:51: [14121]: Main.debug: radius.c:443:radrecv: recv:
User-Name = bgaris
Jul 10 23:26:51: [14121]: Main.debug: radius.c:443:radrecv: recv:
Password = \315\233\121\054\225\012\170\205\077\324\244\324\346\223Ur
Jul 10 23:26:51: [14121]: Main.debug: radius.c:457:radrecv: recv:
NAS-IP-Address = 66.19.47.14
Jul 10 23:26:51: [14121]: Main.debug: radius.c:457:radrecv: recv:
NAS-Port-Id = 1038
Jul 10 23:26:51: [14121]: Main.debug: radius.c:457:radrecv: recv:
Ascend-NAS-Port-Format = 2_4_5_5

etc.. Make sure you have set it up properly. In your raddb/config:

logging {
        ...
        category =debug {
                level "radius.c";
                ...




Anyway:

> I see no ACCT request has been added to the list at all... So does this
> mean the NAS didn't send the Accounting-Response at _all_?

Yes, it definitely means that.

Regards,
Sergey