vlan mtu not set

C

crispyduck

New Member
Feb 17, 2022
16
0
1
40
I have a strange issue, that the mtu size of vlans are not set.

My /etc/network/interfaces:
Code: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto ens3f0
iface ens3f0 inet static
    address 10.99.99.61/24
    up ip route add 10.99.99.62/32 dev ens3f0
    down ip route del 10.99.99.62/32
#Coro link to sto2

auto ens3f1
iface ens3f1 inet static
    address 10.99.99.61/24
    up ip route add 10.99.99.63/32 dev ens3f1
    down ip route del 10.99.99.63/32
#Coro link to sto3

auto ens4f0
iface ens4f0 inet manual
    mtu 9000
#Storage link to sto2

auto ens4f1
iface ens4f1 inet manual
    mtu 9000
#Storage link to sto2

auto ens4f2
iface ens4f2 inet manual
    mtu 9000
#Storage link to sto3

auto ens4f3
iface ens4f3 inet manual
    mtu 9000
#Storage link to sto3

auto enp8s0f0
iface enp8s0f0 inet manual
    mtu 9000
#Uplink 1

auto enp8s0f1
iface enp8s0f1 inet manual
    mtu 9000
#Uplink 2

auto ens2f0
iface ens2f0 inet manual
    mtu 9000
#Uplink 3

auto ens2f1
iface ens2f1 inet manual
    mtu 9000
#Uplink 4

auto enp8s0f0.1111
iface enp8s0f0.1111 inet manual
    mtu 9000
#VLAN 1111 on Uplink1

auto enp8s0f1.1112
iface enp8s0f1.1112 inet manual
    mtu 9000
#VLAN 1112 on Uplink2

auto ens2f0.1113
iface ens2f0.1113 inet manual
    mtu 9000
#VLAN 1113 on Uplink3

auto ens2f1.1114
iface ens2f1.1114 inet manual
    mtu 9000
#VLAN 1114 on Uplink4

auto bond1
iface bond1 inet static
    address 10.88.88.61/24
    bond-slaves ens4f0 ens4f1
    bond-miimon 100
    bond-mode balance-rr
    mtu 9000
    up ip route add 10.88.88.62/32 dev bond1
    down ip route del 10.88.88.62/32
#Storage link to sto2

auto bond2
iface bond2 inet static
    address 10.88.88.61/24
    bond-slaves ens4f2 ens4f3
    bond-miimon 100
    bond-mode balance-rr
    mtu 9000
    up ip route add 10.88.88.63/32 dev bond2
    down ip route del 10.88.88.63/32
#Storage link to sto3

auto bond0
iface bond0 inet manual
    bond-slaves enp8s0f0 enp8s0f1 ens2f0 ens2f1
    bond-miimon 100
    bond-mode balance-tlb
    mtu 9000
#Default Uplink Bond

auto vmbr1111
iface vmbr1111 inet manual
    bridge-ports enp8s0f0.1111
    bridge-stp off
    bridge-fd 0
    mtu 9000
#VLAN111 Bridge

auto vmbr1112
iface vmbr1112 inet manual
    bridge-ports enp8s0f1.1112
    bridge-stp off
    bridge-fd 0
    mtu 9000
#VLAN112 Bridge

auto vmbr1113
iface vmbr1113 inet manual
    bridge-ports ens2f0.1113
    bridge-stp off
    bridge-fd 0
    mtu 9000
#VLAN113 Bridge

auto vmbr1114
iface vmbr1114 inet manual
    bridge-ports ens2f1.1114
    bridge-stp off
    bridge-fd 0
    mtu 9000
#VLAN114 Bridge

auto vmbr0
iface vmbr0 inet manual
    bridge-ports bond0
    bridge-stp off
    bridge-fd 0
    bridge-vlan-aware yes
    bridge-vids 2-4094
    mtu 9000
#Default VM Bridge

auto vmbr0.1708
iface vmbr0.1708 inet static
    address 10.17.8.61/24
    gateway 10.17.8.1
#PVE Mgmt

output of ip link show:
Code: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:15:17:61:84:96 brd ff:ff:ff:ff:ff:ff
    altname enp6s0f0
