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

2018-09-03 Thread Alexandre DERUMIER
out) - Mail original - De: "Klaus Darilion" À: "pve-devel" Envoyé: Lundi 3 Septembre 2018 15:47:06 Objet: Re: [pve-devel] [PATCH v3 pve-common 5/5] Inotify : add mtu option Not sure if this is relevant here: An OVS bridge automatically adjusts its MTU to the smal

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

2018-09-03 Thread Klaus Darilion
Not sure if this is relevant here: An OVS bridge automatically adjusts its MTU to the smallest MTU of all childs. This adjusting is done whenever an interface/port is added or removed. Ie adding an interface with small MTU automatically lowers the MTU of the OVS bridge. Hence, it actually does

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

2018-09-03 Thread Alexandre DERUMIER
ll have 1500 mtu. I'll make a bug report to ifupdown2, and improve my pve-common mtu patch. - Mail original - De: "aderumier" À: "Dennis Busch" Cc: "pve-devel" Envoyé: Lundi 3 Septembre 2018 13:14:33 Objet: Re: [pve-devel] [PATCH v3 pve-common 5

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

2018-09-03 Thread Alexandre DERUMIER
e: "Dennis Busch" À: "aderumier" , "pve-devel" 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)

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

2018-09-03 Thread Dennis Busch
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 ...

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

2018-08-28 Thread Alexandre DERUMIER
mon.git;a=blobdiff;f=src/PVE/INotify.pm;h=330085066f29f461329494084d7a654c0149e7a3;hp=201c97b1965a29650bc16f86619a2ebf407e49c9;hb=c27ef07ff57a0143ef9200ed8ee53401d46f727a;hpb=cebd1c85f0144628a24c61fa06f3602f78da3c61 - Mail original ----- De: "Wolfgang Bumiller" À: "Dennis Busch" Cc:

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

2018-08-28 Thread Wolfgang Bumiller
On Tue, Aug 28, 2018 at 12:02:27PM +0200, Dennis Busch wrote: > Hello Alexandre, > > this check is IMHO uneccessary as Debian inherites MTU from parent to child > interfaces. That is AFAIK officially documente behavior, so this check makes > it impossible to edit an interface that uses mtu

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

2018-08-28 Thread Dennis Busch
Hello Alexandre, this check is IMHO uneccessary as Debian inherites MTU from parent to child interfaces. That is AFAIK officially documente behavior, so this check makes it impossible to edit an interface that uses mtu definition only on parent devices. Best regards Dennis stacktrace GmbH

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

2018-07-04 Thread Alexandre Derumier
also check if mtu value is lower than parent interface fixme: vxlan interface should be 50bytes lower than outgoing interface we need to find which interface is used (unicast/multicast/frr) --- src/PVE/INotify.pm | 22 ++