From: Guy Godfroy <guy.godfroy@gugod.fr>
To: wireguard@lists.zx2c4.com
Subject: Suggestion for WireGuard
Date: Thu, 2 Sep 2021 04:10:05 +0000 (UTC) [thread overview]
Message-ID: <12daa07c-f2c5-483c-9c64-7e9a51efd0c6@gugod.fr> (raw)
In-Reply-To: <CAJaZ5dPHbc5s=JiCbuBKAGf1Nb3vw0xL9W7_=Na4Skt_pjnWZw@mail.gmail.com>
Hello,
I'm not implied in wireguard dev, but I thinks that wouldn't match wireguard mechanism. Indeed AllowedIP isn't only about routing, it is used to match a cryptographic fingerprint to a given IP. Also, having multiple peers containing such thing as DisallowedIP could lead to nonsense.
What don't you use the firewall to block the IP range instead?
next prev parent reply other threads:[~2021-09-02 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:19 Suggestion for WireGuard Kassem Omega
2021-09-02 4:10 ` Guy Godfroy [this message]
2021-09-02 4:54 ` Feng Li
2021-09-02 13:46 ` Lonnie Abelbeck
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=12daa07c-f2c5-483c-9c64-7e9a51efd0c6@gugod.fr \
--to=guy.godfroy@gugod.fr \
--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.