From: Varun Priolkar <me@varunpriolkar.com>
To: Aaron Jones <aaronmdjones@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Server with multiple peers
Date: Sat, 6 Apr 2019 00:17:49 +0530 [thread overview]
Message-ID: <CALwBDFsG5zJb_qLO4oLa6vH-U5QA=ACKFh7jOXtyE3Afd2xumg@mail.gmail.com> (raw)
In-Reply-To: <09129085-bbbe-79da-3b03-2e41c67eafac@gmail.com>
If you really want to do something like this(I'm not sure why), don't
add the route via Wireguard. You can instead use iBGP multipath or
ECMP to do this.
On Fri, Apr 5, 2019 at 9:01 PM Aaron Jones <aaronmdjones@gmail.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 30/03/2019 00:45, Indro Fedrigo wrote:
> > Hi Jason, I'm trying to create a server with multiple peers form a
> > wgx.conf file : the parameter AllowedIPs seems to get set only for
> > the last peer... Any idea ? Thanks for this great piece of
> > software! Indro Fedrigo
>
> You cannot duplicate AllowedIPs. It forms WireGuard's internal routing
> table. You're essentially asking for "If we have traffic to
> 192.168/16, send it to peer A, and also to peer B, and also to peer C,
> and also to peer D".
>
> That doesn't work.
>
> - --
> Aaron Jones
>
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCgAdFiEEYKVBwe43zZh/jkxPivBzdIirMBIFAlyndKEACgkQivBzdIir
> MBLnIRAAp3UURDFtevTlWUSwgKiVyzN9eT6MGtHi1owDOSVafWPoHJ+pM2PGkPj9
> v2aJsgeJK6cIC6j23F8G0ombgGsVaNFTVjeOLNThzgkv2DXJhgWjDu1iuyUmlAI6
> ZSuZ9ccd+OPa3YMGX9apGTeulvVjYGs06yJ5xpgCsqIMhCnj/XOS9HoWrGDWHqOA
> 3AZJK9/i3jIXQHYPSCpdXrppNCw8APQWgNuB1aDPdBMcw8bgARiJzWDF7Q2xBPxx
> SXS2PnFp9oG3+CNqGpEKnurUfx6QSGDPVps6a33HGpdTTAfyZw1Ha8ZSQgb3Yzt0
> U1JWxhLAF+o9ubkK0n9Q0jaunrDfDbbuPmvNF3ZAAkKmITsXPSieT0WB6kXk7l0K
> HZbyEexGLwrCTbLhublIazxQZsJe+ftz8liOrQr3/arGKS1NYItRV0nRKKVSR5Xx
> CsUV4Ngz2Wm+gFaET4QmEJJCARY+LNV+Ntrm+R+s+5vgGK1AJ4iRfR2vYt9dotje
> NiyHqF3FTFpqNK/tZ4CXgROniAmqJs5R4MRRqE5cgEsX8te5iDeCbtZPaAQepECj
> +tWhd10//pjr0G5PajPD8bzIWU2cgHT6JkqwA4l/ibR5EaJm7LQvS0ppUVzS6poy
> bbY0YILEtPSkDioZhxkZ3GTR2rAmE5lcGdW054CYDEdhfx9bYGo=
> =6Gmi
> -----END PGP SIGNATURE-----
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
--
Regards,
Varun Priolkar
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-04-06 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 0:45 Indro Fedrigo
2019-04-05 15:30 ` Aaron Jones
2019-04-05 18:47 ` Varun Priolkar [this message]
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='CALwBDFsG5zJb_qLO4oLa6vH-U5QA=ACKFh7jOXtyE3Afd2xumg@mail.gmail.com' \
--to=me@varunpriolkar.com \
--cc=aaronmdjones@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).