From 1a01a619ab99640d015bef3f26fb2dbe5dd70e4c Mon Sep 17 00:00:00 2001 From: Christian Breunig Date: Sun, 8 Oct 2023 09:08:35 +0200 Subject: T5630: pppoe: allow to specify MRU in addition to already configurable MTU (cherry picked from commit 7090b69845a8d304d1608e18efef383082114f33) --- docs/configuration/interfaces/pppoe.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'docs/configuration/interfaces/pppoe.rst') diff --git a/docs/configuration/interfaces/pppoe.rst b/docs/configuration/interfaces/pppoe.rst index 6e922cfb..b37e95a2 100644 --- a/docs/configuration/interfaces/pppoe.rst +++ b/docs/configuration/interfaces/pppoe.rst @@ -143,6 +143,19 @@ PPPoE options set interfaces pppoe pppoe0 default-route-distance 220 +.. cfgcmd:: set interfaces pppoe mru + + Set the :abbr:`MRU (Maximum Receive Unit)` to `mru`. PPPd will ask the peer to + send packets of no more than `mru` bytes. The value of `mru` must be between 128 + and 16384. + + A value of 296 works well on very slow links (40 bytes for TCP/IP header + 256 + bytes of data). + + The default is 1492. + + .. note:: When using the IPv6 protocol, MRU must be at least 1280 bytes. + .. cfgcmd:: set interfaces pppoe idle-timeout