3: ens4f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
    link/ether 16:3b:48:e3:bf:88 brd ff:ff:ff:ff:ff:ff permaddr 00:19:99:9e:f9:a9
    altname enp5s0f0
4: ens3f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:15:17:61:84:97 brd ff:ff:ff:ff:ff:ff
    altname enp6s0f1
5: ens4f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
    link/ether 16:3b:48:e3:bf:88 brd ff:ff:ff:ff:ff:ff permaddr 00:19:99:9e:f9:aa
    altname enp5s0f1
6: ens4f2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
    link/ether 76:5b:75:c6:cd:45 brd ff:ff:ff:ff:ff:ff permaddr 00:19:99:9e:f9:ab
    altname enp5s0f2
7: ens4f3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
    link/ether 76:5b:75:c6:cd:45 brd ff:ff:ff:ff:ff:ff permaddr 00:19:99:9e:f9:ac
    altname enp5s0f3
8: ens2f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:5e:b7:aa brd ff:ff:ff:ff:ff:ff
    altname enp7s0f0
9: ens2f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:5e:b7:ab brd ff:ff:ff:ff:ff:ff
    altname enp7s0f1
10: enp8s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff permaddr 00:19:99:83:ea:04
11: enp8s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 00:19:99:83:ea:05 brd ff:ff:ff:ff:ff:ff
25: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue master fwbr100i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:00:63:2d:a3:74 brd ff:ff:ff:ff:ff:ff link-netnsid 0
26: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether da:44:a0:be:98:50 brd ff:ff:ff:ff:ff:ff
27: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 4e:f5:a9:37:95:96 brd ff:ff:ff:ff:ff:ff
28: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue master fwbr100i0 state UP mode DEFAULT group default qlen 1000
    link/ether 6a:c4:bf:76:83:56 brd ff:ff:ff:ff:ff:ff
289: veth102i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether fe:08:5d:ae:5f:5a brd ff:ff:ff:ff:ff:ff link-netnsid 1
290: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether fe:e2:12:f9:5e:39 brd ff:ff:ff:ff:ff:ff
291: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 46:b5:61:19:0c:1f brd ff:ff:ff:ff:ff:ff
292: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue master fwbr102i0 state UP mode DEFAULT group default qlen 1000
    link/ether 92:7b:10:2c:4e:50 brd ff:ff:ff:ff:ff:ff
566: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 16:3b:48:e3:bf:88 brd ff:ff:ff:ff:ff:ff
567: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 76:5b:75:c6:cd:45 brd ff:ff:ff:ff:ff:ff
568: enp8s0f0.1111@enp8s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1111 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
569: vmbr1111: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 00:19:99:83:ea:04 brd ff:ff:ff:ff:ff:ff
570: enp8s0f1.1112@enp8s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1112 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
571: vmbr1112: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 00:19:99:83:ea:05 brd ff:ff:ff:ff:ff:ff
572: ens2f0.1113@ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1113 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
573: vmbr1113: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:5e:b7:aa brd ff:ff:ff:ff:ff:ff
574: ens2f1.1114@ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1114 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
575: vmbr1114: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:5e:b7:ab brd ff:ff:ff:ff:ff:ff
576: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
577: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff
578: vmbr0.1708@vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 92:15:1d:6e:09:62 brd ff:ff:ff:ff:ff:ff

Why is the mtu to

enp8s0f0.1111, enp8s0f0.1112, ens2f0.1113 and ens2f1.1114 not applied?

setting it manually with " ip link set dev vmbr1111 mtu 9000" works.

Br
cd
 
Hi,

I can guess, that you can have a phisical interface with mtu 9000, but you can not have the same 9000 mtu on a vlan interface(9000 - vlan header size).

An this will happen on pmx node but also on the your switch ports.

Even you can setup what mtu do you like from shell, this will create some problems (like mtu fragmentation)

Good luck / Bafta !
 
Hi!

@spirit yes, ifupdown2

