From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: openwrt route_allowed_ips is inprecise
Date: Mon, 19 Dec 2016 14:09:33 +0100 [thread overview]
Message-ID: <CAHmME9qEg6iBwWpwgT_oPPGymfccuOdAyHv1e4+n5c-O8n9=4g@mail.gmail.com> (raw)
In-Reply-To: <20161219130602.GA12378@tuxmachine.polynome.dn42>
On Mon, Dec 19, 2016 at 2:06 PM, Baptiste Jonglez
<baptiste@bitsofnetworks.org> wrote:
> Please provide numbers. I would be very surprised if a few redundant
> routes have any performance impact, given that the kernel can handle 600k
> routes without major issues.
I'm thinking about the case in which a server has a 10/8 of clients,
each of which gets a /32. In this case quite a few routes wind up in
the table...
Fortunately the change is pretty easy. Instead of running
`proto_add_ipv4_route ...` you run:
[[ $(ip route get "$i") != *dev\ $INTERFACE\ * ]] && proto_add_ipv4_route ...
next prev parent reply other threads:[~2016-12-19 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 20:14 openwrt route_allowed_ips is inprecise Jason A. Donenfeld
2016-12-19 8:00 ` Jörg Thalheim
2016-12-19 12:32 ` Jason A. Donenfeld
2016-12-19 13:06 ` Baptiste Jonglez
2016-12-19 13:09 ` Jason A. Donenfeld [this message]
2016-12-19 13:19 ` Baptiste Jonglez
2016-12-19 13:21 ` Jason A. Donenfeld
2016-12-20 1:13 ` Baptiste Jonglez
2016-12-20 3:14 ` Jason A. Donenfeld
2016-12-20 3:38 ` Dan Luedtke
2016-12-20 4:33 ` Jason A. Donenfeld
2016-12-20 8:52 ` Dan Lüdtke
2016-12-20 10:15 ` Dan Lüdtke
2016-12-20 13:33 ` Jason A. Donenfeld
2016-12-20 14:51 ` Dan Lüdtke
2016-12-20 18:27 ` 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='CAHmME9qEg6iBwWpwgT_oPPGymfccuOdAyHv1e4+n5c-O8n9=4g@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=baptiste@bitsofnetworks.org \
--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.