1 .\" # DS - begin display
13 .TH rlm_acct_unique 5 "3 February 2004" "" "FreeRADIUS Module"
15 rlm_acct_unique \- FreeRADIUS Module
17 The \fIrlm_acct_unique\fP module creates a unique accounting session
20 Many NAS vendors have their equipment supply an Acct-Session-Id
21 attribute which is not unique over reboots. This makes accounting
22 difficult, as there will be many independent sessions with the same
23 Acct-Session-Id attribute. This module uses the Acct-Session-Id
24 attribute, along with other attributes in the request, to create a
25 more unique session ID, called Acct-Unique-Session-Id.
27 The main configuration items to be aware of are:
29 A list of the attributes used in calculating an MD5 hash which is used
30 as the value for the unique session id.
38 key = "User-Name, Acct-Session-Id, NAS-IP-Address, NAS-Port"
57 After generating the MD5 hash, the module adds it to the accounting
58 request packet received from the client. It will look something like
59 this in your detail file:
62 Acct-Unique-Session-Id = "c66ef57e480b9d26"
65 NOTE: Any attribute you specify that is not found in the 'dictionary'
66 file will cause the server to fail and exit with an error.
68 NOTE: If you want the Acct-Unique-Session-Id of the Start and the
69 Stop packet of a particular session to match, you must use values for
70 the key that will stay the same for the Start and Stop. The above
71 example is a good start. Adding 'Acct-Session-Time', for example, would
72 cause a mismatch because that value is not the same on the Start and
73 Stop accounting packets.
81 .I /etc/raddb/radiusd.conf
87 Chris Parker, cparker@segv.org