Network Settings Configuration Window Confusion

[Shaggy1444]

What Happened?

Using the network settings window is confusing and does not work as seem less-ly.

1. In order to configure different connections by interface type you must locate it by accessing the Wireless selection, then clicking on Edit Connections.
2. If you test different network connection configurations, because that's your job, you have to create whatever connections you need for either interface types, but, in order to test them, you must prioritize the connection(s) you want tested in order for them to be the active one(s) you wish to work with - this is horrendously confusing.
3. VLan(s) on a WiFi interface do not work.
4. You can associate a VLan with a WiFi interface and the interface will get an IP address from a DHCP server, however, the VLan interface does not.

All necessary components for supporting VLan is installed on the client Laptop.

vlan/noble,now 2.0.5ubuntu5 all [installed]

Steps to Reproduce

1. Open System Settings
2. Select Network
3. Click on Wireless
4. Click on Edit Connections
5. Either create or edit a network connection type (Interface or WiFi)

Output from VLan configuration from /etc/netplan

WiFi Device:

network:
version: 2
wifis:
NM-3167e93c-5dc0-470c-8aaa-33907e7ba681:
renderer: NetworkManager
match:
name: "wlp7s0"
macaddress: "30:yy:6B:zz:mm:nn"
dhcp4: true
ipv6-address-generation: "stable-privacy"
access-points:
"xxxxxxxxxxx":
auth:
key-management: "psk"
password: "bbbbbbbbbbb"
networkmanager:
uuid: "3167e93c-5dc0-470c-8aaa-33907e7ba681"
name: "xxxxxxxxxxx"
passthrough:
connection.autoconnect-priority: "1"
connection.timestamp: "1742419682"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
networkmanager:
uuid: "3167e93c-5dc0-470c-8aaa-33907e7ba681"
name: "xxxxxxxxxxx"

VLan WiFi Device:

network:
version: 2
vlans:
Vlan50:
renderer: NetworkManager
dhcp4: true
ipv6-address-generation: "stable-privacy"
id: 50
link: "3167e93c-5dc0-470c-8aaa-33907e7ba681"
networkmanager:
uuid: "924c8826-42f1-48c8-9e4e-7c67cd802a05"
name: "VLAN WiFi connection"
passthrough:
connection.autoconnect-priority: "12"
ethernet.: ""
vlan.flags: "1"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy.: ""

Expected Behavior

Configurations should be able to be set by simply clicking which one(s) should be active on Network Connections sub-window.
This allows for multiple configurations to be created and selected. So if a VLan test is needed with either an Ethernet or WiFi interface, this can be easily done in this window.

Linux Networking VLans should just work with either interface type.

OS Version

8.x (Circe)

Session Type

Classic Session (X11, This is the default)

Software Version

Latest release (I have run all updates)

Log Output

Tracing item 4 (above) back to the DHCP server gives some indication of the failure.

Request(s) to the DHCP server:

- the request is sent from the server back to the client but is somehow rejected (see Client Initiation and Rejection below):
 
2025-03-19T18:02:45-04:00	Informational	kea-dhcp4	INFO [kea-dhcp4.packets.0xfc4d9416d00] DHCP4_PACKET_SEND [hwtype=1 30:yy:6B:zz:mm:nn], cid=[01:30:yy:6B:zz:mm:nn], tid=0xb2105ed0: trying to send packet DHCPOFFER (type 2) from 192.168.50.1:67 to 192.168.50.29:68 on interface vlan01	
2025-03-19T18:02:45-04:00	Informational	kea-dhcp4	INFO [kea-dhcp4.leases.0xfc4d9416d00] DHCP4_LEASE_OFFER [hwtype=1 30:yy:6B:zz:mm:nn], cid=[01:30:yy:6B:zz:mm:nn], tid=0xb2105ed0: lease 192.168.50.29 will be offered	
2025-03-19T18:02:45-04:00	Informational	kea-dhcp4	INFO [kea-dhcp4.packets.0xfc4d9416d00] DHCP4_PACKET_RECEIVED [hwtype=1 30:yy:6B:zz:mm:nn], cid=[01:30:yy:6B:zz:mm:nn], tid=0xb2105ed0: DHCPDISCOVER (type 1) received from 0.0.0.0 to 255.255.255.255 on interface vlan01	
2025-03-19T18:02:45-04:00	Informational	kea-dhcp4	INFO [kea-dhcp4.dhcp4.0xfc4d9416d00] DHCP4_QUERY_LABEL received query: [hwtype=1 30:yy:6B:zz:mm:nn], cid=[01:30:yy:6B:zz:mm:nn], tid=0xb2105ed0

Client Initiation and Rejection:

2025-03-19T18:02:14.066507-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0664] device (Vlan50): Activation: starting connection 'VLAN WiFi connection' (924c8826-42f1-48c8-9e4e-7c67cd802a05)
2025-03-19T18:02:14.066748-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0666] device (Vlan50): carrier: link connected
2025-03-19T18:02:14.066924-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0668] device (Vlan50): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2025-03-19T18:02:14.067545-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0674] device (Vlan50): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2025-03-19T18:02:14.068009-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0679] device (Vlan50): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
2025-03-19T18:02:14.068374-04:00 IManDisL NetworkManager[1318]: <info>  [1742421734.0682] dhcp4 (Vlan50): activation: beginning transaction (timeout in 45 seconds)
2025-03-19T18:02:59.038704-04:00 IManDisL NetworkManager[1318]: <info>  [1742421779.0378] device (Vlan50): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
2025-03-19T18:02:59.040527-04:00 IManDisL NetworkManager[1318]: <warn>  [1742421779.0394] device (Vlan50): Activation: failed for connection 'VLAN WiFi connection'
2025-03-19T18:02:59.040899-04:00 IManDisL NetworkManager[1318]: <info>  [1742421779.0402] device (Vlan50): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
2025-03-19T18:02:59.048776-04:00 IManDisL NetworkManager[1318]: <info>  [1742421779.0486] dhcp4 (Vlan50): canceled DHCP transaction
- this goes on-an-on until you disable the VLan interface

Hardware Info

Physical Laptop using WiFi --> Wireless Router --> Network Switch (VLan) --> Proxmox VE Server (VLan) --> OPNsense VM (VLan) --> ISP Net

-the VLan tagging works as we see from the DHCP Server log above that the right network IP segment is targeted - 192.168.50.0/24

[Shaggy1444]

Update 03/20/2025:

Tested with the Ethernet Interface and DHCP assigned the VLan an IP address matching the subnet.
This does not work with the WiFi interface however.

[Shaggy1444]

Wow! Five days, no takers!