summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDenys Fedoryshchenko <denys.f@collabora.com>2026-10-28 20:16:22 +0200
committerDenys Fedoryshchenko <denys.f@collabora.com>2026-10-28 20:16:22 +0200
commitf0577799d0591b738d6ec7ef83e4197ee7390f90 (patch)
tree7db3211e6625a06908fc70b0f4e0b824d5b56bb8 /docs
parent00d0d536eb40324cffd3857fc603bb6e1e15eb27 (diff)
downloadaccel-ppp-f0577799d0591b738d6ec7ef83e4197ee7390f90.tar.gz
accel-ppp-f0577799d0591b738d6ec7ef83e4197ee7390f90.zip
docs: identify PADR as the source of TR-101 attributes
Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/pppoe_radius.md2
1 files changed, 1 insertions, 1 deletions
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.