![]() I’m not really sure how or why, but I suppose I could dump the tarball into /opt. I did run into one little hair in the soup with SeaMonkey though. Then I remembered I had to go into the WiFi settings in NetworkManager in Fedora and set IPv6 to disabled and reconnect to the WiFi and that solved the problem here too. ![]() Then I used TorGuard’s “What is my Torrent IP” page to check and sure enough Transmission leaked the real IPv6. I checked my IP address and the site showed my Mullvad-assigned VPN ipv4 and no ipv6. I went ahead and did an “Extended DNS Leak Test” and it wasn’t leaking. It doesn’t appear that anything fails to work properly. (yay!) I set the Lockdown Mode (to make sure nothing can access the internet until the VPN is working) and launch on startup and auto-connect. Then it installed it and the other dependencies and everything seems to work and no broken system. Break Mullvad by ignoring the “dbus-libs” dependency. I did sudo zypper install and it complained about that, so I chose option 2. *sigh*ĭo I detect just a hint of Fedora fanboy-ism? I looked around and Mullvad’s only comment is it’s not a priority for them that they have customers who want to pay them and use openSUSE. I managed to get Mullvad VPN to work on openSUSE and about the only caveat seems to be that the RPM package that supports Fedora 37+ expects that dbus-libs will be named that when it lists its dependencies, otherwise it works fine. Mullvad doesn’t support it, but it does work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |