oh my, ifupdown/vlan is still in use?
you appear to be doing "QinQ" (802.1ad) not 802.1q. The ifupdown/vlan
'magic' detection of vlan interface naming wasn't designed to support
that; it only was designed to support 802.1q (see 'VLAN INTERFACES'
here: https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html )
Also, 'vlan 0' typically means 'untagged' (is it even valid to tag with
id 0?), so i'm not sure what exactly you want to do with a nested vlan
id 0 inside another vlan.
Finally, you should be using systemd-networkd. In Ubuntu, ifupdown has
long been deprecated and is no longer officially supported.
Anyway, if you *must* do things this way, try changing your interface
names to remove the dots; e.g. instead of 'ens19.1991.0' call it
'ens19_1991_0', and that should avoid all the ifupdown/vlan magic 'auto-
vlan' code that tries to detect in-name vlan ids and padding.
** Changed in: vlan (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722534
Title:
vlan naming scheme different between interfaces conf and run time
change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1722534/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
