You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use config device sections to set per-interface MTU.
The following snippets work for me:
config device
option name wlan0
option mtu 1511
config device
option name wlan1
option mtu 1512
Results in:
# ip link show wlan0 ; ip link show wlan1
166: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1511 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 04:f0:21:0f:78:bd brd ff:ff:ff:ff:ff:ff
175: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1512 qdisc noqueue master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 04:f0:21:0f:77:6e brd ff:ff:ff:ff:ff:ff
Please open the bug report again. Jo-Philipp Wich clearly you are not using openwrt default settings!!! The settings that also Luci manipulates with a default openwrt 19 install are:
config interface 'lan'
option type 'bridge'
option ifname 'eth1.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option mtu '9000'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
option peerdns '0'
option mtu '9000'
Waiting for a bugfix as the mtu does not change with these default luci manipulated settings.
n8v8R:
Chaos Calmer r47055 | target:mvebu/generic | description:OpenWrt omnia 15.05
OpenWRT latest stable
setting dev iface mtu according to https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg41851.html
config interface 'wl100'
option proto 'none'
option mtu '2000'
Bring the iface up and
ip l show wl100
displaying the MTU as 1500. Seems that either UCI is not parsing the setting or netifd neglecting it.Cross referencing OpenWRT forum https://forum.openwrt.org/t/how-to-set-mtu-on-bare-wireless-interface-using-config-uci/20164/3
and downstream bug ticket https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/211#note_93831
The text was updated successfully, but these errors were encountered: