From: Lucian Cristian <luci@createc.ro>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>,
"jason A. Donenfeld" <Jason@zx2c4.com>
Subject: wg-quick add_route
Date: Wed, 12 Jul 2017 20:53:01 +0300 [thread overview]
Message-ID: <fe5fcf1b-a7d1-6f6c-1561-4b1b1fa4e326@createc.ro> (raw)
Hi Jason,
I'm using wireguard in some mixed topology and until now I've had LEDE
routers as clients but now I would like to add some CENTOS(and other
distros) clients too.
On LEDE there is an option "Create routes for Allowed IPs for this peer"
that is off by default, but in wg-quick this thing is not optional and
the routes are created by default, so if I would like to allow
10.0.0.0/8 it would create default route for all 10.0.0.0/8 to wg
interface and I don't want that.
I would like to use dynamic routing (rip+eigrp) for routing, if you
could add an entry to peers not to add default route to allowed ip would
be great
until then I've disabled add_route rule in the script
Regards
next reply other threads:[~2017-07-12 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 17:53 Lucian Cristian [this message]
2017-10-27 17:23 ` Fwd: " Lucian Cristian
2017-10-27 19:48 ` Jason A. Donenfeld
2017-10-27 20:59 ` Lucian Cristian
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=fe5fcf1b-a7d1-6f6c-1561-4b1b1fa4e326@createc.ro \
--to=luci@createc.ro \
--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).