Transferred attributes

The set of RADIUS attributes transmitted to a RADIUS server in an accounting request is similar to the set of attributes transmitted in an authentication request. However, additional attributes specific to accounting will be added. The following attributes are present in all RADIUS accounting requests:

Overview of the RADIUS attributes transmitted by the device to the accounting server

1

User name

Name of the account that was used for authentication.

4

NAS-IP-Address

IP address of your device

8

Framed-IP-Address

IP address that was assigned to the client

25

Class

All class attributes that the RADIUS authentication server sent in its authentication response.

30

Called-Station-Id

MAC address of your device

31

Calling-Station-Id

MAC address of the client The address is given byte-wise in hexadecimal notation with separators (nn:nn:nn:nn:nn:nn).

32

NAS identifier

Name of your device, if configured.

40

Acct-Status-Type

Request type which signals the start or stop of accounting, or an interim update. Please refer to the section Request types for further information.

44

Acct-Session-Id

A series of characters that uniquely identify the client. It consists of the MAC address of the network adapter, the login timestamp (measured in seconds since January 1, 1970 0:00:00), and the session counter that your device manages locally.

61

NAS-Port-Type

Type of physical port over which a user had requested authentication.

ID 19 denotes clients from WLAN
ID 15 denotes clients from Ethernet

87

NAS-Port-Id

Description of the interface over which the client is connected to your device. This can be a physical as well as a logical interface, such as LAN-1, WLAN-1-5 or WLC-TUNNEL-27.

Note: Consider that more than one client may be connected to one interface at a time, so that, unlike dial-in servers, port numbers are not unique for clients.

In the case of an accounting stop request or an interim update, the request contains the following additional attribute:

42: Acct-Input-Octets; The sum of all data bytes received from the client in this session, modulo 2³².
43: Acct-Output-Octets; The sum of all data bytes sent to the client in this session, modulo 2³².
46: Acct-Session-Time; The total duration of the client's session in seconds.
Note: If the session was ended due to an idle timeout, this value is reduced by the idle time.
47: Acct-Input-Packets; The number of data packets that your device received from the client during the session.
48: Acct-Output-Packets; The number of data packets that your device sent to the client during the session.
49: Acct-Terminate-Cause; The reason for termination or the end of the accounting session. This is sent if Acct-Status-Type has the value Start or Stop.
52: Acct-Input-Gigawords; The upper 32 bits of the sum of all data bytes received from the client during this session.
53: Acct-Output-Gigawords; The upper 32 bits of the sum of all data bytes sent to the client during this session.
55: Event-Timestamp; The elapsed time since this accounting request was submitted by the device, measured in seconds since January 1, 1970 0:00:00. This attribute is only present if your device’s real time clock contains a valid value.

Note: Note that the RADIUS accounting only starts accounting after a client successfully logs in, i.e. the time needed for authentication is not recorded. Using Traffic-Limit-Option you can limit the data traffic during the authentication phase. The final accounting stop request also contains the termination cause attribute (49). An overview of these attributes can be found in the LANCOM "Public Spot: Implementation Guide", available from www.lancom-systems.com.