Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: jens <jens@viisauksena.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg set allowed ip confusion
Date: Wed, 4 Jan 2017 22:15:42 +0100	[thread overview]
Message-ID: <CAHmME9rakpxbx+YU=_TnNqjJYSbACO+K6SPdRw4PZrwxAV5sqg@mail.gmail.com> (raw)
In-Reply-To: <5674e440-84df-dab2-41ef-327cf61dca1e@viisauksena.de>

Hi Jens,

One peer, one IP. The routing enforces a 1:1 relationship. So no, you
can't do this. But I sincerely doubt you would even want to do this.

On your server, each peer's allowed IPs should probably be a /32 of
the actual internal IP address of the peer.

The front page of wireguard.io has an illustrative example
configuration of a client-server topology:
https://www.wireguard.io/#cryptokey-routing

Jason

  reply	other threads:[~2017-01-04 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 21:10 jens
2017-01-04 21:15 ` Jason A. Donenfeld [this message]
2017-01-04 21:21   ` jens

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='CAHmME9rakpxbx+YU=_TnNqjJYSbACO+K6SPdRw4PZrwxAV5sqg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=jens@viisauksena.de \
    --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).