From: Jim Darby <uberscubajim@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Timing issue (?) with wg-quick up on Raspberry Pi B+
Date: Sun, 10 Sep 2017 12:34:34 +0100 [thread overview]
Message-ID: <1e1740c3-f8cf-2ee2-d842-749b687cb737@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
I've been using WireGuard and it's proven great. However, I've noticed a
perclirary on a Raspberry Pi B+.
When I do a wg-quick up wg0 it echos the commands it's running and
they're fine. So it says:
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip address add 192.168.2.3/32 dev wg0
[#] ip link set mtu 1420 dev wg0
[#] ip link set wg0 up
[#] ip route add 192.168.2.0/24 dev wg0
However, if I look at wg0 I get:
wg0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
So, it's all worked /apart/ from the ip address add 192.168.2.3/32 dev wg0.
It works fine on the faster Raspberry Pi 3 and if run the ip address
command manually it performs perfectly.
This leads me to suspect some sort of timing problem that rarely shows
due to most machines being significantly faster.
Any ideas?
Regards,
Jim.
[-- Attachment #2: Type: text/html, Size: 2503 bytes --]
next reply other threads:[~2017-09-10 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 11:34 Jim Darby [this message]
2017-09-10 12:44 ` Jason A. Donenfeld
2017-09-10 13:09 ` Jim Darby
2017-09-10 14:26 ` Jason A. Donenfeld
2017-09-10 15:08 ` Jim Darby
2017-09-10 22:25 ` Jason A. Donenfeld
2017-09-10 22:30 ` Jason A. Donenfeld
2017-09-10 23:23 ` Jim Darby
2017-09-11 0:52 ` Jason A. Donenfeld
2017-09-11 12:35 ` Jim Darby
2017-09-11 12:37 ` Jason A. Donenfeld
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=1e1740c3-f8cf-2ee2-d842-749b687cb737@gmail.com \
--to=uberscubajim@gmail.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).