Thanks Alan for the rapid answer. My problem is that on a accounting packet the Stop hasn't the correct Acct-Session-Time. The value that is passed from the pam module is the difference between a date like 1970-01-01 and the date 2005-04-04.
So when I'm seeing the account time of an user the value of the Acct-Session-Time is very big, and is not real. My question is how can I activate the correct accounting using the pam_auth_radius? Kindly Bruno On Apr 5, 2005 2:12 AM, Alan DeKok <[EMAIL PROTECTED]> wrote: > Bruno Sousa <[EMAIL PROTECTED]> wrote: > > What happens is that the client machine does not send the correct > > ConnectTime, for instance the start Time is sent with values like: > > 1970-01-01 00:59:57. The Reason to disconnect sent on the Stop packet > > is [7]Not Local. > > There is no "accounting start time" RADIUS attribute. > > There *is* an Acct-Session-Time, but it's a time *interval*, not a > date. > > > What can I do, to enable accounting correctly? > > Perhaps you could explain what you mean by "correct ConnectTime", > and "the start Time". There are no such attributes sent by the PAM > module, and no such RADIUS attributes defined anywhere. > > 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
