From: Jim Darby <uberscubajim@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Timing issue (?) with wg-quick up on Raspberry Pi B+
Date: Mon, 11 Sep 2017 00:23:11 +0100 [thread overview]
Message-ID: <59B5C95F.50508@gmail.com> (raw)
In-Reply-To: <CAHmME9pe-91wvf8pCwea7kzzNQoOw4aCn9jACoO=CE+BtA3KVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2950 bytes --]
On 10/09/17 23:25, Jason A. Donenfeld wrote:
> I just wrote the attached script, which will tell you all the
> processes that have an open netlink socket...
>
> There's a bit too much fluff in there on a desktop system, but I
> imagine the pi might help boil it down to a few candidates. Probably
> we'll determine it's an ifplugd/ifupdown.action thing, but we'll see.
Many thanks again for such great work. Here's the output of the
netlistenerwho.sh program. It's awash with potential culprits!
PID TTY STAT TIME COMMAND
1 ? Ss 2:35 /sbin/init
128 ? Ss 0:01 /lib/systemd/systemd-udevd
770 ? Ss 2:24 /sbin/dhcpcd -q -b
783 ? Ss 0:15 avahi-daemon: running [janus.local]
840 ? Ss 0:32 /lib/systemd/systemd-logind
896 ? Ss 10:19 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u
107:112
906 ? S 0:02 /usr/sbin/dnsmasq -x
/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7
/etc/dnsmasq.
1204 ? Ss 0:00 /lib/systemd/systemd --user
18942 ? Ss 0:00 /lib/systemd/systemd --user
I also made a great mistake earlier: the problematic system is the
version of Raspbian based on begin *8* and /not/ *9*. Debian 9 works fine!
I've tweaked the /etc/network/interfaces file to have the line “iface
wg0 inet manual” in it so we /shouldn't/ get DHCP running or anything…
I tried the nlmon trick but I got the response “RTNETLINK answers:
Operation not supported” which isn't too helpful.
After some more playing I've found that running the wg-quick script's
commands by hand works. But then, I'm /manually/ entering them and that
affects timing.
I note you perform the ”ip link set wg0 up” /after/ the “ip address add
192.168.2.3/32 dev wg0” and “ip link set mtu 1420 dev wg0”. /However,
/the act of creating the interface with the “ip link add wg0 type
wireguard” seems to trigger the ip up automatically. The log files give:
Sep 10 23:57:51 janus kernel: wireguard: WireGuard 0.0.20170907 loaded.
See www.wireguard.com for information.
Sep 10 23:57:51 janus kernel: wireguard: Copyright (C) 2015-2017 Jason
A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
Sep 10 23:57:51 janus ifplugd(wg0)[14109]: ifplugd 0.28 initializing.
Sep 10 23:57:51 janus ifplugd(wg0)[14109]: Using interface
wg0/00:00:00:00:00:00
Sep 10 23:57:51 janus ifplugd(wg0)[14109]: Using detection mode: IFF_RUNNING
Sep 10 23:57:51 janus ifplugd(wg0)[14109]: Initialization complete, link
beat detected.
Sep 10 23:57:52 janus ifplugd(wg0)[14109]: Executing
'/etc/ifplugd/ifplugd.action wg0 up'.
Sep 10 23:57:52 janus ifplugd(wg0)[14109]: client: /sbin/ifup: interface
wg0 already configured
Sep 10 23:57:52 janus ifplugd(wg0)[14109]: Program executed successfully.
Which could well be interesting. I manually ran ifdown then ifup on wg0
and it /didn't/ lose its IP address.
Most perplexing!
Jim.
[-- Attachment #2: Type: text/html, Size: 4354 bytes --]
next prev parent reply other threads:[~2017-09-10 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 11:34 Jim Darby
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 [this message]
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=59B5C95F.50508@gmail.com \
--to=uberscubajim@gmail.com \
--cc=Jason@zx2c4.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).