From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "KeXianbin(http://diyism.com)" <kexianbin@diyism.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [Question or Feature Request] Any wg1.conf option to limit peer IP as 1-to-1?
Date: Mon, 17 Dec 2018 09:54:03 +0100 [thread overview]
Message-ID: <CAHmME9ou8Tt8GAxjw6qcPdmRmVyKShLVrBCJiFRC1KYVZ+KSeQ@mail.gmail.com> (raw)
In-Reply-To: <CAKVinOX5fnvdv1sBvxq=aV3+UpM-g9CnAU9rMu7zrx-WQ9rzVg@mail.gmail.com>
On Mon, Dec 17, 2018 at 9:49 AM KeXianbin(http://diyism.com)
<kexianbin@diyism.com> wrote:
> I found the definition in manual:
> AllowedIPs — a comma-separated list of IP (v4 or v6) addresses with CIDR masks
> from which incoming traffic for this peer is allowed and to which
> outgoing traffic for this peer is directed
>
> from: https://manpages.debian.org/unstable/wireguard-tools/wg.8.en.html
Yes, that is indeed what the man page says and it is the expected
behavior. You've reported here, however, "Currently, the peer can set
any IP, for example 10.1.0.4, and can send packets to my
http://10.1.0.1:80 from 10.1.0.4," which sounds bad and like something
worth taking seriously, if I'm interpreting that correctly. Would you
take the time to create a reproducer similar to what I posted in my
last email?
Thanks,
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-12-17 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 1:42 [Question or Feature Request] Any wg1.conf option to limit peer IP as 1-to-1? KeXianbin(http://diyism.com)
2018-12-17 7:39 ` Jason A. Donenfeld
2018-12-17 7:53 ` KeXianbin(http://diyism.com)
2018-12-17 8:10 ` KeXianbin(http://diyism.com)
2018-12-17 8:49 ` KeXianbin(http://diyism.com)
2018-12-17 8:54 ` Jason A. Donenfeld [this message]
2018-12-17 9:02 ` KeXianbin(http://diyism.com)
2018-12-17 8:50 ` Jason A. Donenfeld
2018-12-17 7:44 ` Tim Weippert
2018-12-17 7:50 ` Jason A. Donenfeld
2018-12-17 7:54 ` Tim Weippert
2018-12-17 8:00 ` KeXianbin(http://diyism.com)
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=CAHmME9ou8Tt8GAxjw6qcPdmRmVyKShLVrBCJiFRC1KYVZ+KSeQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=kexianbin@diyism.com \
--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).