From: Derrick Lyndon Pallas <derrick@pallas.us>
To: wireguard@lists.zx2c4.com
Subject: Re: Python Wrapper for wireguard-tools
Date: Sat, 22 Aug 2020 14:14:27 -0700 [thread overview]
Message-ID: <abdfb441-3df9-3ab5-dae2-7ed4f648e40c@pallas.us> (raw)
In-Reply-To: <CAHmME9qoWSURAqdQJuOdo9xCBgrtENNOGgf_o1uRep66xRWzJw@mail.gmail.com>
Andrew, if you'd like help creating a truly cross-platform library in
python, I'm happy to help. The reasons wgnlpy is currently Netlink-only
is that I was developing it for a Linux system and pyroute2 didn't
support Wireguard yet. If embeddable-wg-library supported UAPI and BSD
too, then hooking it up to Pyhton via CFFI would make a lot of sense,
and I'm potentially able to help with that as well. ~Derrick
On 8/22/20 12:05 PM, Jason A. Donenfeld wrote:
> Hey Andrew,
>
> The most complete "library" is actually the wgctrl-go one from Matt
> (CC'd). It's complete because it supports all the same interfaces as
> wg(8) -- Linux Netlink, OpenBSD IOCTL, and x-platform UAPI. The
> embeddable-wg-library is just for Linux Netlink, but I should maybe
> refactor that to be more modular. And as you pointed out, the wgnlpy
> stuff is Netlink also.
>
> If you wanted to start a new cross-platform library, and essentially
> "clone" Matt's Go library into a pure Python one, I'd certainly
> welcome that effort and would be happy to help.
>
> Jason
next prev parent reply other threads:[~2020-08-22 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 14:04 Andrew Roth
2020-08-22 19:05 ` Jason A. Donenfeld
2020-08-22 21:14 ` Derrick Lyndon Pallas [this message]
2020-08-31 20:40 ` Matt Layher
2020-08-24 14:37 ` Arti Zirk
2020-08-24 18:57 ` Ryan Whelan
[not found] ` <CAKmhVko10JYo__SfNGujkeVV_YCPVLtBkLzcXoMfo7X3qjD5pA@mail.gmail.com>
2020-08-24 19:38 ` Mo Balaa
2020-08-27 8:34 ` Jason A. Donenfeld
2020-08-27 8:59 ` Mo Balaa
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=abdfb441-3df9-3ab5-dae2-7ed4f648e40c@pallas.us \
--to=derrick@pallas.us \
--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).