All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Xu <alex_y_xu@yahoo.ca>
To: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] auth-only wireguard
Date: Thu, 6 Oct 2016 13:42:47 -0400	[thread overview]
Message-ID: <20161006134247.347b1040@alex-archsus> (raw)
In-Reply-To: <1475771658.1684011.747950545.01B63CCC@webmail.messagingengine.com>

On Thu, 06 Oct 2016 09:34:18 -0700
Jehan Tremback <jehan@altheamesh.com> wrote:

> Let me be more specific about my application. I'm trying to create a
> system where routers in a "mesh" network (mixed ad-hoc wifi and
> ethernet) pay their neighbors, or are paid by their neighbors for
> bandwidth. To make this happen, I've got to be able to identify
> traffic from specific neighbors with something less spoofable than MAC
> addresses. Creating tunnels between neighbors fits the bill for now,
> and gives me a good handle to apply traffic shaping to different
> neighbors. The encapsulating tunnel packet will have the source IP
> address of the previous hop neighbor, and will be sent to the next
> hop neighbor, and can be prioritized . Authentication keeps anyone
> from spoofing addresses and stealing bandwidth.

So... now everybody can spy on each other's traffic instead of
also spoofing it. That doesn't seem like a huge improvement to me.

  parent reply	other threads:[~2016-10-06 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  2:12 [WireGuard] auth-only wireguard Jehan Tremback
2016-10-06  5:48 ` Jason A. Donenfeld
2016-10-06 15:03 ` Bruno Wolff III
2016-10-06 16:34   ` Jehan Tremback
2016-10-06 17:35     ` Jason A. Donenfeld
2016-10-06 17:42     ` Alex Xu [this message]
2016-10-06 19:34       ` Jehan Tremback
2016-10-06 17:32   ` Jason A. Donenfeld
2016-10-06 19:27     ` Bruno Wolff III
2016-10-06 20:43       ` 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:
  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=20161006134247.347b1040@alex-archsus \
    --to=alex_y_xu@yahoo.ca \
    --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.