From: Wang Jian <larkwang@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multihomed server issue
Date: Tue, 1 Aug 2017 19:28:39 +0800 [thread overview]
Message-ID: <CAF75rJD7ZcSKp6WiEHg+VUa7=07-+9P3r6TxU6s9ieW+LdkNhQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pujFf3pUAr9NZK81DZMQHYsH1gvgh3uH6RAQwNEZ8JDA@mail.gmail.com>
2017-08-01 11:06 GMT+08:00 Jason A. Donenfeld <Jason@zx2c4.com>:
> On Tue, Aug 1, 2017 at 4:01 AM, Wang Jian <larkwang@gmail.com> wrote:
>> 2017-07-31 23:34 GMT+08:00 Jason A. Donenfeld <Jason@zx2c4.com>:
>>> On Fri, Jul 28, 2017 at 2:51 AM, Wang Jian <larkwang@gmail.com> wrote:
>>>> The solution can be one of:
>>>>
>>>> 1. server can RTS (response to source), or can bind to arbitary
>>>> address for outgoing
>>>
>>> The server does already respond to source.
>>
>> Sorry, I didn't make it clear. By saying RTS, I mean response to
>> source link, that is,
>> using called address and incoming link.
>
> You're still unclear to me. What?
Let's say server has multiple interfaces, eth0, eth1, ... ethN, with
IP0, IP1, ... IPn,
If an incoming request is to eth1, to IP1, then the server's response
packet will go out from eth1, and source is IP1.
In some cases, it can be done using policy routing, but other cases not. I know
a FreeBSD based VPN implements so called RTS.
In my case, the server looks like
eth0 = 10.1.1.2/24 (default route, via 10.1.1.1/24)
eth1.100 = 172.16.1.2/30 (policy routing: when source address
is 111.111.1.0/24, route via 172.16.1.1/30)
eth1.200 = 172.16.2.2/30 (policy routing: when source address
is 111.111.2.0/24, route via 172.16.2.1/30)
dummy0 = 111.111.1.2/24
dummy1 = 111.111.2.2/24
When a wireguard client contacts 111.111.1.2, the server responses UDP packet
with source address 10.1.1.2 but not the desired 111.111.1.2, because
of default route.
I have mailed you my network setup privately. Sorry for inconvenience.
next prev parent reply other threads:[~2017-08-01 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 0:51 Wang Jian
2017-07-31 15:34 ` Jason A. Donenfeld
2017-08-01 2:01 ` Wang Jian
2017-08-01 3:06 ` Jason A. Donenfeld
2017-08-01 11:28 ` Wang Jian [this message]
2017-08-03 3:00 ` Wang Jian
2017-08-03 12:59 ` Jason A. Donenfeld
2017-08-03 18:38 ` Wang Jian
2017-08-10 14:29 ` Jason A. Donenfeld
2017-08-10 18:43 ` Jason A. Donenfeld
2017-08-10 21:17 ` Jan De Landtsheer
2017-08-10 22:16 ` Baptiste Jonglez
2017-08-10 23:50 ` Jason A. Donenfeld
2017-08-12 1:55 ` Jason A. Donenfeld
2017-08-12 16:08 ` Wang Jian
2017-09-07 21:28 ` Jason A. Donenfeld
2017-09-09 8:26 ` Wang Jian
2017-09-20 13:15 ` Jason A. Donenfeld
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='CAF75rJD7ZcSKp6WiEHg+VUa7=07-+9P3r6TxU6s9ieW+LdkNhQ@mail.gmail.com' \
--to=larkwang@gmail.com \
--cc=Jason@zx2c4.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).