From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dan Luedtke <mail@danrl.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: openwrt route_allowed_ips is inprecise
Date: Tue, 20 Dec 2016 05:33:11 +0100 [thread overview]
Message-ID: <CAHmME9popkFYu-am43TMCc6NcPtUA5dYRWPuTDJS-B69L73_cQ@mail.gmail.com> (raw)
In-Reply-To: <89D5D16F-84AF-4FC6-9AA1-55EFCB6A3B9E@danrl.com>
On Tue, Dec 20, 2016 at 4:38 AM, Dan Luedtke <mail@danrl.com> wrote:
> No objection but a remark: It is now even more complex and I think shell script is not the right solution.
This is *not* a complex algorithm and can be implemented correctly in
shell. It's on my list for tomorrow to actually clean that up.
> This is pretty straightforward with netlink
No, it's much less straight-forward with raw netlink. Raw netlink
involves hundreds of lines of code to do anything at all. A real mess.
Fortunately there are wrapper libraries you can use from various
languages to make it easier.
> Regarding LEDE, netifd should track the routes being added and the extra routes do not really do harm.
Alright then...
Speaking of netifd, did you ever fix that netifd issue with the IP dependency?
next prev parent reply other threads:[~2016-12-20 4:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 20:14 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
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 [this message]
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=CAHmME9popkFYu-am43TMCc6NcPtUA5dYRWPuTDJS-B69L73_cQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=mail@danrl.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).