All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andy Dorman <adorman@ironicdesign.com>
Cc: Ironic Design Development <devel@lists.ironicdesign.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg0 packets not being routed?
Date: Fri, 4 May 2018 02:15:32 +0200	[thread overview]
Message-ID: <CAHmME9o+yduX0kbM0BV1qqGBbyf83XHi6bmcTSFXqzmVHw=FfQ@mail.gmail.com> (raw)
In-Reply-To: <8599540b-b761-57a1-a585-b4395f9bed96@ironicdesign.com>

Hello Andy,

The mistake you've made is that your NOC servers don't have a route
indicating that 192.168.100.0/24 should go to wg0, and likely your
Linode server doesn't have a route indicating that 192.168.99.0/25
should go to wg0. Instead, packets to these addresses are going out of
your default route, which is to the Internet, which rightfully rejects
RFC1918 addresses.

You can fix this in two ways:

1) Just use 192.168.99.0/24 addresses on both sides, so the route can
be inferred from the IP you're using. Or,

2) If you want to keep your existing structures of subnets, then just
add those routes:

nocbox $ ip route add 192.168.100.0/24 dev wg0
linode $ ip route add 192.168.99.0/24 dev wg0

If you're using wg-quick(8) to configure things, this will be taken
care of automatically, by the way.

Jason

  parent reply	other threads:[~2018-05-04  0:13 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 [this message]
2018-05-04  2:53   ` wg0 packets not being routed? FIXED! Andy Dorman

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='CAHmME9o+yduX0kbM0BV1qqGBbyf83XHi6bmcTSFXqzmVHw=FfQ@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=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.