WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Arne Schwabe <arne@rfc2549.org>
Cc: dev@nmap.org, openvpn-devel@lists.sourceforge.net,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [Openvpn-devel] [ANNOUNCE] Wintun: Layer 3 TUN Driver for Windows
Date: Mon, 25 Mar 2019 11:37:19 +0100
Message-ID: <CAHmME9rMuAXh97168Cdhh3NYPvX_On_rmn3+3+9hzMuYGv9s1g@mail.gmail.com> (raw)
In-Reply-To: <0fe186bb-7df2-e3c4-cccd-b3b624fbc1bf@rfc2549.org>

Hey Arne,

On Mon, Mar 25, 2019 at 11:23 AM Arne Schwabe <arne@rfc2549.org> wrote:
> I wish you good luck in this endeavour and welcome the prospect of
> having a better tun driver for Windows. We know that our own TAP/TUN
> driver is a pain point for us as well and having a better alternative is
> something we would definitively like to have/support a more modern driver.
> The lack of tap is not a big deal for OpenVPN anymore. The world shifted
> quite a bit and tap support is not needed that much anymore. Android
> does not support it. MacOS client supports tun natively (utun) and tap
> requires extra kext. And so on...

That's good to know. I wasn't aware that that perspective was there
for OpenVPN as well. It certainly makes things simpler. In that case,
I'll certainly try to continue to keep OpenVPN in mind when developing
this. And depending on everybody's time availability, maybe at some
point we could work together in adding experimental support for Wintun
in OpenVPN.

> I am afraid our project members are currently busy and cannot really
> contribute much to your new shiny driver. We barely have enough time for
> OpenVPN itself. But if you have something that is good enough at least
> for testing and has a reasonable stable API just an extra mail and I
> think we can implement it as alternative to our own driver.

Great. I'll send a follow-up when we're at that point. At the moment
we're working out some details with IO_CSQ, and then we'll try to put
together some half-decent API documentation to make this easy. Then,
I'll poke you and we can get rolling with this.

> Frome the site: The source code is provided under the GPL 2.0 and is
> available via git:
> One detail here. If you have/add a file that defines the API for
> external programs, to license it under a freeer license for 3rd party to
> include that API file without license worries. Like our tap-windows.h
> (https://github.com/OpenVPN/tap-windows6/blob/master/src/tap-windows.h).
> This was primarily requested by the Freeswan developer iirc.

That's a good point. I'll certainly do something like that. Or,
possibly I'll just relicense the whole driver to MIT so nobody has to
worry. Will give it some thought.

WireGuard mailing list

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  1:04 Jason A. Donenfeld
2019-03-23 21:10 ` Alen Opacic
2019-03-25 10:23 ` [Openvpn-devel] " Arne Schwabe
2019-03-25 10:37   ` Jason A. Donenfeld [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHmME9rMuAXh97168Cdhh3NYPvX_On_rmn3+3+9hzMuYGv9s1g@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=arne@rfc2549.org \
    --cc=dev@nmap.org \
    --cc=openvpn-devel@lists.sourceforge.net \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox