From: "Dan Lüdtke" <mail@danrl.com>
To: Nicolas Prochazka <nicolas.prochazka@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ wireguard-dev ] About configuring allowedip
Date: Thu, 23 Feb 2017 14:41:47 +0100 [thread overview]
Message-ID: <241066D3-A3AD-4E76-B7E0-9C0DC26713D6@danrl.com> (raw)
In-Reply-To: <CADdae-h1pmyzn5aTsnBG5nBaKCuLk03eu0wtQ0E1V0j+nBZsiA@mail.gmail.com>
Nicolas: Could you provide the configuration files? Because from your =
little graphic or schema I can not even derive what you are configuring. =
I guess there is something overlapping prefixes maybe?
Jason: I think we are approaching the point in time when there will be a =
-dev and a -users ML :)
> On 23 Feb 2017, at 14:03, Nicolas Prochazka =
<nicolas.prochazka@gmail.com> wrote:
>=20
> Hello, i'm trying to do this with wireguard, withtout success :=20
>=20
> peer1 ---> peer2 : config ok , works
> peer3 ---> peer1 : config ok , works=20
> peer3 --->peer1 ---> peer2 : not ok .
>=20
> I suspect allowed-ip configuration, but all my tests does not works.
> perhaps I must create two wireguard interface on peer 1 and do =
forwarding/routing ?=20
> i'm using ipv6 as internal ip.
>=20
> so my question is :=20
> - two interface ?
> - specifiq magic allowedip ?
> ( allowed ip is confusing for, it is using for routing and for =
evicting paquet ? )
>=20
> Regards,=20
> Nicolas=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2017-02-23 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 13:03 Nicolas Prochazka
2017-02-23 13:41 ` Dan Lüdtke [this message]
2017-02-24 10:41 ` Nicolas Prochazka
2017-02-24 13:10 ` Dan Lüdtke
2017-02-24 15:06 ` Nicolas Prochazka
2017-02-23 21:16 ` Baptiste Jonglez
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=241066D3-A3AD-4E76-B7E0-9C0DC26713D6@danrl.com \
--to=mail@danrl.com \
--cc=nicolas.prochazka@gmail.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).