@guletz do you men I need a higher mtu on the parent/physical if? I thought linux networking should be aware of the vlan header size?
I am actually testing it with NFS and at the moment I don't see any problems with fragmentation.

Br,
cd
 
I have tested on my side, it's working with with a simple

Code: 
auto eno2
iface eno2 inet manual
        mtu 9000

auto eno2.100
iface eno2.100 inet manual
        mtu 9000

auto vmbr2
iface vmbr2 inet manual
        bridge-ports eno2
        mtu 9000

[/QUOTE]

as you use ifupdown2, can you send the result of:
"
 ifup enp8s0f0.1111 -d
"

?

Also, I see than enp8s0f0 also enslaved in bond0.   Why don't you use bond0.1111  ?

Also, vmbr0 have  bond0, but vmbr0 is a vlan aware bridge. 

and vmbr1111 is non vlanware with  enp8s0f0.1111

Mixing vlan-aware && non vlan-aware bridge with same physical interfaces, with mixing bond/non-bond is really a bad Idea I think.


Why don't use simply use the vmbr0 (vlan-aware or non-vlan aware, as you want),  and define vlan on the vm nic level ?
 
I just retested, removing the stp part, but still no mtu 9000 after networking restart.

Here the output from ifup enp8s0f0.1111 -d:
Code: 
root@sepp-sto-03:~# ifup enp8s0f0.1111 -d
debug: args = Namespace(all=False, iflist=['enp8s0f0.1111'], verbose=False, debug=True, quiet=False, CLASS=None, withdepends=False, perfmode=False, nocache=False, excludepats=None, interfacesfile=None, interfacesfileformat='native', type=None, syntaxcheck=False, skipupperifaces=False, force=False, syslog=False, noact=False, printdependency=None, noaddons=False, version=None, nldebug=False)
debug: creating ifupdown object ..
info: requesting link dump
info: requesting address dump
info: requesting netconf dump
debug: nlcache: reset errorq
debug: {'use_daemon': 'no', 'template_enable': '1', 'template_engine': 'mako', 'template_lookuppath': '/etc/network/ifupdown2/templates', 'default_interfaces_configfile': '/etc/network/interfaces', 'disable_cli_interfacesfile': '0', 'addon_syntax_check': '0', 'addon_scripts_support': '1', 'addon_python_modules_support': '1', 'multiple_vlan_aware_bridge_support': '1', 'ifquery_check_success_str': 'pass', 'ifquery_check_error_str': 'fail', 'ifquery_check_unknown_str': '', 'ifquery_ifacename_expand_range': '0', 'link_master_slave': '0', 'delay_admin_state_change': '0', 'ifreload_down_changed': '0', 'addr_config_squash': '0', 'ifaceobj_squash': '0', 'adjust_logical_dev_mtu': '1', 'state_dir': '/run/network/'}
info: loading builtin modules from ['/usr/share/ifupdown2/addons']
info: module ppp not loaded (module init failed: no /usr/bin/pon found)
info: module batman_adv not loaded (module init failed: no /usr/sbin/batctl found)
debug: bridge: using reserved vlan range (0, 0)
debug: bridge: init: warn_on_untagged_bridge_absence=False
debug: bridge: init: vxlan_bridge_default_igmp_snooping=None
debug: bridge: init: arp_nd_suppress_only_on_vxlan=False
debug: bridge: init: bridge_always_up_dummy_brport=None
info: executing /sbin/sysctl net.bridge.bridge-allow-multiple-vlans
debug: bridge: init: multiple vlans allowed True
info: module mstpctl not loaded (module init failed: no /sbin/mstpctl found)
info: executing /bin/ip rule show
info: executing /bin/ip -6 rule show
info: module ethtool not loaded (module init failed: /sbin/ethtool: not found)
info: address: using default mtu 1500
info: address: max_mtu undefined
info: executing /usr/sbin/ip vrf id
info: mgmt vrf_context = False
info: dhclient: dhclient_retry_on_failure set to 0
info: executing /bin/ip addr help
info: address metric support: OK
info: module ethtool not loaded (module init failed: /sbin/ethtool: not found)
info: module ppp not loaded (module init failed: no /usr/bin/pon found)
info: module mstpctl not loaded (module init failed: no /sbin/mstpctl found)
info: module batman_adv not loaded (module init failed: no /usr/sbin/batctl found)
info: looking for user scripts under /etc/network
info: loading scripts under /etc/network/if-pre-up.d ...
info: loading scripts under /etc/network/if-up.d ...
info: loading scripts under /etc/network/if-post-up.d ...
info: loading scripts under /etc/network/if-pre-down.d ...
info: loading scripts under /etc/network/if-down.d ...
info: loading scripts under /etc/network/if-post-down.d ...
info: using mgmt iface default prefix eth
info: processing interfaces file /etc/network/interfaces
debug: bond1: evaluating port expr '['ens4f0', 'ens4f1']'
debug: bond2: evaluating port expr '['ens4f2', 'ens4f3']'
debug: bond0: evaluating port expr '['enp8s0f0', 'enp8s0f1', 'ens2f0', 'ens2f1']'
debug: vmbr1111: evaluating port expr '['enp8s0f0.1111']'
debug: vmbr1112: evaluating port expr '['enp8s0f1.1112']'
debug: vmbr1113: evaluating port expr '['ens2f0.1113']'
debug: vmbr1114: evaluating port expr '['ens2f1.1114']'
debug: vmbr0: evaluating port expr '['bond0']'
debug: scheduling '['pre-up', 'up', 'post-up']' for ['enp8s0f0.1111']
debug: dependency graph {
        lo : []
        ens3f0 : []
        ens3f1 : []
        ens4f0 : []
        ens4f1 : []
        ens4f2 : []
        ens4f3 : []
        enp8s0f0 : []
        enp8s0f1 : []
        ens2f0 : []
        ens2f1 : []
        enp8s0f0.1111 : ['enp8s0f0']
        enp8s0f1.1112 : ['enp8s0f1']
        ens2f0.1113 : ['ens2f0']
        ens2f1.1114 : ['ens2f1']
        bond1 : ['ens4f1', 'ens4f0']
        bond2 : ['ens4f3', 'ens4f2']
        bond0 : ['ens2f1', 'ens2f0', 'enp8s0f0', 'enp8s0f1']
        vmbr1111 : ['enp8s0f0.1111']
        vmbr1112 : ['enp8s0f1.1112']
        vmbr1113 : ['ens2f0.1113']
        vmbr1114 : ['ens2f1.1114']
        vmbr0 : ['bond0']
        vmbr0.1708 : ['vmbr0']
}
debug: enp8s0f0.1111: found dependents ['enp8s0f0']
info: enp8s0f0.1111: running ops ...
debug: enp8s0f0.1111: pre-up : running module openvswitch
debug: enp8s0f0.1111: pre-up : running module openvswitch_port
debug: enp8s0f0.1111: pre-up : running module xfrm
debug: enp8s0f0.1111: pre-up : running module link
debug: enp8s0f0.1111: pre-up : running module bond
debug: enp8s0f0.1111: pre-up : running module vlan
debug: enp8s0f0.1111: pre-up : running module vxlan
debug: enp8s0f0.1111: pre-up : running module usercmds
debug: enp8s0f0.1111: pre-up : running module bridge
info: vmbr1111: applying bridge port configuration: ['enp8s0f0.1111']
info: vmbr1111: enp8s0f0.1111: bridge-pathcosts: no configuration detected, resetting to default 100
debug: (cache 4)
info: enp8s0f0.1111: netlink: ip link set dev enp8s0f0.1111: bridge port attributes
debug: attributes: {3: 100}
debug: enp8s0f0.1111: pre-up : running module bridgevlan
debug: enp8s0f0.1111: pre-up : running module tunnel
debug: enp8s0f0.1111: pre-up : running module vrf
info: vrf: syncing table map to /etc/iproute2/rt_tables.d/ifupdown2_vrf_map.conf
info: vrf: dumping iproute2_vrf_map
info: {}
debug: enp8s0f0.1111: pre-up : running module address
info: executing /sbin/sysctl net.mpls.conf.enp8s0f0/1111.input=0
info: writing "9000" to file /sys/class/net/enp8s0f0.1111/mtu
debug: enp8s0f0.1111: up : running module dhcp
debug: enp8s0f0.1111: up : running module address
debug: enp8s0f0.1111: up : running module addressvirtual
debug: enp8s0f0.1111: up : running module usercmds
debug: enp8s0f0.1111: up : running script /etc/network/if-up.d/postfix
info: executing /etc/network/if-up.d/postfix
debug: enp8s0f0.1111: up : running script /etc/network/if-up.d/chrony
info: executing /etc/network/if-up.d/chrony
debug: enp8s0f0.1111: post-up : running module usercmds
debug: enp8s0f0.1111: statemanager sync state pre-up
debug: saving state ..
info: exit status 0


