Public bug reported: In initramfs-tools manual, the vlan section indicates that it's possible to configure multiple VLAN.
> vlan tells to create a VLAN tagged device. Allows one to configure > one or multiple VLAN tagged devices using the > "vlan=$name.$id:$parent" syntax. E.g. "vlan=eth0.1:eth0" Op‐ > tional parameter for NFS root. I couldn't figure out the correct syntax for multiple VLAN interfaces however. There is indeed a loop `for v in $VLAN`[1] in the code, but the parsing doesn't support either spaces (vlan="eno1.123:eno1 eno2.456:eno2"), commas (vlan=eno1.123:eno1,eno2.456:eno2) or multiple definitions (vlan= eno1.123:eno1 vlan=eno2.456:eno2)[2]. I actually don't really need multiple VLAN, but I was trying to workaround the need to hardcode the name of the interface to support different hardware (I'm working on PXE Ubuntu deployment on a tagged VLAN). [1]: https://git.launchpad.net/ubuntu/+source/initramfs- tools/tree/scripts/functions?h=applied/ubuntu/noble#n369 [2]:https://git.launchpad.net/ubuntu/+source/initramfs- tools/tree/init?h=applied/ubuntu/noble#n159 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2085598 Title: Support for multiple VLANs with vlan=<name>.<dev> Status in initramfs-tools package in Ubuntu: New Bug description: In initramfs-tools manual, the vlan section indicates that it's possible to configure multiple VLAN. > vlan tells to create a VLAN tagged device. Allows one to configure > one or multiple VLAN tagged devices using the > "vlan=$name.$id:$parent" syntax. E.g. "vlan=eth0.1:eth0" Op‐ > tional parameter for NFS root. I couldn't figure out the correct syntax for multiple VLAN interfaces however. There is indeed a loop `for v in $VLAN`[1] in the code, but the parsing doesn't support either spaces (vlan="eno1.123:eno1 eno2.456:eno2"), commas (vlan=eno1.123:eno1,eno2.456:eno2) or multiple definitions (vlan= eno1.123:eno1 vlan=eno2.456:eno2)[2]. I actually don't really need multiple VLAN, but I was trying to workaround the need to hardcode the name of the interface to support different hardware (I'm working on PXE Ubuntu deployment on a tagged VLAN). [1]: https://git.launchpad.net/ubuntu/+source/initramfs- tools/tree/scripts/functions?h=applied/ubuntu/noble#n369 [2]:https://git.launchpad.net/ubuntu/+source/initramfs- tools/tree/init?h=applied/ubuntu/noble#n159 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2085598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
