Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: Evan Hunt <each@isc.org>,
	cerowrt@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] stuff that can be dropped from rc8 #113
Date: Tue, 6 Dec 2011 11:19:07 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1112061115410.11705@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw7SLm0MyCWzzVPYO9PXnTJhF7RbMXSExRL-M5pqs3etjQ@mail.gmail.com>

neither of these tools are relavent to bufferbloat, so I don't see any 
reason to use them in cerowrt.

be very leery of including stuff because its 'good' or it's the 'right 
way to do things'

if it's not commonly deployed today, there are probably reasons for that. 
pick your battles. Cerowrt is not designed to make a 'next gen frouter', 
it's to research fixes for bufferbloat, If a tool doesn't directly affect 
bufferbloat, use the default instead.

David Lang

On Tue, 6 Dec 2011, Dave Taht wrote:

> What I am going to try to do here is outline the packages we can
> easily drop from rc8
> in order to meet the main goals of cerowrt - first and foremost -
> creating a test tool to
> help fix bufferbloat. We can always add this stuff back in later, with
> funding, or with
> people (other than me) doing the development, build, integration, and test work.
>
> This involves making some hard choices about reducing things on the roadmap
> down to a sane level on the amount of resources we will have next quarter.
>
> http://www.bufferbloat.net/projects/cerowrt/roadmap
>
> 1) bind9.
>
> I'm glad we got it working. It's a great proof of concept. Seeing
> DNSSEC work was awesome
>
> A) However, bind-latest doesn't build anymore for some reason, and I
> don't know why.
> B) until bug #113 is fixed - and it sure as hell doesn't need to be
> fixed on a embedded system -
>    there's no point in DNSSEC. Nobody has fixed it, we simply don't
> have the resources to
>    do it ourselves.
> C) even with 'proof of concept' of the dhcp-dns automagic naming
> scheme, we have no
>    working version of that now that can be applied for general usage.
> This too, does
>    not need to be developed on an embeddded system.
>
> D) dnsmasq is better integrated with the gui and 'just works
>
> 2) ISC-ntp
>
> A) It's big, complex, and ALSO isn't building at the moment.
> B) busybox-ntp is integrated with the gui and just works.
>
> I note we can make a step forward towards getting dnssec to work right
> by hacking up
> that version of ntp to do pre and post 'I got time' scripts.
>
> As for bug #113
>
> I have poked deeply into the uclibc library and discovered it's
> getaddrinfo routine
> is a cheap hack on top of gethostbyname. Poking into ntp itself did not show
> a decent concept of 'get dns, fail, try something else, then validate'...
>
> But:
>
> I'm not expert at any of these subsystems, and me spending any more time on it
> than I already have this year does not seem productive.
>
> Eliminating these two packages from the build knocks out bugs #113, #205,
> #239, #238, #233, #280, #281. It would be good to throw all these over the
> wall to isc's bug system and have tracking numbers to deal with there.
>
>

      reply	other threads:[~2011-12-06 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 16:15 Dave Taht
2011-12-06 19:19 ` david [this message]

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=alpine.DEB.2.02.1112061115410.11705@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=each@isc.org \
    /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