The reason for this strange config is that I have running a LXC with NFS trunking, I want/need both, a bond on top of the 4 physical NICs for several VMs and PVE Mgmt as well as the 4 VLANs 1111-1114 dedicated to a specific uplink.
If thee are better ways to archive this suggestions are welcome.

So far this works well. I found yesterday only the problem with the MTU as my NFS LXC where no more reachable after I changed them to mtu 9000, after looking on the applied network config the reason for this was clear. When setting it manually with ip link everything works fine.

The overall setup is the following:
3 nodes in a PVE cluster. PVE and some space for LXCs on a HW RAID1, and a big zpool for sharing via NFS.
n1 and n2 are the primary storage providers exporting the ZFS datasets to other hypervisors,.... backup/replication is done via zrep from n1 and n2 to n3. In case of maintenance or failure I can simply migrate the nfs VMs to n3 and it will export the latest replicated snapshot from there.
Actually doing the zrep failover manually, but I will change this to some hook scripts toing it automatically on nfs vm migration.
And as I am limited to 1g network, I am doing all this crazy nfs trunking and mesh networking with rr.

Maybe a bit complicated setup for a pseudo storage cluster, but with 1g this was the best solution I found having good performance and a hot backup for maintenance tasks or disaster failover.

I love ZFS+NFS for my shared storage mainly for some Lab ESXi hosts, not the best performance, but great for snapshotting and cloning a couple of ESXi VMs.
Ceph cluster would be nice, but with my 1g network I decided to go this way and spread the load over two nodes with a 3rd as backup/failover.
 
