[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
This bug was fixed in the package initramfs-tools - 0.133ubuntu9 --- initramfs-tools (0.133ubuntu9) eoan; urgency=medium * Add support for creating VLANs via vlan=eth0.1:eth0 on kernel commandline, and as VLAN= conf.d snippet. LP: #1382054 -- Dimitri John Ledkov Fri, 14 Jun 2019 14:46:05 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Fix Released Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Committed -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/368566 -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
@Martin Encrypted root is available in Ubuntu. -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
I will go with dracut syntax here: vlan=: And will only support the .id naming, e.g.: vlan=eth0.1:eth0 As i'd think dracut syntax is more popular, despite being a bit backwards parsing the pairs. With added support, that phydevice is activated as well on s390x. -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Milestone: None => ubuntu-19.06 -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
@SKOM: Thanks for providing the hook. Saved me a lot of time. It may be worth mentioning that the new VLAN interfaces have to be shut down before booting by a line like this in initramfs.conf: DROPBEAR_SHUTDOWN="eth0 eth0.1" I wonder, why this configuration is not available by default in stock Debian: Neither encrypted root nor VLAN is very unusual in a server configuration. Cheers, Martin -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
I wrote a hook to add a VLAN-Device to the initramfs, you can add in your /etc/initramfs-tools/initramfs.conf the following line: VLAN=: you can also add multiple devices: VLAN=": :" the hooks ans script are in the attachment. I use it to unlock a encrypted root partition over a vlan hinterface. Have fun.. :) ** Attachment added: "vlan.tar" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+attachment/5137284/+files/vlan.tar -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Tags added: canonical-bootstack -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Tags added: sts -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
Hi, I can confirm that it is often the case, and that it previously causes me headaches at installing debian/ubuntu distro via pxe on vlan tagged networks . Those where use of native vlan is reserved/forbiddenand where you must pass many mutualised switches. -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in “initramfs-tools” package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs&m=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+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