search

ViRb3 / wgcf

🚤 Cross-platform, unofficial CLI for Cloudflare Warp
MIT License
6.25k stars 693 forks source link

Can't reach 1.1.1.1 #15

Closed barolo closed 4 years ago

barolo commented 4 years ago

Everything is fine via mobile app, tried key from app, and generated through wgcf. pings can reach 1.1.1.1 just fine but upon bringing wg interface up pinging is no longer possible checked that I'm not going through proxy, my resolv.conf is proper 1.1.1.1/ 1.0.0.1. My connection doesn't have ipv6


./wgcf trace
2020/04/28 18:21:58 Using config file: wgcf-account.toml
2020/04/28 18:22:08 Get "https://cloudflare.com/cdn-cgi/trace": dial tcp: lookup cloudflare.com on 1.1.1.1:53: read udp 172.16.0.2:38131->1.1.1.1:53: i/o timeout
ViRb3 commented 4 years ago

There's a lot that could be wrong, and it's most probably related to your setup rather than wgcf. Try this free VPN provided by TunSafe. Generate a profile and use it the same way as you use the wgcf profile. Does it work? If not, then the problem is with you, and not wgcf. Otherwise please let me know and I will investigate.

barolo commented 4 years ago

It seems to be an issue with systemd, systemd-netwokd "Routing all DNS over WireGuard (i.e. Domains=~.) will prevent the DNS resolution of endpoints." "systemd-networkd does not automatically create routes for subnets specified in AllowedIPs. See systemd issue 14176. This will not affect the connectivity between peers since they exist in the subnet that is specified with the Address= option in the .network file.:" Unsure why it's not popping up everywhere though

ViRb3 commented 4 years ago

I am using WireGuard on Ubuntu and Debian with systemd without any problems. The routes not being added from AllowedIPs is related to #2, and I can confirm that the missing routes are not a problem. Did you test the other VPN, does it work?

barolo commented 4 years ago

I'm trying is TunSafe one working for you? I'm testing it on two systems one without systemd, with 5.6 kernels and inbuilt wireguard, both have issues with name resolution Edit: It's working on my systemd system now, unsure what fixed it....

ViRb3 commented 4 years ago

Sorry, apparently TunSafe VPN doesn't work (right now), so you can't test on it. I'm glad the problem fixed by itself, although that's not the answer one would want to hear. If you find any problems with wgcf itself I would be more than happy to look into them, but system-specific problems are really off of my limits. I am closing this now.

barolo commented 4 years ago

What I did, was to make sure that resolv.conf is properly symlinked, and removed ipv6 addresses from generated config as neither my system nor my ISP support ipv6 at all Might be useful for somebody passing by

mahdi-ln commented 4 years ago

What I did, was to make sure that resolv.conf is properly symlinked, and removed ipv6 addresses from generated config as neither my system nor my ISP support ipv6 at all Might be useful for somebody passing by

At beginning this solved my problem but now the problem is returned.

barolo commented 4 years ago

What I did, was to make sure that resolv.conf is properly symlinked, and removed ipv6 addresses from generated config as neither my system nor my ISP support ipv6 at all Might be useful for somebody passing by

At beginning this solved my problem but now the problem is returned.

It works fine on both of my systems now, but, I have to remember to launch wg-quick with sudo, otherwise it won't work even though it seemingly connects. And I have to remove ALL ipv6 entries, Addresses and AllowedIPs

ViRb3 commented 4 years ago

My ISP doesn't support IPv6 either, but IPv6-enabled WireGuard profiles like this one work fine on my Windows and Ubuntu machines, without any changes. I'm afraid I can't really help here since I cannot reproduce this issue, but it's most likely a routing problem.

barolo commented 4 years ago

My ISP doesn't support IPv6 either, but IPv6-enabled WireGuard profiles like this one work fine on my Windows and Ubuntu machines, without any changes. I'm afraid I can't really help here since I cannot reproduce this issue, but it's most likely a routing problem.

I agree that ipv6 is most likely a secondary thing [ and my fault, I'm on Gentoo ] in my case it was the resolving which fixed both machines. Is it normal to have to use sudo to make it work? Shouldn't we be able to just import the profile via networkmanager and use it?