Open timur-davletshin opened 10 months ago
Interface mtu option should translate to pppd mtu/mru cli arguments.
The word 'should' is doing a lot of lifting here.
Shouldn't proto_pppoe_setup()
call to ppp_generic_setup()
pass mtu
also?
@jow-: for pppoe "should" is false. The MTU option needs to apply to the 'ethernet' interface responsible for the connection, if there is one.
The manpages for the pppoe.so
module list zero (direct) options for MTU.
https://www.man7.org/linux/man-pages/man8/pppd.8.html#PPPOE_OPTIONS
So two solutions here seem evident: either a) delete the GUI option, or b) remap it so that it applies to the underlying interface (less trivial).
Closed by 995d3a1801cf3b850e8c7c35937fbdd0526ff53e
I see luci-proto-ppp has returned MTU settings back. Can someone clarify what does this MTU settings do?
Can someone clarify what does this MTU settings do?
See
I see luci-proto-ppp has returned MTU settings back. Can someone clarify what does this MTU settings do?
Apparently not what one thinks it should do.
It is supposed to control the PPP MRU/MTU values which are independent from the underlying ethernet MTU. Due to a bug in netifd this option currently is inoperable, a fix is being worked on.
@jow- so the pppd's part working fine it's just 'Devices' tab which is broken?
No, netifd / the ppp protocol handler is broken, the fix for this will not happen in LuCI.
Generally there two ways to set up MTU. One is in the Devices tab (Luci UI) and the other one is in the Interfaces tab (I'm talking about PPPoE connection).
They correspond to respective parts of the configuration file:
/etc/config/network
:Actual behavior:
Only MTU in
device
section (or Devices tab) will actually apply to PPPoE connection. The other one ininterface
does nothing. Check can be done by ifconfig or directly via Luci UI.Expected behavior:
Remove duplicating (and non-functioning) MTU settings in PPPoE interface settings (Interfaces tab).
Note: I'm not talking about physical interface (eth0 in this example), only about pppoe-wan.