11-20-2023, 09:55 PM
(This post was last modified: 11-20-2023, 09:56 PM by Earthenware.)
After a long and tedious day installing, de-installing and re-installing OSs, I've found the problem (I think).
The short version is that the culprit is the Mullvad VPN client.
The long version is as follows:
I've used four OSs as part of testing: LL 6.6, LL 5.4, Mint and MX.
All OSs work fine when booted from Live USB.
All installed OSs work fine until the Mullvad client is installed.
The Mullvad client screws up every OS.
In all cases except MX, the problem remains even after the Mullvad client is de-installed.
I even regressed to LL 5.4 and an older version of the Mullvad client (which I know to work ok) and found the same problem: LL works fine, Mullvad install screws it up, remove Mulllvad, still screwed.
I know for a fact that some of these combos work on my old computers (e.g. LL 5.4 and old Mullvad client), so I can only assume that the NIC in the new PC is the other factor.
I like Mullvad, so I'm going to take this up with them. Hopefully there's a fix available. If there is, I'll report back here in case anyone else has the same problem.
Until then, I'll mark this thread as SOLVED, although all I've really done is identify the culprit rather than solved the problem.
PS: How do I mark it as solved?
The short version is that the culprit is the Mullvad VPN client.
The long version is as follows:
I've used four OSs as part of testing: LL 6.6, LL 5.4, Mint and MX.
All OSs work fine when booted from Live USB.
All installed OSs work fine until the Mullvad client is installed.
The Mullvad client screws up every OS.
In all cases except MX, the problem remains even after the Mullvad client is de-installed.
I even regressed to LL 5.4 and an older version of the Mullvad client (which I know to work ok) and found the same problem: LL works fine, Mullvad install screws it up, remove Mulllvad, still screwed.
I know for a fact that some of these combos work on my old computers (e.g. LL 5.4 and old Mullvad client), so I can only assume that the NIC in the new PC is the other factor.
I like Mullvad, so I'm going to take this up with them. Hopefully there's a fix available. If there is, I'll report back here in case anyone else has the same problem.
Until then, I'll mark this thread as SOLVED, although all I've really done is identify the culprit rather than solved the problem.
PS: How do I mark it as solved?