From: "Vojtěch Káně" <email@example.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <firstname.lastname@example.org>
Subject: Re: Strange behavior when a peer has the same key as the interface
Date: Sun, 5 Sep 2021 22:27:25 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
> This is by design across all implementations, so that multiple peers can share the same stanzas after the [Interface] section.
Does that mean it's unfixable in the meaning you cannot detect it and
return appropriate error?
While being clearly my mistake, it took me multiple hours to understand
the problem instead of simply getting `cannot set peer foo as it already
is a public key of interface bar`.
next prev parent reply other threads:[~2021-09-05 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 7:24 Vojtěch Káně
2021-09-05 13:24 ` Jason A. Donenfeld
2021-09-05 20:27 ` Vojtěch Káně [this message]
2021-09-05 20:54 ` Jason A. Donenfeld
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 \
* 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).