+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Software - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=5)
+--- Forum: Installing Software (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=18)
+--- Thread: NetworkManager wont see Wireguard-based VPN (/showthread.php?tid=6827)
NetworkManager wont see Wireguard-based VPN - bonnevie - 03-03-2020
Hello,
I've installed Wireguard but NetworkManager doesn't see it. My VPN provider tells me that Wireguard-support was added to NetworkManager v1.16 with KDE destops in mind. Since Ubuntu 18.04 runs on v1.10.14 and Xfce, no dice I guess. Can I upgrade to NetworkManager v1.16 without breaking anything? Has anyone here managed to install Wireguard in LL4.8?
Re: NetworkManager wont see Wireguard-based VPN - Valtam - 03-03-2020
I wouldn't even attempt it. Network Manager is a key component. 1.22+ will be available in June.
Sent from my Mobile phone using Tapatalk
Re: NetworkManager wont see Wireguard-based VPN - bonnevie - 03-03-2020
Ok, I'll wait. Thank you Jerry.
Re: NetworkManager wont see Wireguard-based VPN - Earthenware - 01-27-2021
I installed Wireguard this afternoon and now my network interfaces have changed and I can't connect to the internet any more.
I can boot LL3 from a USB stick and it works fine (I'm using it right now). Is there a simple way to transfer network files/settings from a working LL3 to my HDD (LL4)?
I don't want to spend ages messing about with settings if I can avoid it. Just copying files/settings will be easier.
Re: NetworkManager wont see Wireguard-based VPN - Earthenware - 01-28-2021
Now fixed.
If anyone should come here looking for Wireguard problems in the future...
Although I uninstalled Wireguard, it had permanently renamed my interfaces, for example eth0 is now em1.
This stopped all internet traffic from working and so my original intention was to seek some simple way to transfer settings from a known working source (e.g. my bootable LL3 USB stick) to my HDD.
Then I remembered that my firewall rules are interface-specific, so I just re-wrote them to allow for the interface name change.
The em1 interface works fine now, although I'm not at all happy that Wireguard made these changes, especially without asking me first or notifying me that it had done so afterwards.
Now I just have to find Wireguard functionality without using WireguardÂ
