From: Kent Friis <leeloored@gmx.com>
To: wireguard@lists.zx2c4.com
Subject: Multiple unreachable
Date: Sun, 26 Apr 2020 23:01:49 +0200 [thread overview]
Message-ID: <20200426230149.bf9e998b37a983892c635e78@gmx.com> (raw)
I have a pretty simple Wireguard setup between two machines. The power
supply in my brothers server died, so the tunnel is of course down. My
machine is running Linux 5.6.7 (from kernel.org, no patches or out of
tree drivers) with in-kernel Wireguard.
To see if he has gotten his server back up, I tried to ping it (via the
tunnel). That gave more unreachable responses than expected (note the
sequence number):
PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
...
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
From 172.24.0.1 icmp_seq=1 Destination Host Unreachable
ping: sendmsg: Destination address required
^C
--- 172.16.1.1 ping statistics ---
1 packets transmitted, 0 received, +50 errors, 100% packet loss, time 0ms
172.24.0.1 is my end.
172.16.1.1 is my brother (not online)
rc.wireguard:
ip link add dev wg0 type wireguard
wg setconf wg0 /etc/wireguard/wg0.conf
ip address add dev wg0 172.24.0.1
ip link set up dev wg0
ip route add 172.16.1.0/24 dev wg0
wg0.conf:
[Interface]
PrivateKey = removed
ListenPort = 51820
[Peer]
PublicKey = also removed
AllowedIPs = 172.16.1.0/24
My PC has been rebooted since the tunnel was last up, so Wireguard has no
ip address for the other end.
This is not causing any problems that I've noticed, but I assume there is
a bug somewhere to give this many errors. Pinging an unreachable host on the
LAN only gives one "Host Unreachable" message per sequence number.
-Kent
reply other threads:[~2020-05-06 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200426230149.bf9e998b37a983892c635e78@gmx.com \
--to=leeloored@gmx.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).