WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Netdev <netdev@vger.kernel.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: organization of wireguard linux kernel repos moving forward
Date: Mon, 9 Dec 2019 13:49:20 +0100
Message-ID: <CAHmME9oUfp_1udMFNMpeXPeoa7aacdNp9Q31eKvoTBpu+G5rpQ@mail.gmail.com> (raw)
In-Reply-To: <87d0cxlldu.fsf@toke.dk>

On Mon, Dec 9, 2019 at 1:43 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> "Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> > 2) wireguard-tools.git will have the userspace utilities and scripts,
> > such as wg(8) and wg-quick(8), and be easily packageable by distros.
> > This repo won't be live until we get a bit closer to the 5.6 release,
> > but when it is live, it will live at:
> > https://git.zx2c4.com/wireguard-tools/ [currently 404s]
> > https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/wireguard-tools.git/
> > [currently 404s]
> Any plans for integrating this further with iproute2? One could imagine
> either teaching 'ip' about the wireguard-specific config (keys etc), or
> even just moving the 'wg' binary wholesale into iproute2?

I'd definitely be interested in this. Back in 2015, that was the plan.
Then it took a long time to get to where we are now, and since then
wg(8) has really evolved into its own useful thing. The easiest thing
would be to move wg(8) wholesale into iproute2 like you suggested;
that'd allow people to continue using their infrastructure and whatnot
they've used for a long time now. A more nuanced approach would be
coming up with a _parallel_ iproute2 tool with mostly the same syntax
as wg(8) but as a subcommand of ip(8). Originally the latter appealed
to me, but at this point maybe the former is better after all. I
suppose something to consider is that wg(8) is actually a
cross-platform tool now, with a unified syntax across a whole bunch of
operating systems. But it's also just boring C.
WireGuard mailing list

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 11:56 Jason A. Donenfeld
2019-12-09 12:43 ` Toke Høiland-Jørgensen
2019-12-09 12:49   ` Jason A. Donenfeld [this message]
2019-12-09 16:01     ` Toke Høiland-Jørgensen
2019-12-09 16:18     ` David Ahern
2019-12-09 16:36       ` Toke Høiland-Jørgensen
2019-12-26 17:45 ` 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:

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

  git send-email \
    --in-reply-to=CAHmME9oUfp_1udMFNMpeXPeoa7aacdNp9Q31eKvoTBpu+G5rpQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=netdev@vger.kernel.org \
    --cc=toke@toke.dk \
    --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 \
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:

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