From: Jan De Landtsheer <jan.delandtsheer@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Jan De Landtsheer <jan@delandtsheer.eu>,
Wang Jian <larkwang@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FR: interface ListenAddress (Aka:Multihomed server issue)
Date: Thu, 10 Aug 2017 19:12:27 +0000 [thread overview]
Message-ID: <CABQfmN3EFBL-w3KwLJQMa3HB7_FTrFEFXyQyeJqDtM4yg4DW4Q@mail.gmail.com> (raw)
In-Reply-To: <CABQfmN1fviFhgp1bw82_A9RnZrokch+PmwLZCUMZm=F_doxc5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2955 bytes --]
Forgot to tell :
both versions (server/client) 0.0.20170726
Jan
On Thu, Aug 10, 2017 at 9:10 PM Jan De Landtsheer <
jan.delandtsheer@gmail.com> wrote:
>
> basically this is what happens:
> client connects to 134.56.78.5:443
> wg show gives:
> peer 111.22.33.25:443
>
>
> +----------------------+
> |
> |
> +----------------+ client
> |
> | |
> 81.82.222.111/18 (fixed IP)
> XXXX++XX |
> |
> XXXXXX XXX
> +----------------------+
> XX X XX
> X internet X client config:
> X X XX [interface]
> XX XX peer
> 134.56.78.5:443
> 111.22.33.26/30 |XXX XX
> default gateway | XXXXXXX
> |
> | after connect:
> UPLINK | wg show
> | peer
> 111.22.33.25:443
> |
> +-------------------+-------------------+
> | eth1:111.22.33.25/30 |
> | |
> | router = wg server |
> | |
> | eth0: 134.56.78.1/24 deft gw for 134.56.78.0/24
> | eth0: 134.56.78.5/24 a free ip with open port for 443
> (wg destination)
> +----------------+----------------------+
> |
> |
> |
> |
> |
> +----------------------------+--------------------------------+ also
> 134.56.78.0/24
>
> no nat at all in this setup only some firewall filtering
>
> Jan
>
> On Thu, Aug 10, 2017 at 8:40 PM Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
>
>> Hi Jan,
>>
>> So it looks like this is happening to you:
>>
>>
>> This should not be the behavior, and if it is, you've either found a bug
>> in WireGuard or a bug in your own setup.
>>
>> 1) Are you running the latest snapshot of WireGuard? Which one?
>> 2) "but I don’t know for sure… it seems to be a regression somewhere as
>> I don’t recall to have that problem before…" Can you be more precise?
>> 3) If you are running the latest version, does this patch fix it?
>> http://ix.io/z3d
>> 4) Can you confirm that there exists a route from the server back to the
>> client?
>>
>> Thanks,
>> Jason
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 6970 bytes --]
[-- Attachment #2: rts.jpg --]
[-- Type: image/jpeg, Size: 81200 bytes --]
next prev parent reply other threads:[~2017-08-10 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 9:13 Jan De Landtsheer
2017-08-10 15:51 ` Jason A. Donenfeld
2017-08-10 16:57 ` Jan De Landtsheer
2017-08-10 18:40 ` Jason A. Donenfeld
2017-08-10 19:10 ` Jan De Landtsheer
2017-08-10 19:12 ` Jan De Landtsheer [this message]
2017-08-10 19:46 ` Jason A. Donenfeld
2017-08-10 20:50 ` Jan De Landtsheer
2017-08-10 21:00 ` Jan De Landtsheer
2017-08-10 21:03 ` 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=CABQfmN3EFBL-w3KwLJQMa3HB7_FTrFEFXyQyeJqDtM4yg4DW4Q@mail.gmail.com \
--to=jan.delandtsheer@gmail.com \
--cc=Jason@zx2c4.com \
--cc=jan@delandtsheer.eu \
--cc=larkwang@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).