Okay, but then it should work with Interface MTU 9000 and VLAN MTU 8000, but it is not set in either way.

Br,
cd
 
info: writing "9000" to file /sys/class/net/enp8s0f0.1111/mtu
Click to expand...
so, here ifupdown2 is trying to set mtu to 9000 on enp8s0f0.1111. I don't known why it's not working.


do you have tried withtout vlan-aware on vmbr0 ?

Code: 
auto vmbr0
iface vmbr0 inet manual
    bridge-ports bond0
    bridge-stp off
    bridge-fd 0
    mtu 9000
#Default VM Bridge

auto vmbr0v1708
iface vmbr0v1708 inet static
    address 10.17.8.61/24
    gateway 10.17.8.1
    mtu 1500
#PVE Mgmt
 
Hi, removing the vlan-aware makes no difference. All other br and if vlan-br it is working, only on the 4 vlans the MTU is not set.

Maybe I have overseen it before, executing "ifup enp8s0f0.1111" sets the MTU correctly, only on networking start/restart it is not set for the four vlan interfaces.

Any Idea how to further debug this?

Thanks so far,
cd
 
crispyduck said:
Hi, removing the vlan-aware makes no difference. All other br and if vlan-br it is working, only on the 4 vlans the MTU is not set.

Maybe I have overseen it before, executing "ifup enp8s0f0.1111" sets the MTU correctly, only on networking start/restart it is not set for the four vlan interfaces.

Any Idea how to further debug this?

Thanks so far,
cd
Click to expand...
if you have local access to the server,
the best way could be to stop/disable networking service,

then start interfaces with ifupdown2 in debug mode

#ifup -a -d


and check in the log if ifupdown2 is trying to set the mtu.
if yes, and if you don't see the mtu on the interface, it could be a nic driver bug refusing to set the mtu.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back