Back To MAN Pages From BackTrack 5 R1 Master List
Many NAS vendors have their equipment supply an Acct-Session-Id attribute which is not unique over reboots. This makes accounting difficult, as there will be many independent sessions with the same Acct-Session-Id attribute. This module uses the Acct-Session-Id attribute, along with other attributes in the request, to create a more unique session ID, called Acct-Unique-Session-Id.
The main configuration items to be aware of are:
modules { ...
acct_unique {
key = "User-Name, Acct-Session-Id, NAS-IP-Address, NAS-Port"
}
...
}
...
preacct { ...
acct_unique ...
}
After generating the MD5 hash, the module adds it to the accounting request packet received from the client. It will look something like this in your detail file:
Acct-Unique-Session-Id = "c66ef57e480b9d26"
NOTE: Any attribute you specify that is not found in the 'dictionary' file will cause the server to fail and exit with an error.
NOTE: If you want the Acct-Unique-Session-Id of the Start and the Stop packet of a particular session to match, you must use values for the key that will stay the same for the Start and Stop. The above example is a good start. Adding 'Acct-Session-Time', for example, would cause a mismatch because that value is not the same on the Start and Stop accounting packets.
If you would like to republish one of the articles from this site on your webpage or print journal please contact IronGeek.
Copyright 2020, IronGeek