https://bugs.kde.org/show_bug.cgi?id=412795

Stephen <kdeb...@drsudo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdeb...@drsudo.com

--- Comment #8 from Stephen <kdeb...@drsudo.com> ---
I experienced this too, and was very frustrated by it (especially the default
name being invalid and losing my config). I thought that I could add a little
bit of explanation to it. The name of the connection is being used as the Linux
interface name (The list of names that you get if you type "ip link" at a
terminal).

AFAIK, other VPN types (such as OpenVPN) in the network manager don't do this.
I have an OpenVPN connection up right now, and it gets the interface name
"tun0". This has nothing to do with the name that I put in the network manager.

The consistent behavior would be to have the wireguard network get named
something like "wg0" regardless of what it is called in the network manager. On
the other hand having the Linux interface get a nice name is really cool. I
think the ideal would be if there was "interface name" field in the wireguard
setup UI, and the connection name was decoupled from the interface name.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to