The following vendor-specific RADIUS attributes from LANCOM Systems (Vendor 2356) are supported by the PPPoE server:
| RADIUS ID | Attribute name / description | Access Request | Access Reply | Example |
|---|---|---|---|---|
| 2356-8 | LCS-TxRateLimitDefines a maximum downstream rate in kbps at Layer 2 from the perspective of the PPPoE server (NAS) toward the PPPoE client. This can be used to limit the download bandwidth of a PPPoE client at Layer 2. This function is only supported when the PPPoE client is connected via LAN interfaces. It is not supported when the PPPoE client is connected via Layer 2 tunnel interfaces such as Ethernet-over-GRE (EoGRE) or L2TPv3. | x | LCS-TxRateLimit=10000 | |
| 2356-9 | LCS-RxRateLimitDefines a maximum upstream rate in kbps at Layer 2 from the perspective of the PPPoE server (NAS) from the direction of the PPPoE client. This can be used to limit the upload bandwidth of a PPPoE client at Layer 2. This function is only supported when the PPPoE client is connected via LAN interfaces. It is not supported when the PPPoE client is connected via Layer 2 tunnel interfaces such as Ethernet-over-GRE (EoGRE) or L2TPv3. | x | LCS-RxRateLimit=10000 |
The following vendor-specific attributes from the Broadband Forum (Vendor 3561) are supported.
The values are inserted by an external access node such as a DSLAM, OLT, or switch and are transmitted as user-specific PPPoE tags in PADI/PADR messages. The PPPoE server transfers the existing attributes from the PPPoE tags into RADIUS attributes according to RFC 4679 (e.g., in the Access Request) toward the RADIUS server.
The values 3561-129 to 3561-144 contain general status values (e.g., attainable data rate in DSL) about the condition of the line to the router.
| RADIUS ID | Attribute name / description | Access Request | Access Reply |
|---|---|---|---|
| 3561-1 | Agent-Circuit-IdThis attribute contains the logical port name of the access node from which the PPPoE client’s requests are initiated. | x | |
| 3561-2 | Agent-Remote-IdThis attribute contains an operator-specific, statically configured string that uniquely identifies the subscriber on the corresponding access node port. | x | |
| 3561-129 | Actual data rate Upstream | x | |
| 3561-130 | Actual data rate Downstream | x | |
| 3561-131 | Minimum Data Rate Upstream | x | |
| 3561-132 | Minimum Data Rate Downstream | x | |
| 3561-133 | Attainable Data Rate Upstream | x | |
| 3561-134 | Attainable Data Rate Downstream | x | |
| 3561-135 | Maximum Data Rate Upstream | x | |
| 3561-136 | Maximum Data Rate Downstream | x | |
| 3561-137 | Minimum Data Rate Upstream in low power state | x | |
| 3561-138 | Minimum Data Rate Downstream in low power state | x | |
| 3561-139 | Maximum Interleaving Delay Upstream | x | |
| 3561-140 | Actual interleaving Delay Upstream | x | |
| 3561-141 | Maximum Interleaving Delay Downstream | x | |
| 3561-142 | Actual interleaving Delay Downstream | x | |
| 3561-144 | Access loop encapsulation | x |
