Timing issue (?) with wg-quick up on Raspberry Pi B+

Jim Darby uberscubajim at gmail.com
Sun Sep 10 13:34:34 CEST 2017

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 dev wg0
    [#] ip link set mtu 1420 dev wg0
    [#] ip link set wg0 up
    [#] ip route add dev wg0

However, if I look at wg0 I get:

wg0       Link encap:UNSPEC  HWaddr 
           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 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?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20170910/408ba5b3/attachment.html>

More information about the WireGuard mailing list