From: Markus Lindenberg <markus@lindenberg.io>
To: wireguard@lists.zx2c4.com
Subject: Re: 34C3 - WireGuard Workshop?
Date: Wed, 20 Dec 2017 17:40:23 +0100 [thread overview]
Message-ID: <20171220164023.dpev2hmuml3bd4m4@hodor.lindenberg.io> (raw)
In-Reply-To: <CAHmME9qVY2jiMoXGKYmfBSh4DD0tACZiV90RKqxw6SaunbaYLg@mail.gmail.com>
Hi Jason,
On Mon, Dec 18, 2017 at 07:52:42PM +0100, Jason A. Donenfeld wrote:
>
> I'll be at 34C3. Is there any interest in having some sort of
> WireGuard workshop? Are there things to talk about it? Would this be
> fun or interesting? How many people would be interested in such a
> thing?
I (and I guess others in the Freifunk realm) would be interested in how
to use WireGuard for open mesh networks, there are some unique problems
here (like running l3 mesh routing or l2 mesh routing protocols inside l2
tunnels inside wireguard; multicast; provisioning tunnels when only one
party is trusted, ...). The interest in and visibility of Wireguard is
quite high in our community, although I'm not familiar with the latest
developments in the most used wifi mesh firmware (Gluon based on Lede),
but I guess Gluon/Lede devs will be present.
If you need a place for a workshop I'm sure you'd be welcome at the
workshop space or stage of the Open Infrastructure Orbit:
https://events.ccc.de/congress/2017/wiki/index.php/Cluster:Open_Infrastructure_Orbit
> PS: still trying to work out hotel arrangements, if anybody knows any
> Leipzig tricks.
Surplus hotel rooms are posted on this page:
https://events.ccc.de/congress/2017/wiki/index.php/HotelExchange
prev parent reply other threads:[~2017-12-20 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 18:52 Jason A. Donenfeld
2017-12-18 19:45 ` Georg Faerber
2017-12-18 20:56 ` Martin Schmiedecker
2017-12-20 16:11 ` Germano Massullo
2017-12-20 16:40 ` Markus Lindenberg [this message]
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=20171220164023.dpev2hmuml3bd4m4@hodor.lindenberg.io \
--to=markus@lindenberg.io \
--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).