[pve-devel] [PATCH v3 pve-common 5/5] Inotify : add mtu option

[Alexandre DERUMIER]

>>Just every configuration, where you change /etc/network/interfaces in a 
>>way like: 
>>
>>------------ 
>>iface bond0 inet manual 
>>... 
>>slaves eno18 eno19 
>>mtu 9000 
>>------------ 
>>
>>without also writing the "mtu 9000" in the eno18 and eno19 sections. It 
>>will work, but every try of changing network configuration via GUI will 
>>fail with an error message. 


mmm,ok. I didn't known that's could work.
So setting mtu to bond device, force mtu to slaves too ?


----- Mail original -----
De: "Dennis Busch" <dennis.busch at stacktrace.de>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 3 Septembre 2018 12:28:34
Objet: Re: [pve-devel] [PATCH v3 pve-common 5/5] Inotify : add mtu option

> 
> Currently, I think that I'm using check_mtu only on child interfaces (bond,vlan,bridgeport). 
> @Denis : do you have a sample config where it's not working ? 
> 

Just every configuration, where you change /etc/network/interfaces in a 
way like: 

------------ 
iface bond0 inet manual 
... 
slaves eno18 eno19 
mtu 9000 
------------ 

without also writing the "mtu 9000" in the eno18 and eno19 sections. It 
will work, but every try of changing network configuration via GUI will 
fail with an error message.