Question about AcctUniqueID
Dennis Skinner
dskinner at bluefrog.com
Wed Dec 7 04:12:00 CET 2005
Hello all,
I read the docs and hunted down some messages from this list about it.
Here is what is in my radiusd.conf on both servers:
acct_unique {
key = "User-Name, Acct-Session-Id, NAS-IP-Address,
Client-IP-Address, NAS-Port-Id"
}
(forgive the line wrap)
I noticed this in my radacct table:
*************************** 1. row ***************************
RadAcctId: 13988509
AcctSessionId: 00000B80
AcctUniqueId: 00eff1fb2a906db0
UserName: user at bluefrognet.net
Realm: bluefrognet.net
NASIPAddress: 192.168.1.210
NASPortId: 127
NASPortType: Async
AcctStartTime: 2005-08-30 08:52:54
AcctStopTime: 2005-08-30 08:55:14
AcctSessionTime: 135
AcctAuthentic: RADIUS
ConnectInfo_start:
ConnectInfo_stop: 26400/24000 V34=2B/V44/LAPM
AcctInputOctets: 31080
AcctOutputOctets: 118434
CalledStationId: ##########
CallingStationId: ##########
AcctTerminateCause: User-Request
ServiceType: Framed-User
FramedProtocol: PPP
FramedIPAddress: 192.168.100.101
AcctStartDelay: 0
AcctStopDelay: 5
*************************** 2. row ***************************
RadAcctId: 16960699
AcctSessionId: 00000B80
AcctUniqueId: 00eff1fb2a906db0
UserName: user at bluefrognet.net
Realm: bluefrognet.net
NASIPAddress: 192.168.1.210
NASPortId: 144
NASPortType: Async
AcctStartTime: 2005-12-05 08:54:43
AcctStopTime: 2005-12-05 09:11:08
AcctSessionTime: 986
AcctAuthentic: RADIUS
ConnectInfo_start: 46666/26400 V90/V42bis/LAPM =285
ConnectInfo_stop: 26400 V34=2B/V44/LAPM =2826400/2
AcctInputOctets: 184798
AcctOutputOctets: 1271017
CalledStationId: ##########
CallingStationId: ##########
AcctTerminateCause: User-Request
ServiceType: Framed-User
FramedProtocol: PPP
FramedIPAddress: 192.168.100.66
AcctStartDelay: 0
AcctStopDelay: 0
2 rows in set (0.03 sec)
I have obviously obfuscated some of the data, but I kept it sane to the
original.
The part that has me puzzled is the NASPortId (I didn't change that in
the data above). I assume that is the same as NAS-Port-ID in the key
above, but FreeRADIUS has created identical AcctUniqueId's with diff ports.
I am using 0.9.3 at the moment. I am working on uprading, but was
wondering if this is a bug, or something that I may have missed in the
ChangeLog, or am I missing something else?
Thanks!
--
Dennis Skinner
Systems Administrator
BlueFrog Internet
http://www.bluefrog.com
More information about the Freeradius-Users
mailing list