All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Text-based IPC for Userspace Implementations
Date: Thu, 18 May 2017 18:46:42 +0200	[thread overview]
Message-ID: <1495126002.1834.2.camel@gmx.de> (raw)
In-Reply-To: <CAHmME9pQxx_-h=8a_YpRgGnidjOA8aJeT=Lz3v-RkB_17dP9jA@mail.gmail.com>

On Wed, 2017-05-17 at 16:08 +0200, Jason A. Donenfeld wrote:
> Hi Manuel,
>=20
> On Wed, May 17, 2017 at 4:04 PM, Manuel Sch=C3=B6lling
> <manuel.schoelling@gmx.de> wrote:
> > Great to hear that wireguard gets a nice IPC interface.
> > Do you already know when this is about to land in the wireguard
> > releases/repos?
>=20
> When Trevor wakes up today and publishes rev32b of Noise, I'm
> planning
> on releasing a snapshot of WireGuard seconds after. Currently 7am on
> the pacific coast...

I am a bit confused: I updated to 0.0.20170517 on Debian, but no
/run/wireguard/ or /var/run/wireguard/ exists.
Then I checked the source code and apparently only the wireguard-tools
support the new socket IPC interface but the kernel module does not.
Is that observation correct?

Thanks!

Manuel

  reply	other threads:[~2017-05-18 16:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 12:36 Text-based IPC for Userspace Implementations Jason A. Donenfeld
2017-05-16 13:12 ` Toke Høiland-Jørgensen
2017-05-16 16:01   ` Jonathan Rudenberg
2017-05-16 16:09     ` Toke Høiland-Jørgensen
2017-05-16 19:26     ` Jörg Thalheim
2017-05-17 14:01       ` Jason A. Donenfeld
2017-05-17 14:04         ` Manuel Schölling
2017-05-17 14:08           ` Jason A. Donenfeld
2017-05-18 16:46             ` Manuel Schölling [this message]
2017-05-18 18:04               ` Daniel Kahn Gillmor
2017-05-17 14:14         ` Bzzzz
2017-05-17 14:17           ` Jason A. Donenfeld
2017-05-16 16:33   ` Guanhao Yin
2017-05-17 13:53     ` Jason A. Donenfeld
2017-05-16 15:43 ` Ivan Labáth
2017-05-17 14:00 ` Jason A. Donenfeld
2017-05-17 18:07   ` Toke Høiland-Jørgensen
2017-05-17 18:10     ` Jason A. Donenfeld
2017-05-17 17:04 ` Jason A. Donenfeld
     [not found] ` <20170516154204.GB9458@matrix-dream.net>
     [not found]   ` <CAHmME9roTAqMYB0qB7JG3rkKfGw1nfzTz0AD-frcGyyweCTcJQ@mail.gmail.com>
2017-05-18  8:02     ` allowed_ips move semantics? Ivan Labáth
2017-05-18 10:08       ` Jason A. Donenfeld
2017-05-18 12:00         ` Ivan Labáth

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=1495126002.1834.2.camel@gmx.de \
    --to=manuel.schoelling@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.