touch-packages team mailing list archive

[Jorge Niedbalski <1382054@xxxxxxxxxxxxxxxxxx>]

** 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=<vlanname>:<phydevice>

  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