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 > 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 >> ​ >> >