| commit | 60e5ec7bad389e1f703538fde0c2d3feeb24bd52 | [log] [tgz] |
|---|---|---|
| author | Gustavo Silva <gsilva@furukawalatam.com> | Fri Feb 12 10:50:55 2021 -0300 |
| committer | Gustavo Silva <gsilva@furukawalatam.com> | Wed Mar 10 09:31:59 2021 -0300 |
| tree | 14cb72faa19343eff4500538e2bab240135f603a | |
| parent | 63e2ea0d6156dbceb1edec031a1014e025d408e6 [diff] |
[VOL-3661] PPPoE IA application - initial commit Change-Id: Idaf23f8736cba955fe8a3049b8fc9c85b3cd3ab9 Signed-off-by: Gustavo Silva <gsilva@furukawalatam.com>
As described in TR-101 Issue 2 - 3.9.2, the PPPoE Intermediate Agent supports the PPPoE access method and is a function placed on the Access Node in order to insert access loop identification.
The PPPoE Intermediate Agent intercepts all upstream PPPoE discovery stage packets, i.e. the PADI, PADR and upstream PADT packets, but does not modify the source or destination MAC address of these PPPoE discovery packets. Upon receipt of a PADI or PADR packet sent by the PPPoE client, the Intermediate Agent adds a PPPoE TAG to the packet to be sent upstream. The TAG contains the identification of the access loop on which the PADI or PADR packet was received. If a PADI or PADR packet exceeds the Ethernet MTU after adding the access loop identification TAG, the Intermediate Agent must drop the packet, and issue the corresponding PADO or PADS response with a Generic-Error TAG to the sender.