Comment 16 for bug 1988480

My feature request question is:

With this new ip= approach, all we can provide is:

ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip>

So, we can't install through a VLAN interface and/or through a lacp bond.

Back in d-i, we can use netcfg/use_vlan and netcfg/vlan_id through the installer cmdline, so as to configure a VLAN tagged interface and install over it, but apparently we can't do the same with subiquity. It would be nice to have this as a feature request for the future, for cases where the client switches won't allow untagged network traffic.

Also, the same applies for lacp. Sometimes the network ports are configured with lacp bond (802.3ad) and the switch won't let an interface be brought up unless it sends lacpdus. That feature is also missing in d-i, so although it would be nice to have, people have been able to get workarounds up to date.

That feature was discussed in:

Debian Bug report logs - #611250
please support network bonding
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250

In the Debian bug report that, someone even submitted a patch (see Message #39 received at <email address hidden>):

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39

However, I've looked into debian-installet netcfg tree and that patch has never been merged:

https://salsa.debian.org/installer-team/netcfg

It has also never landed into Ubuntu's netcfg package:

https://launchpad.net/ubuntu/+source/netcfg

So, it means that the netcfg/bonding, netcfg/bonding_mode and netcfg/bonding_slaves options that the patch adds, were never really implemented.

Not sure what your thoughts are, but sounds like good features to implement in the future.