Arch Linux

Vlazm

Member

Registered: 2025-01-27

Posts: 38

[SOLVED] Mullvad vpn doesn't work properly

I have issues with mullvad vpn that seemingly appeared out of the blue.

Mullvad worked just fine for few dayus after I installed the AUR package mullvad-vpn-bin.
Later however my internet trafic failed to go through.
Pinging domains like archlinux.org fails with following message:

PING archlinux.org (xxxx:xxxx:xxxx:xxxx::xxxx) 56 data bytes
From [my host name] (xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) icmp_seq=1 Destination unreachable: Port unreachable
From [my host name] (xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) icmp_seq=2 Destination unreachable: Port unreachable
From [my host name] (xxxx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx) icmp_seq=3 Destination unreachable: Port unreachable

I apologise for over redaction, I just don't want to accidentally leak any sensitive information.

Pinging DNS servers works just fine though (1.1.1.1 for example goes through just fine)

What is strange about this ping is that the address (duplicated in each packet line) is too long I think?
Its first 4 column-separated numbers match one of my DNS servers provided in /etc/resolve.conf exactly (minus the port for some reason).
I don't remember putting that DNS server so it may have been mullvad's DNS server?? And I don't know where the other part of that long ass address comes from.

Pinging that long address works both with and without vpn connection.

I tried to remove mullvad-vpn-bin and install mullvad-vpn package, however I have a feeling that it did not built from source and somehow used cache left by mullvad-vpn-bin (although I don't think its possible cause I removed it with yay -Rns mullvad-vpn-bin which I think also removes cache?)

That's all I have. I'd really appreciate some advice

Last edited by Vlazm (Today 06:11:10)

---

Arch linux — essential

Vlazm

Member

Registered: 2025-01-27

Posts: 38

Re: [SOLVED] Mullvad vpn doesn't work properly

ok, this one is on me. It works now, however I swear it was not working for prolonged period of time yesterday. The ping command that I usually use for checking if VPN is connected properly (I quickly check if resources that fall under regional censorship are reachable) apparently may not always work with VPNs and system-wide proxies, which I admit, I should've done more research on before posting the question. Again, vpn was not really working anyways so I assumed the ping output was somehow related. Marking as solved

---

Arch linux — essential

-thc

Member

Registered: 2017-03-15

Posts: 1,094

Re: [SOLVED] Mullvad vpn doesn't work properly

What is strange about this ping is that the address (duplicated in each packet line) is too long I think?

Why do you think that it's too long?

Its first 4 column-separated numbers match one of my DNS servers provided in /etc/resolve.conf exactly (minus the port for some reason).

Why do you think port numbers are involved?