Are you just using AcctSessionId? If so, I would suggest using AcctUniqueId,
as this provides you a much more unique and random ID. I've had problems
with multiple RAS devices conflicting against session id's, or a NAS reusing
an ID after a reboot, in the past. AcctUniqueId helps avoid this problem.
In radiusd.conf
# Create a unique accounting session Id, as many NASes re-use
# or repeat values for Acct-Session-Id, causing no end of confusion.
#
# This module will add a (probably) unique session id
# to an accounting packet based on the attributes listed
# below found in the packet. see doc/rlm_acct_unique
#
acct_unique {
key = "User-Name, Acct-Session-Id, NAS-IP-Address,
Client-IP-Address, NAS-Port-Id"
}
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:freeradius-
> [EMAIL PROTECTED] On Behalf Of Graeme Hinchliffe
> Sent: Thursday, June 03, 2004 9:34 AM
> To: freeradius-users
> Subject: Accounting unique id
>
> Hiya
> I know it is unlikley but to increase the uniqueness of accounting
> id's
> withing radacct databases what do people think of the following simple
> idea:
>
> When a stop packet is recieved for a session, the unique id is set
> to
> null. This would free up that id for future use, but would it cause any
> issues?
>
> I know it's unlikley to happen, but just incase?
>
> thoughts?
>
> --
> -----
> Graeme Hinchliffe (BSc)
> Core Internet Systems Designer
> Zen Internet (http://www.zen.co.uk/)
>
> ICQ 3842605 (link)
>
> Direct: 0845 058 9074
> Main : 0845 058 9000
> Fax : 0845 058 9005
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
