From f0577799d0591b738d6ec7ef83e4197ee7390f90 Mon Sep 17 00:00:00 2001 From: Denys Fedoryshchenko Date: Wed, 28 Oct 2026 20:16:22 +0200 Subject: docs: identify PADR as the source of TR-101 attributes Signed-off-by: Denys Fedoryshchenko --- docs/pppoe_radius.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/pppoe_radius.md b/docs/pppoe_radius.md index edacdb7d..ba22426f 100644 --- a/docs/pppoe_radius.md +++ b/docs/pppoe_radius.md @@ -86,4 +86,4 @@ Note: The attribute ID and Vendor ID for the shaper are configurable in the `[sh PPPoE discovery tags (like Service-Name) are generally handled by the server configuration, but TR-101 (Broadband Forum) tags can be processed if `tr101` support is enabled. * **TR-101 Attributes** (Vendor: ADSL-Forum) - * accel-ppp can parse Agent-Circuit-Id and Agent-Remote-Id from PADO/PADR packets if they are present in Vendor-Specific tags, and these can be used for authentication or accounting logging. + * With `[pppoe] tr101=1`, accel-ppp extracts Agent-Circuit-Id and Agent-Remote-Id from TR-101 Vendor-Specific tags in client PADR packets and includes them in RADIUS authentication and accounting requests. PADO is a server response, not the source of these client tags. -- cgit v1.2.3