[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2021-06-30 Thread Dan Streetman
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904549 Title:

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2021-03-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: netplan.io (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpa

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-30 Thread Benjamin Allot
Sadly, the journalctl logs don't go back that far now. It failed on a baremetal server, not a cloud. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904549 Title: MTU is

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-26 Thread Lukas Märdian
This looks kind of similar to LP: #1888726 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904549 Title: MTU is not set on vlan interface Status in netplan: New Status

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-23 Thread Dan Streetman
I can't reproduce it, on a VM with similar config the vlan does get the right mtu. can you provide your systemd-networkd journal log? Is there a specific environment (e.g. specific cloud) this fails in? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug not

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-23 Thread Benjamin Allot
Hello, I don't need it on bond-manlan for sure (MTU 1500 on this one and its VLANs), but I read in several place that setting MTU on the bond would also set it on interface members. And that indeed worked correctly. As I said, I think the issue is definitely more in the udevd/networkd part (rem

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-23 Thread Dimitri John Ledkov
this could be udevd/networkd bug which both fiddle with mtu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1904549 Title: MTU is not set on vlan interface Status in netp

[Touch-packages] [Bug 1904549] Re: MTU is not set on vlan interface

2020-11-23 Thread Dimitri John Ledkov
I wonder if you need more mtu settings on: * ens10f2 * ens10f3 * bond-manlan I don't think that MTU is allowed to be higher on a vlan, than on bond- man, than on physical interfaces. Why did you not set mtu: 9000 on bond- manlan? however that does not explain how come the vlans on top of bond-co