Processed attributes

Your device evaluates the authentication response of a RADIUS server for attributes that it may possibly process further. Most attributes however only have a meaning if the authentication response was positive, so that they influence the subsequent session:

Table 1. Overview of the supported RADIUS attributes
ID : Name Meaning Possible values in LCOS
18 Reply-Message An arbitrary string from the RADIUS server that may transport either a login failure reason or a user welcome message. This message may be integrated into user-defined start or error pages via the SEVERMSG element.  
25 Class An arbitrary octet string that may contain data provided by the authentication/accounting backend. Whenever the device sends RADIUS accounting requests, they will contain this attribute as-is. Within an authentication response, this attribute can occur multiple times in order, for example, to transmit a string that is longer than 255 bytes. The device processes all occurrences in accounting requests in the order they appeared in the authentication response.  
26 Vendor 2356, Id 1 LCS-Traffic-Limit Defines the data volume in bytes after which the device automatically ends the session. This value is useful for volume-limited accounts. If this attribute is missing in the authentication response, it is assumed that no volume limit applies. A traffic limit of 0 is interpreted as an account which is principally valid, however with a used-up volume budget. The device does not start a session in this case.  
26 Vendor 2356, Id 3 LCS-Redirection-URL This can contain any URL that is offered as an additional link on the start page. This can be the start page of the user or a page with additional information about the user account.  
26 Vendor 2356, Id 5 LCS-Account-End Defines an absolute point in time (measured in seconds since January 1, 1970 0:00:00) after which the account becomes invalid. If this attribute is missing, an unlimited account is assumed. The device does not start a session if its internal clock has not been set, or the given point in time is in the past.  
26 Vendor 2356, Id 7 LCS-Public-Spot-Username Contains the name of a Public Spot user for auto-login. Auto-login refers to the table of MAC authenticated users who are automatically assigned usernames by the server.  
26 Vendor 2356, Id 8 LCS-TxRateLimit Defines the maximum downstream rate in kbps. This restriction may be combined with the corresponding Public Spot function.  
26 Vendor 2356, Id 9 LCS-RxRateLimit Defines the maximum upstream rate in kbps. This restriction may be combined with the corresponding Public Spot function.  
26 Vendor 2356, Id 13 LCS-Advertisement-URL Specifies a comma-separated list of advertisement URLs.  
26 Vendor 2356, Id 14 LCS-Advertisement-Interval Specifies the interval in minutes after which the Public Spot reroutes a user to an advertisement URL. With an interval of 0 forwarding occurs directly after login.  
27 Session-Timeout Defines an optional maximum duration of the session, measured in seconds. If this attribute is missing in the response, an unlimited account is assumed. A Session timeout of zero seconds is interpreted as an account which is principally valid, however with a used-up time budget. The device does not start a session in this case.  
28 Idle timeout Defines a time period in seconds after which the device will terminate the session if no packets were received from the client. This value may possibly overwrite the idle timeout that is defined locally under Public Spot > Server > Idle timeout.  
64 Tunnel-Type Defines the tunneling protocol which will be used for the session.  
65 Tunnel-Medium-Type Defines the transport medium over which the tunneled session will be established.  
81 Tunnel-Private-Group-ID Defines the group ID if the session is tunneled.  
85 Acct-Interim-Interval Defines the amount of time between subsequent RADIUS accounting updates. This value is only evaluated if the RADIUS client does not have a local accounting interval defined, i.e. if you have not set an Accounting update cycle for the Public Spot module.  
Note: Note that the LCS-Account-End and Session-Timeout attributes are mutually exclusive, and it therefore does not make sense to include both in the response. If both attributes are included in a response, the attribute that appears as the last one in the attribute list will define the session’s time limit.

www.lancom-systems.com

LANCOM Systems GmbH | A Rohde & Schwarz Company | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E‑Mail info@lancom.de

LANCOM Logo