nm-vpn reports vnet0 as a connected vpn

[cjohnston1158]

When running VMs on my laptop nv-vpn reports as being connected to vnet0 which seems odd.

LC_ALL=C nmcli -t connection show --active
:72b1520d-923c-47f9-9443-59c2d1829c13:802-11-wireless:wlp59s0
virbr0:aefcd86c-6a1a-4b89-b889-42b4fe3ca9f4:bridge:virbr0
vnet0:fa8b1a4f-91de-4a14-9c05-71d4c0233066:tun:vnet0

apt-cache policy i3xrocks-nm-vpn
i3xrocks-nm-vpn:
Installed: 3.0.18-1
Candidate: 3.0.18-1
Version table:
*** 3.0.18-1 500
500 http://ppa.launchpad.net/regolith-linux/stable/ubuntu focal/main amd64 Packages

[kgilmer]

There were some recent changes to the vpn block that are being published to the release PPA today Chris. Can you verify after update if the issue still exists?

[cjohnston1158]

This does appear fixed in the latest release. Thanks Ken!

[cjohnston1158]

@kgilmer I think I spoke too soon.. It now shows vnet1

pt-cache policy i3xrocks-nm-vpn
i3xrocks-nm-vpn:
Installed: 3.0.21-1
Candidate: 3.0.21-1
Version table:
*** 3.0.21-1 500
500 http://ppa.launchpad.net/regolith-linux/stable/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

[cjohnston1158]

I'm still seeing this with 3.2.1-1

[kgilmer]

Hi @cjohnston1158 , I do not use this type of VPN so am unsure of what the expected behavior is. Are you expecting to see wlp59s0 or something else?

[cjohnston1158]

It's not actually a vpn but a bridge.

[moritzheiber]

I'm returning to this ticket because, judging from the output, the script does exactly what it's supposed to do. The VM is creating a tun device (vnet0) which NetworkManager correctly identifies and manages.

You later said that vnet1 was being shown. Is that still the case? And is it really a device of type bridge? Following the logic of the virtual network interfaces it should also be a tun device.