Skip to content

fix(nm): support VLAN interfaces in NetworkManager backend - #30

Open
apostroll wants to merge 1 commit into
ProtonVPN:stablefrom
apostroll:fix/support-vlan-interfaces
Open

apostroll wants to merge 1 commit into
ProtonVPN:stablefrom
apostroll:fix/support-vlan-interfaces

Conversation

@apostroll

Copy link
Copy Markdown

NetworkManager VLAN interfaces (NM.DeviceType.VLAN / NM.SETTING_VLAN_SETTING_NAME) were previously excluded from physical device discovery and parent connection resolution.

When the primary network interface is a VLAN trunk (where the parent ethernet device has no default gateway and the active default route lives on a VLAN sub-interface like enp8s0.10), WireGuard connection setup failed with GatewayNotFoundError and timed out due to the killswitch dummy interface blocking reachability checks.

This adds NM.DeviceType.VLAN and NM.SETTING_VLAN_SETTING_NAME to the NetworkManager backend device filters and physical connection checks.

NetworkManager VLAN interfaces (NM.DeviceType.VLAN / NM.SETTING_VLAN_SETTING_NAME)
were previously excluded from physical device discovery and parent connection
resolution.

When the primary network interface is a VLAN trunk (where the parent ethernet
device has no default gateway and the active default route lives on a VLAN
sub-interface like enp8s0.10), WireGuard connection setup failed with
GatewayNotFoundError and timed out due to the killswitch dummy interface
blocking reachability checks.

This adds NM.DeviceType.VLAN and NM.SETTING_VLAN_SETTING_NAME to the
NetworkManager backend device filters and physical connection checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant