From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: IT Developer <developer@it-offshore.co.uk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard added to Alpine Linux
Date: Thu, 2 Mar 2017 19:24:16 -0800 [thread overview]
Message-ID: <CAHmME9pSB59MBqxRa0Hm-EwrnARAvT42wHsYjdZO=7MFrhjb+A@mail.gmail.com> (raw)
In-Reply-To: <02a8fddb-7246-984c-c51c-cd8fe3925694@it-offshore.co.uk>
Hi Stuart,
On Thu, Mar 2, 2017 at 1:49 PM, Stuart Cardall
<developer@it-offshore.co.uk> wrote:
> Wireguard can be added to Alpine with:
>
> apk add wireguard-tools
Great!
>. On the server it is probably necessary to:
>
> echo wireguard >> /etc/modules && rc-update add modules boot
This step should not be necessary. You're probably forgetting to call
`depmod -a` after installing the module. This is needed to ensure that
the right module aliases and dependency information is generated, so
that the module is _auto-loaded_ when users run `ip link add wg0 type
wireguard`.
> A wireguard user mentioned on irc earlier today that everything is working
> perfectly.
Awesome!
>
> To monitor releases @ Alpine we use https://release-monitoring.org/ - if it
> doesn't pick up the changes I'll subscribe.
Okay. Well, keep in mind that I publish release notes here and tips to
distributions about any possible build changes, so your involvement or
at least subscription here would indeed be a good thing.
>
> If there is a step I was missing to correctly run `make check` I would still
> like to run it in the future - perhaps it will pick up potential issues from
> Alpine using musl libc (not glibc).
It's certainly not any of the current `make check` or tests/ stuff
that you're currently looking at. Rather, when WireGuard is compiled
in debug mode, if you insert it, then it will go through a series of
self-tests. For more intense testing, involving the userspace
component, there's `make test-qemu`, which builds a kernel and boots
up QEMU... But I suspect this is a bit too heavy weight for a distro.
And besides, it's already being run for every commit for all
kernel.org kernels on: https://www.wireguard.io/build-status/ By the
way -- this uses musl libc, so I ensure it will always run nicely
there.
The only thing remaining in the package is to remove the incoherent
"wireguard-tests" package, which doesn't work in the way you'd hope,
and doesn't belong there.
Regards,
Jason
next prev parent reply other threads:[~2017-03-03 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6b590394-3134-b725-a063-0993b32a51c4@it-offshore.co.uk>
2017-03-02 15:33 ` Jason A. Donenfeld
2017-03-02 21:49 ` Stuart Cardall
2017-03-03 3:24 ` Jason A. Donenfeld [this message]
2017-03-23 19:39 ` Stuart Cardall
2017-03-08 16:05 ` Release monitoring (Was: Wireguard added to Alpine Linux) Baptiste Jonglez
2017-03-08 17:12 ` Stuart Cardall
2017-03-08 18:05 ` Stuart Cardall
2017-03-10 3:14 ` 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='CAHmME9pSB59MBqxRa0Hm-EwrnARAvT42wHsYjdZO=7MFrhjb+A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=developer@it-offshore.co.uk \
--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).