From: Nicolai <nicolai+wireguard@chocolatine.org>
To: wireguard@lists.zx2c4.com
Subject: OpenBSD interop testing
Date: Tue, 8 Sep 2020 03:23:07 +0000 [thread overview]
Message-ID: <20200908032307.GA93967@chocolatine.org> (raw)
Hello all,
Now that OpenBSD has tagged 6.8-beta it's a good time to report interop
testing of WireGuard. I've been using the kernel implementation since
support was merged in June. Every peer combination I've tried works
properly, it's a joy to use, and I'm excited for 6.7 users to upgrade
and start using the kernel implementation.
All OpenBSD-current machines are using the kernel implementation. Here
are the interop tests, all on IPv4:
0. peer-A, peer-B
1. OpenBSD 6.7 amd64 wireguard-go, OpenBSD 6.7-current amd64
2. OpenBSD 6.7-current amd64, OpenBSD 6.7-current amd64
3. OpenBSD 6.8-beta amd64, OpenBSD 6.8-beta amd64
4. Debian 10 x86-64 backported kernel, OpenBSD 6.7-current amd64
5. Debian 10 x86-64 backported kernel, OpenBSD 6.8-beta amd64
6. iOS 13.5.1, OpenBSD 6.7-current amd64
7. iOS 13.6, OpenBSD 6.7-current amd64
8. iOS 13.7, OpenBSD 6.7-current amd64
9. iOS 13.7, OpenBSD 6.8-beta amd64
10. macOS 10.15.4 (Catalina), OpenBSD 6.7-current amd64
11. macOS 10.15.6 (Catalina), OpenBSD 6.8-beta amd64
12. Android 5.1, OpenBSD 6.7-current amd64
13. Android 5.1, OpenBSD 6.8-beta amd64
14. OpenBSD 6.7-current i386, OpenBSD 6.7 amd64 wireguard-go
15. OpenBSD 6.7-current i386 PSK, OpenBSD 6.7 amd64 wireguard-go PSK
16. OpenBSD 6.7-current amd64 PSK, OpenBSD 6.7-current amd64 PSK
17. OpenBSD 6.8-beta amd64, OpenBSD 6.7 amd64 wireguard-go
Thank you to all developers, users, and contributors, in particular Matt
and Jason for bringing WireGuard to OpenBSD, and to everyone who has
given code feedback on tech@.
Nicolai
reply other threads:[~2020-09-18 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200908032307.GA93967@chocolatine.org \
--to=nicolai+wireguard@chocolatine.org \
--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).