(05-05-2021, 09:43 AM)poi$on ivy Wrote: (05-04-2021, 08:24 PM)Drako Wrote: (05-04-2021, 07:28 PM)Equinox Wrote: For future reference, you shouldn’t clone from GitHub unless you have to. It makes package management hell, and there’s a reason package managers exist in the Linux userspace.
That aside though, install openvpn as well. This can also be found in the mullvad github, but a better practice would be to use your package manager to install openvpn. Once openvpn is installed, configure it for mullvad, then enable the service unit, and you’ll be good.
Blackarch doesn't have a package available for Mullvad, so it is totally necessary for the OP to use a git clone here.
It's very possible that there is a daemon for mullvad, but it's either only available to the Debian/Fedora installation, or you'll need to jump through some hoops to get a daemon working in the git clone install. It would also help to know what version you installed. Was it the WireGuard or OpenVPN version?
(05-04-2021, 08:43 PM)Equinox Wrote: (05-04-2021, 08:24 PM)Drako Wrote: Blackarch doesn't have a package available for Mullvad, so it is totally necessary for the OP to use a git clone here.
It's very possible that there is a daemon for mullvad, but it's either only available to the Debian/Fedora installation, or you'll need to jump through some hoops to get a daemon working in the git clone install. It would also help to know what version you installed. Was it the WireGuard or OpenVPN version?
Yes, I cloned it for this reason. I can download the .deb file and convert it with debtap, but you still have to compile and build it I think and then do a NPM install. And yeah, its true that mullvad isnt made for Arch, mainly only fedora and debian. So thats why I cloned it from github.
I am using wireguard. Its the one that works best on my computer.
Neither, I’m doing all of this based on my experience in using Linux. And a generally good assumption to make for Arch users is that they have an AUR package manager installed, and there is an AUR package for mullvad. That’s why I brought up the bit about package management.
I would go with the openvpn option were it me though.
Should I install AUR? I read that its sometimes causes errors in the system and some people dont use it anymore, but if you think its fine then I'll trust it. Can I use the wireguard file instead of openvpn? Should I use 'sudo yay -S mullvadvpn?' Or what is the command for downloading it?
That’s a more nuanced question than I can answer for you.
The reason people don’t like using the arch user repository is because there’s no real standard of work quality there. In an ideal world, your package manager has a defined set of instructions that would install a package to your computer that is replicable and standardized. This is what pacman for Arch users, apt for Debian users, xbps for void users, etc. is attempting to accomplish.
The AUR doesn’t have any standardization, nor does it have any quality checking. There’s no official maintainer who can say that a package build for an AUR package is of any quality. That’s it’s biggest downfall.
That being the case though, you have to decide for yourself if you want an AUR package manager. Do you want a package manager that just installs package, even if you don’t know where those packages are going or how it affects your system? In most cases, you probably don’t. But in the advent of convenience, maybe you do.
If I had to say, I would say yes, you should install an AUR package manager. That being said though, my next suggestion is to use it frugally. It’s better than just cloning a git repository in that it’s actually managed, and can easily be uninstalled or modified. But using it too much can be detrimental in that if your file system may at some point become cluttered and disorganized.
As for the wireguard file, you may absolutely use wireguard instead of openvpn. Mullvad encouraged that, actually. You’re not bound by openvpn in the slightest.
And yes, the package name in the AUR is mullvad. As a bit of a protip, you shouldn’t use sudo in conjunction with an AUR package manager. Again, it’s not standardized in any way. That can open you up to privilege escalation (you don’t know what commands are being executed by the package build). AUR package managers use a fakeroot to build packages and will call sudo when appropriate so you’re not vulnerable to such attacks.