From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] procd support for core daemons?
Date: Sat, 25 Jan 2014 11:50:25 -0500 [thread overview]
Message-ID: <CAA93jw4csUrnw574MZYODGd5Ed4J6rgLcHkHP+SW92of5Azfkg@mail.gmail.com> (raw)
In-Reply-To: <eaea2e09-2548-439c-bcf7-6cb027302e69@email.android.com>
On Sat, Jan 25, 2014 at 11:43 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Left to convert are babeld (which was the only one of the above I
>> really cared about, sadly. I am bogged down on understanding the
>> uci_validate routine).
>
> I mostly care about babeld and tincd. Will look into those when I get a chance, unless you beat me to it...
Well, when I get back to california I have ipv6 capability again so
I'll add tincd to my testlist of the
vpn technologies that may be problematic with source/dst routing...
but I'm done through monday at least. gotta pack.
>> >> http://wiki.openwrt.org/doc/techref/procd
>
> That page is useless...
like all wikis it can be improved.
I left a bunch of documentation behind in the babeld attempt on how
the validator theoretically works.
>
> -Toke
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-01-25 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 16:14 Dave Taht
2014-01-25 16:43 ` Toke Høiland-Jørgensen
2014-01-25 16:50 ` Dave Taht [this message]
2014-01-25 17:06 ` Toke Høiland-Jørgensen
2014-01-25 17:18 ` Dave Taht
2014-01-25 20:23 ` Aaron Wood
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 6:08 Dave Taht
2014-01-22 18:45 ` David Personette
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4csUrnw574MZYODGd5Ed4J6rgLcHkHP+SW92of5Azfkg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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