Hello,
I locally tested the recent addition of vlan support with a local trunk
port of a vlan-capable switch on a connected laptop. I did not perform a
full installation, but merely completed the network setup and tested it
in a debug shell. Observations:
For some reason network configuration succeeded on the trunk port even
when configured as a non-trunk one. The switch interprets untagged
traffic as if it were originating from the desired vlan but then sends
back traffic tagged. For some reason, the dhcp client picked up the
tagged traffic and correctly configured IPv4. pinging then (expectedly)
did not work. In another attempt where I correctly configured the trunk
port, networking just worked.
While walking through the test procedure, I found one message
suboptimal:
| If your network interface is directly connected to a VLAN trunk port,
| specifying a VLAN ID may be necessary to get a working connection.
This is presented after a user has chosen to be connected to a trunk
port. The available selection asks for a VLAN ID with no method to opt
out of providing a VLAN ID. I recommend changing the wording to be more
affirmative. Possible wording:
| To configure the network connection on the VLAN trunk port, please
| provide the desired VLAN ID.
Helmut