WireGuard Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: "Ivan Labáth" <labawi-wg@matrix-dream.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] wg set - unexpected change of routes
Date: Tue, 30 Aug 2016 10:44:39 -0500	[thread overview]
Message-ID: <20160830154439.GA5923@wolff.to> (raw)
In-Reply-To: <20160830064454.GA12680@matrix-dream.net>

On Tue, Aug 30, 2016 at 07:44:54 +0100,
  Ivan Labáth <labawi-wg@matrix-dream.net> wrote:
>
>I think repeating subnets in different peers is most probably
>an error and in such circumstances the most useful action would
>be to fail and report it as such.

Except in some cases it is convenient to use a large network for one peer 
and carve out a small subnet in another. Having to list a big subnet with 
a carve out as the sum of smaller networks can be a big pain.

  reply	other threads:[~2016-08-30 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  6:44 [WireGuard] wg set - unexpected change of routes Ivan Labáth
2016-08-30 15:44 ` Bruno Wolff III [this message]
2016-08-30 19:27   ` Ivan Labáth
2016-08-30 19:37     ` Dave Taht

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=20160830154439.GA5923@wolff.to \
    --to=bruno@wolff.to \
    --cc=labawi-wg@matrix-dream.net \
    --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