From: d tbsky <tbskyd@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Feature Request for Multihomed Endpoints
Date: Fri, 19 Apr 2019 08:20:56 +0800 [thread overview]
Message-ID: <CAC6SzHJfx0Cc7mCu7oxynYCtngZRTsHH3cfYE3BxwsERocCw+g@mail.gmail.com> (raw)
In-Reply-To: <676a8baf337fbc174cd065143da771e3@mitteilung.com>
Markus Grundmann <markus@activezone.de>
> I wish the endpoint was able to pick a explicit outgoing IP address to connect the other endpoint over the 802.3ad interface but the uplink interface address is not recommend for me. What do you think about it?
if you search the mail list, you will find this had been discussed
several times these years. last year under rhel7 I could make a
multi-home environment which wireguard can not work reliably. however
I can not reproduce it under netns so can not debug it further.
I wonder if there is simple netns configuration to force wireguard
binding specific ip address?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-04-19 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 2:51 Markus Grundmann
2019-04-19 0:20 ` d tbsky [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=CAC6SzHJfx0Cc7mCu7oxynYCtngZRTsHH3cfYE3BxwsERocCw+g@mail.gmail.com \
--to=tbskyd@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).