From: Du Felix <boost.subscribing@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: sysctl of Alpine standard 3.8.1 doesn't support option -r.
Date: Mon, 3 Dec 2018 15:28:16 +0800 [thread overview]
Message-ID: <CAMbARA6yEQvHEL+X-1+pfOPePu_1ULLLZdr81wC7SW65j=ep+w@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1001 bytes --]
I use alpine standard 3.8.1, which has kernel 4.14.82-0-vanilla.
When I start wireguard as client peer with *wg-quick up client*, It says:
> [#] ip link add client type wireguard
> [#] wg setconf client /dev/fd/63
> [#] ip address add 10.0.0.4/24 dev client
> [#] ip link set mtu 1420 dev client
> [#] ip link set client up
> [#] resolvconf -a client -m 0 -x
> [#] wg set client fwmark 51820
> [#] ip -4 route add 0.0.0.0/0 dev client table 51820
> [#] ip -4 rule add not fwmark 51820 table 51820
> [#] ip -4 rule add table main suppress_prefixlength 0
> sysctl: unrecognized option: r
> BusyBox v1.29.3 (2018-11-21 11:45:56 UTC) multi-call binary.
>
> Usage: sysctl -p [-enq] [FILE...] / [-enqaw] [KEY[=VALUE]]...
>
> Show/set kernel parameters
>
> -p Set values from FILEs (default /etc/sysctl.conf)
> -e Don't warn about unknown keys
> -n Don't show key names
> -q Quiet
> -a Show all values
> -w Set values
>
The client peer cannot ping server peer.
[-- Attachment #1.2: Type: text/html, Size: 1390 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-12-05 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 7:28 Du Felix [this message]
2018-12-05 13:59 ` sysctl of Alpine standard 3.8.1 doesn't support option -r Lonnie Abelbeck
2018-12-06 23:59 ` Jason A. Donenfeld
2018-12-24 13:46 Sterrenboer
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='CAMbARA6yEQvHEL+X-1+pfOPePu_1ULLLZdr81wC7SW65j=ep+w@mail.gmail.com' \
--to=boost.subscribing@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).