GNOME Bugzilla – Bug 794200
NetworkManager detects spurious "unmanaged tun device" which is its own VPN connection
Last modified: 2020-11-12 14:33:13 UTC
When I connect to a VPN, the first thing that happens is that nm-openconnect-service creates a 'vpn0' logical device in the kernel. NetworkManager sees that, and considers it a completely separate 'unmanaged' device, not at all associated with the VPN service that NM was currently bringing up. This is wrong. I'm not sure if it's contributing to the problems in bug 794190 where the proper NM VPN connection ends up thinking it's routed through "vpn0", which is actually just itself... $ nmcli con NAME UUID TYPE DEVICE VPN2 bda8e791-d172-491d-b41e-35aa8a26fb3d vpn vpn0 Wired connection 1 2415d366-c770-4fd1-9f5a-403e417998af 802-3-ethernet enp0s31f6 virbr0 491c2da0-a8b2-4a8f-8e88-9ad0ea56f282 bridge virbr0 vpn0 05d8702d-85c6-4416-ac58-99edee9282a0 tun vpn0 Mar 09 11:44:33 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: ** (nm-openconnect-service:11917): WARNING **: Created tundev vpn0 Mar 09 11:44:33 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: ** Message: openconnect started with pid 12183 Mar 09 11:44:33 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595873.1752] vpn-connection[0x2ac5200,bda8e791-d172-491d-b41e-35aa8a26fb3d,"VPN2",0]: VPN plugin: state changed: starting (3) ... Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6316] keyfile: add connection in-memory (05d8702d-85c6-4416-ac58-99edee9282a0,"vpn0") Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6325] device (vpn0): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6334] device (vpn0): Activation: starting connection 'vpn0' (05d8702d-85c6-4416-ac58-99edee9282a0) Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6342] device (vpn0): state change: disconnected -> prepare (reason 'none') [30 40 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6367] device (vpn0): state change: prepare -> config (reason 'none') [40 50 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6382] device (vpn0): state change: config -> ip-config (reason 'none') [50 70 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6386] device (vpn0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6496] device (vpn0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6504] device (vpn0): state change: secondaries -> activated (reason 'none') [90 100 0] Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6542] policy: set 'vpn0' (vpn0) as default for IPv4 routing and DNS Mar 09 11:44:34 uc8d3ff76b9bc5848a9cc NetworkManager[30113]: <info> [1520595874.6543] device (vpn0): Activation: successful, device activated.
Yes, that is very wrong in my opinion. It's how VPN connections are implemented in NetworkManager, and fixing it is a larger work. But despite this being an old issue, I is on our TODO list... it just takes time.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).