From: Matt Layher <mdlayher@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: [ANNOUNCE] wgctrl-go (formerly wireguardctrl) moved to WireGuard organization
Date: Mon, 13 May 2019 12:25:12 -0400 [thread overview]
Message-ID: <2d055837-37e0-c51e-02a0-f69d7f6cef89@gmail.com> (raw)
Hello all,
I'm pleased to announce that wgctrl-go (formerly wireguardctrl) has been
moved to the WireGuard organization. I'd like to thank Jason for this
offer, and for his help in making the transition happen as smoothly as
possible.
Package wgctrl is a Go package which enables control of WireGuard
interfaces on multiple platforms.
The new repository can be found at
https://github.com/WireGuard/wgctrl-go. It was previously my personal
project at https://github.com/mdlayher/wireguardctrl, which now
redirects to the new location.
The expected Go import path is now "golang.zx2c4.com/wireguard/wgctrl",
and code which makes use of this package must be updated accordingly,
including the package name switch from "wireguardctrl" to "wgctrl".
Documentation can be viewed at
https://godoc.org/golang.zx2c4.com/wireguard/wgctrl.
At the moment, wgctrl-go supports configuring both Linux kernel and
userspace WireGuard devices on UNIX platforms, but Windows support is
actively being worked on. My intent is to add support for configuring
any type of WireGuard device under a unified Go interface, so please do
reach out if you're building a new implementation for a different
platform which does not make use of the userspace configuration protocol.
If you run into any trouble with wgctrl-go, feel free to reply to this
email, file an issue, or reach out on #wireguard on freenode.
Thanks for your time,
Matt Layher
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-05-13 16:25 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=2d055837-37e0-c51e-02a0-f69d7f6cef89@gmail.com \
--to=mdlayher@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).