Doing some experiments this seems to be working with netplan.io 0.100 in
Groovy. No matter if 'match.macaddress' is set or not on my local eth
interface.
As far as I can tell the fix was released with netplan 0.99 in Focal
final and was SRU'ed to Bionic as well.
(https://github.com/CanonicalLtd/ne
** Tags added: fr-445
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
https://bugs.launchpa
Why does this bug title refer to "private" ethernet adapters? It sounds
like you're saying the problem is much more general than this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
M
What prevent the generator to use Match/Name instead of
Match/OriginalName by default in .link file like it does for generated
.network files ?
As the few properties that may require a match on the original name
(like set-name) should already use a match directive anyway, so it
should not be an is
Still broken in 20.04 beta. This is a real shame…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug
@cyphermox Need to confirm this on focal daily ... we still need a "match:
macaddress" for setting MTU.
This is really a show stopper when cloning servers with virtualization and
containerization an new MAC.
Working with VLANs this is an essential setting for getting networking before
config mgm
This bug is also affecting 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
https://bu
** Tags added: id-5ddbf947fc883b102e714c12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
Any updates for bionic? We would strongly need this fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about
Still broken on 18.04.3 with netplan 0.98-0ubuntu1~18.04.1 and systemd
237-3ubuntu10.31.
With dhcp set to false, use-mtu seems to be useless. The only affordable
workaround I found is to create an override .link file that only matches
by mac address and set the MTU. For example:
[Match]
MACAddres
Still broken on 18.04.03 (netplan 0.97).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
ht
Can we have a status on this? I can also confirm that the suggested
workaorund works, but this should be fixed anyhow, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not app
Marking this invalid for cloud-init per netplan symptoms 'fixed' in
https://bugs.launchpad.net/netplan/+bug/1807273 look like it might be
the same case here with no change to cloud-init
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are
Clearing up bug statuses: We'll fix this for 18.04 and above, but first
it needs to land in the development release. Won't Fix is for the
releases before 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
That is a different issue we're solving elsewhere. You should be able to
override the UseMTU= field.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: netplan.io (Ubuntu)
Stat
Please see if this is solved by the fix for
https://bugs.launchpad.net/netplan/+bug/1807273 (setting use-mtu: false)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on p
I'm having a similar issue where setting the MTU to 1500 and using a match on
mac address does not stick. This is on a EC2 T2.Medium instance. Actual
configuration from a dev server:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 12:0f:ae:49:5d:06
mtu: 1500
I'm having a similar issue where setting the MTU to 1500 and using a match on
mac address does not stick. This is on a EC2 T2.Medium instance. Actual
configuration from a dev server:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 12:0f:ae:49:5d:06
mtu: 1500
Logs were added for cloud-init, so marking the cloud-init task back to
'new'.
** Changed in: cloud-init
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
I just got bit by this one too.
This is frustrating since the top two (for me) Google hits for "ubuntu netplan
mtu" both come from official Ubuntu sources, and both provide broken solutions:
https://blog.ubuntu.com/2017/12/01/ubuntu-bionic-netplan
https://blog.ubuntu.com/2017/07/05/quick-and-eas
I have the same here.
Netplan creates .link with
[Match]
OriginalName=ens4
Which can't be used since the network interface was already renamed
[...]
Jul 02 15:46:09 eolebase kernel: virtio_net virtio1 ens4: renamed from eth0
[...]
Jul 02 15:46:09 eolebase systemd-udevd[310]: Config file
/run/s
Hi Daniel,
Thank you for clarifying! I didn't see that was already a known issue.
Best,
Andrew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet inte
Hi Andy,
This is a known issue - after giving backends a chance to bring up network
interfaces, netplan apply will iterate over interfaces that are still down,
unbind them from their driver and rebind them. This can cause renaming of
the interface.
In general, adding "set-name: ens7" to your YAML
Matching by MAC address corrects the MTU issue on both Ubuntu 17.10 and
Ubuntu 18.04.
I noticed one side effect though - this happened on fresh Ubuntu 17.10
and Ubuntu 18.04 installs. After adding the "match: ... macaddress: ..."
parts to the YAML file, running "netplan apply" caused the "ens7" de
Adding requested file.
** Attachment added: "cloud-init collect-logs output file"
https://bugs.launchpad.net/netplan/+bug/1724895/+attachment/5136750/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Can you run cloud-init collect-logs in your instance and attach the
tarfile (cloud-init.tar.gz in the current working directory).
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Incomplete
--
You received this bug notification because
Glad that helped. I'm confused as to why cloud-init doesn't add the mac
addresses - it does in my VMs. Let's ask them; I'll add them to the bug.
** Description changed:
+ == cloud-init query ==
+
+ Cloud-init isn't adding MAC addresses in the match stanza for various
+ network interfaces in /et
Yup, adding a match on MAC seems to work. It would be nice if whatever
sets up the default /etc/netplan/50-cloud-init.yaml included the match
on MAC?
rsa@tppjoe03:~$ ifconfig
eno1: flags=4163 mtu 1500
inet 10.2.0.203 netmask 255.255.255.0 broadcast 10.2.0.255
inet6 fe80::aa1e:8
It should work if you match by MAC address. It's a messy interaction with
udev, as I understand it. Could you try matching by MAC and seeing if that
works?
We should definitely document it better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Apparently this was not fixed for Ubuntu 18.04 release?
rsa@tppjoe01:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_R
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
https://bugs.launchpa
Confirmed that this is still an issue in bionic (beta 2, all packages
updated), 0.36.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
T
So the only thing I see in the logs that looks suspicious is:
Jan 30 13:30:49 bridgevm systemd-udevd[376]: Config file
/run/systemd/network/10-netplan-br0devs.link matches device based on
renamed interface name 'ens8', ignoring
(my setup is explained in
https://bugs.launchpad.net/ubuntu/+source/n
Still happening on 0.32~17.10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage notifications about this bug go to:
https://bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nplan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on private ethernet interfaces
To manage not
36 matches
Mail list logo
