this post was submitted on 18 Jan 2024
1 points (100.0% liked)

WireGuard

3 readers
1 users here now

WireGuard - a fast, modern, secure VPN Tunnel.

founded 1 year ago
MODERATORS
 
This is an automated archive.

The original was posted on /r/wireguard by /u/rqbin_jus on 2024-01-18 14:39:24+00:00.


I am hosting a wg vpn on a raspberry pi4, and it works well on two windows client. Now, i try to connect my arch linux laptop, and i have some serious issues with the dns. I tried everything, but nothing work :/ i can connect to the DNS, but not to websites. Help ? :(

(sorry for the french outputs)

❯ sudo wg-quick up wg0

[#] ip link add wg0 type wireguard

[#] wg setconf wg0 /dev/fd/63

Warning: AllowedIP has nonzero host part: 10.149.249.1/24

Warning: AllowedIP has nonzero host part: fd11:5ee:bad:c0de::1/64

[#] ip -4 address add 10.149.249.2/32 dev wg0

[#] ip link set mtu 1420 up dev wg0

[#] resolvconf -a wg0 -m 0 -x

[#] ip -6 route add fd11:5ee:bad:c0de::/64 dev wg0

[#] ip -4 route add 10.149.249.0/24 dev wg0

__________________________________________________________________________________

❯ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) octets de données.

64 octets de 8.8.8.8 : icmp_seq=1 ttl=59 temps=62.4 ms

64 octets de 8.8.8.8 : icmp_seq=2 ttl=59 temps=49.6 ms

64 octets de 8.8.8.8 : icmp_seq=3 ttl=59 temps=67.0 ms

^C

--- statistiques ping 8.8.8.8 ---

3 paquets transmis, 3 reçus, 0% packet loss, time 2004ms

rtt min/avg/max/mdev = 49.624/59.680/67.021/7.357 ms

__________________________________________________________________________________

❯ ping google.fr

ping: google.fr: Échec temporaire dans la résolution du nom

__________________________________________________________________________________

❯ cat /etc/resolv.conf

nameserver 127.0.0.53

options edns0 trust-ad

search .

__________________________________________________________________________________

❯ sudo wg-quick down wg0

[#] ip link delete dev wg0

[#] resolvconf -d wg0 -f

❯ ping google.fr

PING google.fr (2a00:1450:4007:819::2003) 56 octets de données

64 octets de par21s22-in-x03.1e100.net (2a00:1450:4007:819::2003) : icmp_seq=1 ttl=110 temps=40.1 ms

64 octets de par21s22-in-x03.1e100.net (2a00:1450:4007:819::2003) : icmp_seq=2 ttl=110 temps=41.7 ms

64 octets de par21s22-in-x03.1e100.net (2a00:1450:4007:819::2003) : icmp_seq=3 ttl=110 temps=40.5 ms

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here