From: Andy Dorman <adorman@ironicdesign.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Cc: Ironic Design Development <devel@lists.ironicdesign.com>
Subject: Re: wg0 packets not being routed? FIXED!
Date: Thu, 3 May 2018 21:53:46 -0500 [thread overview]
Message-ID: <2f57d1a5-1814-3f04-211d-94971b1a6f03@ironicdesign.com> (raw)
In-Reply-To: <CAHmME9o+yduX0kbM0BV1qqGBbyf83XHi6bmcTSFXqzmVHw=FfQ@mail.gmail.com>
On 5/3/18 7:15 PM, Jason A. Donenfeld wrote:
> ip route add 192.168.100.0/24 dev wg0
Thank you everyone, that was it. Once I added an explicit route for the
remote IP block on each server it ALL worked (and latency is pretty
good, under 30ms over about a 10-hop route).
Somehow I had gotten the idea that the setup was more complicated if I
used the same IP block on both ends of the VPN. I am pretty sure I did
NOT get that from the wireguard.com web site. When I find the doc that
mislead me I will work with the author to make it clearer for a nube
like me.
Thank you again.
--
Andy
prev parent reply other threads:[~2018-05-04 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 21:53 wg0 packets not being routed? Andy Dorman
2018-05-03 23:03 ` jens
2018-05-03 23:37 ` Germano Massullo
2018-05-04 0:15 ` Jason A. Donenfeld
2018-05-04 2:53 ` Andy Dorman [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=2f57d1a5-1814-3f04-211d-94971b1a6f03@ironicdesign.com \
--to=adorman@ironicdesign.com \
--cc=devel@lists.ironicdesign.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.