This is an issue for us as well. It seems in our case, the NAS retransmits the start packet 60 seconds later and this has an impact on the acctuniqueid as shown in the example below:
Tue Aug 30 13:32:49 2011
Event-Timestamp = "Aug 30 2011 13:32:48 EDT"
User-Name = "user@example.com"
NAS-IP-Address = 69.72.31.155
NAS-Identifier = "mtar-apx01.1dial.com"
Ascend-Owner-IP-Addr = 0.0.0.0
NAS-Port = 4652
Ascend-NAS-Port-Format = 4
NAS-Port-Type = Async
Service-Type = Framed-User
Class = 0x4241534943495350
Acct-Status-Type = Start
Acct-Delay-Time = 0
Acct-Session-Id = "592238627"
Acct-Authentic = RADIUS
Ascend-Auth-Delay = 1580
Ascend-Data-Rate = 21600
Ascend-Xmit-Rate = 40000
Ascend-Modem-PortNo = 92
Ascend-Modem-SlotNo = 14
Ascend-Modem-ShelfNo = 1
Calling-Station-Id = "..."
Ascend-Calling-Id-Type-Of-Num = Unknown
Ascend-Calling-Id-Number-Plan = Unknown
Ascend-Calling-Id-Presentatn = Allowed
Ascend-Calling-Id-Screening = 40
Called-Station-Id = "..."
Ascend-Data-Svc = Switched-Voice-Bearer
Framed-Protocol = PPP
Framed-IP-Address = 208.103.135.234
Proxy-State = 0x3138
Proxy-State = 0x313435
Proxy-State = 0x323034
Realm = "example.com"
Acct-Unique-Session-Id = "547e6cd62913bca0"
Timestamp = 1314725569
Tue Aug 30 13:33:49 2011
Event-Timestamp = "Aug 30 2011 13:32:48 EDT"
User-Name = "user@example.com"
NAS-IP-Address = 69.72.31.155
NAS-Identifier = "mtar-apx01.1dial.com"
Ascend-Owner-IP-Addr = 0.0.0.0
NAS-Port = 4652
Ascend-NAS-Port-Format = 4
NAS-Port-Type = Async
Service-Type = Framed-User
Class = 0x4241534943495350
Acct-Status-Type = Start
Acct-Delay-Time = 60
Acct-Session-Id = "592238627"
Acct-Authentic = RADIUS
Ascend-Auth-Delay = 1580
Ascend-Data-Rate = 21600
Ascend-Xmit-Rate = 40000
Ascend-Modem-PortNo = 92
Ascend-Modem-SlotNo = 14
Ascend-Modem-ShelfNo = 1
Calling-Station-Id = "..."
Ascend-Calling-Id-Type-Of-Num = Unknown
Ascend-Calling-Id-Number-Plan = Unknown
Ascend-Calling-Id-Presentatn = Allowed
Ascend-Calling-Id-Screening = 40
Called-Station-Id = "..."
Ascend-Data-Svc = Switched-Voice-Bearer
Framed-Protocol = PPP
Framed-IP-Address = 208.103.135.234
Proxy-State = 0x3230
Proxy-State = 0x3832
Proxy-State = 0x3934
Realm = "example.com"
Acct-Unique-Session-Id = "0041ee21d0b1c6b1"
Timestamp = 1314725629
As with many companies using load balancing, it may not be good to use Client-IP-Address to key on as this changed 60 seconds later.
Default in modules/acct_unique:
acct_unique {
key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port"
}
The man page for rlm_acct_unique shows:
acct_unique {
key = "User-Name, Acct-Session-Id, NAS-IP-Address, NAS-Port"
}
Anyone know when this was changed?
From: "Arran Cudbard-Bell" <a.cudbardb@gmail.com>
To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org>
Sent: Saturday, June 18, 2011 7:50:49 AM
Subject: Re: different acctuniqueids with common keys?
On Jun 18, 2011, at 1:26 PM, andrew@sybaweb.com wrote:
> On Sat, 18 Jun 2011 07:39:53 +0200, Arran Cudbard-Bell wrote:
>> As Alan says it's the NAS not including a consistent set of
>> Attribute and or values.
>
> The key attributes per the config (acct_unique { key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port"
> }) *are* consistent in the radacct table yet the value of acctuniqueid is not. I suppose the missing values could have been populated later.
Um yes. Especially if you're using interim updates.
-Arran
Arran Cudbard-Bell
RM-RF Limited - Security consultation and contracting
VoIP: +1 916-436-1352 Cell: +44 7854041841
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html