Wireguard adapter was created, but we are not able to establish a connection
❯ /home/yup/.local/bin/zcli vpn up
➤ INFO Selected project: ok
➤ INFO VPN config saved: /home/yup/.config/zerops/zerops.conf
! WARN Wireguard adapter was created, but we are not able to establish a connection,this could indicate a problem on our side. Please contact our support team via https://support.zerops.io, [email protected] or join our discord https://discord.com/invite/WDvCZ54.
22 Replies
^ i also cant ssh into it
@Aleš can someone help ?
sup nermal
@pr0tys
what OS/distro @the j
cachyos, basically arch linux
Hi, can you post output of
sudo wg show and cat /etc/resolv.conf?after i run zcli vpn up or before
after
kk
❯ sudo wg show
interface: wg0-mullvad
public key: eZMdU5V5KQX7Mjup95PZzwPB+uIUrkRnL9r4o8MZPS0=
private key: (hidden)
listening port: 48109
fwmark: 0x6d6f6c65
peer: fZFAcd8vqWOBpRqlXifsjzGf16gMTg2GuwKyZtkG6UU=
preshared key: (hidden)
endpoint: 127.0.0.1:34691
allowed ips: 0.0.0.0/0
latest handshake: 1 minute, 36 seconds ago
transfer: 140.36 MiB received, 6.91 MiB sent
interface: zerops
public key: icSpj7IYoVIMEj/w2XjqOtot7/eAH3l+u51RARt+F34=
private key: (hidden)
listening port: 58020
peer: TUrP7wF8Rl/lflKBhOf19Q/+KdwPYyS5AqnvZzBEUl0=
endpoint: 93.185.106.128:29032
allowed ips: 10.4.24.0/22, fda0:5ef:105:c0de::/64, 10.4.28.0/22, fda0:5ef:105:c0df::/64
latest handshake: 7 seconds ago
transfer: 156 B received, 180 B sent
persistent keepalive: every 5 seconds
~/zerops master*
❯
❯ cat /etc/resolv.conf
nameserver 10.64.0.1
options edns0
options trust-ad
~/zerops master*
❯
okay, seems like the interface and connection has been estabilished, but didn't setup dns resolver correctly
can you try
zcli vpn down, then sudo wg-quick up /home/yup/.config/zerops/zerops.conf and post output of that?❯ sudo wg-quick up /home/yup/.config/zerops/zerops.conf
[#] ip link add zerops type wireguard
[#] wg setconf zerops /dev/fd/63
[#] ip -4 address add 10.4.28.3/32 dev zerops
[#] ip -6 address add fda0:5ef:105:c0df:10:4:28:3/128 dev zerops
[#] ip link set mtu 1280 up dev zerops
[#] ip -6 route add fda0:5ef:105:c0df::/64 dev zerops
[#] ip -6 route add fda0:5ef:105:c0de::/64 dev zerops
[#] ip -4 route add 10.4.28.0/22 dev zerops
[#] ip -4 route add 10.4.24.0/22 dev zerops
[#] resolvectl dns zerops 10.4.24.1
[#] resolvectl domain zerops zerops
~/zerops master*
❯
hmm, wired was expecting this to end with error. What version of resolver do you use
resolvectl --version?systemd 256 (256.9-1-arch)
this is lowkey kinda weird
and output of
resolvectl status❯ resolvectl status
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
Current DNS Server: 10.64.0.1
DNS Servers: 10.64.0.1
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net
2001:4860:4860::8888#dns.google
Link 2 (eno1)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.100.1
DNS Servers: 192.168.100.1
Link 26 (wg0-mullvad)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 28 (zerops)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.4.24.1
DNS Servers: 10.4.24.1
DNS Domain: zerops
~/zerops master*
❯
okay, I take it back seems dns is setup correctly, try
ping logger.core.zerops to be sure❯ ping logger.core.zerops
ping: logger.core.zerops: Temporary failure in name resolution
~/zerops master*
❯
bruh what
😭
wait maybe i need vpn up
its already up
smh
vpn up essentially does
sudo wg-quick up which you have ran manuallyah alr
post output of
dig @10.4.24.1 logger.core.zeropsSeems to me like clash between mullvad and wireguard configuring resolv.conf. Especially mullvad did it some freaky way.