But wg-quick for some reason refuses to work with my ivpn config files. First, I can’t start them from the home dir ( invalid name, or can’t find it). Only works when I copy them to /etc/wireguard/. But even then I can’t get Internet through the proxy VM.
Would also be nice if I can get port forwarding to work and the connection issues resolved (maybe because ICMP is disabled? I have hybrid Internet via. DSL and LTE when I force connection through DSL most issues go away(Also does blocking ICMP improve privacy?)
How do I troubleshoot this? Are there better way’s to get VPN working?
I know obviously almost nothing about networking and have wasted dozens of hours on this issue.
But blocking all ICMP outright can break something in your connections and then you’ll be stuck figuring out why do you have problems with connection.
I’d at least allow path MTU discovery.
I don’t know which IVPN DNS you should use. You can ask IVPN about it.
You can try to use public DNS (126.96.36.199 / 188.8.131.52 / 184.108.40.206 / etc) to check if the problem is with DNS server IP or somewhere else.
Fedora 38. I normarly use DISP for my vpn qubes. But I also tried fresh AppVM’s
When I swap the ivpn config with a mullvad config everything works fine.
The configs have the same amount of lines and probably also characters…
When I use IVPN, wg-quick doesn’t want them from the home dir and then dig always gives timeout errors
This is my ivpn config.
PrivateKey = X
Address = X
DNS = 172.16.0.1
PublicKey = X
AllowedIPs = 0.0.0.0/0,::0/0
Endpoint = xxxx:xxxx
And Mullvad is the same.
I really don’t get it
How can I troubleshoot this??
Does wireguard not apply the conf correctly somehow?
Also I can’t post any replies anymore. The forum blocks me for 12 hours
I did that
This is not just an issue with ivpn. Just tried it with proton same issue. Only mullvad works
Changed the dns in the wireguard config and the dns hijacking scriipt restarted and run the commands. Still no dns
I did not add these rules. Sorry did i mention that I have the ivpn-proxy behind a mullvad-proxy (with the exact mullvad setup). I only tried to get it working behind the mullvad-proxy. I guess that might be the issue? But the GUI client from IVPN worked fine. Just leaked the mullvad DNS… Almost the same as the current config…
I shows connection established but dig still returns nothing. So the same as the mullvad guide I guess. Curl ip.me also works… i should mention that tasket-ivpn is behind mullvad-proxy. I will convert mullvad also to tasket… wait
Tasket behind Tasket gives the same error…
Just IVPN in tasket gives also no dig reply…