It's not impossible already to do VLANs with d-i currently (for anyone
reading this after a temporary work around until this is properly fixed)...
Step 1) Get to the screen where d-i presents you with a list of network
interfaces
Step 2) Go to VT2 (using alt-F2) and activate the console
Step 3) Add a VLAN interface to whichever physical interface you want it
on... ip link add link eno1 name eno1.42 type vlan id 42
Step 4) Go back to VT1 (using alt+F1) and choose to go 'Back' and then
forward by selecting 'Configure the network' to repopulate the list
Step 5) Pick the new VLAN interface until you're at the screen where
you'd normally pick 'Configure network manually...' (but don't pick this
option yet)
Step 6) Go BACK to VT2 (using alt-F2)
Step 7) Bring the physical and VLAN interfaces up... ip link set eno1
up; ip link set eno1.42 up
Step 8) Go BACK to VT1 (using alt+F1) and continue as normal
EASY!.. OK... FINE... I admit that is sarcasm. It's also laughable that
it's easier to get d-i to use PPPoE than it is a VLAN.
Now you might think to do the commands on VT2 all at once, but I find
once you've picked the network interface with d-i it'll bring the
interface down!
Also these instructions are useless if you're not configuring a static
IP as you'll have to be super quick before the autoconfiguration fails.
Lastly... (this is the main reason I'm adding to this bug report)...
Does the new patch discussed here address the fact that usually I find I
have to run this (AFTER the system has booted up for the first time)...
sed -i 's/allow-hotplug/auto/' /etc/network/interfaces
... and then reboot again before any networking works?
Because 'allow-hotplug' just doesn't cut it with VLAN interfaces... it
seems it must be 'auto'
Frankly I don't see why we don't use 'auto' in the default
/etc/network/interfaces (whether using a VLAN or not) as it covers
everything 'allow-hotplug' does but actually works in more cases.
Thoughts?
