-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internet gets disabled when I try to run wg client #13
Comments
It seems like you are using a proxy DNS running on localhost ( |
Cool Thanks. I removed all the DNS from wifi and from the router as well. Still, I got the same problem after 1 successful run. 2020/04/25 15:23:33 Get "https://cloudflare.com/cdn-cgi/trace": dial tcp: lookup cloudflare.com on 127.0.0.53:53: read udp 127.0.0.1:49003->127.0.0.53:53: i/o timeout |
Okay, so there is no internet even though I removed the Proxy DNS. ravinder@ravinder-Aspire-A515-51:$ wg-quick up ravinder_private/warp+.conf 1 ravinder@ravinder-Aspire-A515-51:$ ping 1.1.1.1 1 ravinder@ravinder-Aspire-A515-51:$ wg-quick down ravinder_private/warp+.conf The Internet doesn't work now after running the client. |
To connect on Ubuntu, try this exact sequence.. ping -c 3 -W 3 google.com |
When I use DNS through Tor, this sequence is how I have to connect to warp on Ubuntu. This sequence works every time. ping -c 3 -W 3 google.com |
Tried this. --- google.com ping statistics --- --- google.com ping statistics --- --- google.com ping statistics --- |
Hey so i figured my problem of proxy-dns which is of cloudflared. I used the command sudo cloudflared proxy-dns. How can i stop this? Cuz it goes to 127.0.0.53:53. How can i reset this? My bad, 127.0.0.53 is my stub resolver as it is defined in /etc/resolv.conf |
As this issue is with your individual setup and unrelated to the project, I'm afraid I cannot help there. I will now close this issue, but I hope you manage to fix it. Feel free to reply here and add any notes for other users if you figure out out. |
Yeah, so I changed my nameserver to 1.1.1.1 by overriding the /etc/resolv.conf. By doing so it's faster than it's default one which is 127.0.0.53.
The real problem is still not fixed. Not sure if the client has the issue or the Cloudflare API. |
Timeout error as the internet gets disabled when running the wg-quick up wgcf-profile.conf. In my mobile, the app 1.1.1.1 works fine. Also, I didn't get this issue on windows laptop(downloading, browsing all works fine) but on ubuntu after sometime internet gets disabled when try to run wg client.
ravinder@ravinder-Aspire-A515-51:$ wg-quick up wgcf-profile.conf
[#] ip link add wgcf-profile type wireguard
[#] wg setconf wgcf-profile /dev/fd/63
[#] ip -4 address add 172.16.0.2/32 dev wgcf-profile
[#] ip -6 address add fd01:5ca1:ab1e:8c92:3e75:2f5:4a5e:47d1/128 dev wgcf-profile
[#] ip link set mtu 1420 up dev wgcf-profile
[#] resolvconf -a tun.wgcf-profile -m 0 -x
[#] wg set wgcf-profile fwmark 51820
[#] ip -6 route add ::/0 dev wgcf-profile table 51820
[#] ip -6 rule add not fwmark 51820 table 51820
[#] ip -6 rule add table main suppress_prefixlength 0
[#] ip6tables-restore -n
[#] ip -4 route add 0.0.0.0/0 dev wgcf-profile table 51820
[#] ip -4 rule add not fwmark 51820 table 51820
[#] ip -4 rule add table main suppress_prefixlength 0
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
[#] iptables-restore -n
ravinder@ravinder-Aspire-A515-51:$ ./wgcf_1.0.5_linux_amd64 trace --config "ravinder_private/warp+.toml"
2020/04/25 10:45:54 Using config file: ravinder_private/warp+.toml
2020/04/25 10:46:14 Get "https://cloudflare.com/cdn-cgi/trace": dial tcp: lookup cloudflare.com on 127.0.0.53:53: read udp 127.0.0.1:36291->127.0.0.53:53: i/o timeout
ravinder@ravinder-Aspire-A515-51:$ wg-quick down wgcf-profile.conf
[#] ip -4 rule delete table 51820
[#] ip -4 rule delete table main suppress_prefixlength 0
[#] ip -6 rule delete table 51820
[#] ip -6 rule delete table main suppress_prefixlength 0
[#] ip link delete dev wgcf-profile
[#] resolvconf -d tun.wgcf-profile -f
[#] iptables-restore -n
[#] ip6tables-restore -n
The text was updated successfully, but these errors were encountered: