From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: Richard Brown <richard.e.brown@dartware.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Bufferbloat at upcoming LUG talk
Date: Mon, 26 Nov 2012 10:28:00 -0500 [thread overview]
Message-ID: <11838.1353943680@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw6P-LVda40ODMZ6uospgENSpjpNw--U2tBLdFaedcRfog@mail.gmail.com>
>>>>> "Dave" == Dave Taht <dave.taht@gmail.com> writes:
>> (In general, leaking names is really not that much of a worry...)
Dave> Names, no. Amplification attacks are a serious problem with DNS.
Dave> The internet is rife with worms and daemons that are leveraging open
Dave> dns servers to amplification attacks. In a few short weeks that macej
Dave> had left the port open,
so, there is a difference between leaking names, and providing recursive
service to everyone...
Dave> I've tried very hard to respond to CVEs over the course of this
Dave> project (bind alone, had 5), but I'm away from the lab, in the middle
Dave> of a trip, in between a major upgrade of functionality to cerowrt and
Dave> trying to get funding to re-invigorate this project.
Understood.
Dave> I haven't had much time to hack. None to test.
Dave> I would to get to where we had infrastructure to easily create, test,
Dave> and push out security related fixes.
I wonder if part of the issue is that flashing hardware is a pain in the
butt to do automagically. Were I able to spend paid time on this, I'd
want to do a cerowrt build for x86, or some other trivially virtualized
processor.
>> Use the fountain images that Van Jacobson used at IETF84.
Dave> In my own preso at the lincs, I used my coffee cup...
Dave> There is an interesting preso that shemminger is using that uses soda
Dave> bottles to do something similar to both concepts. Jamming holes into
Dave> it randomly to simulate red....
Dave> I may adopt this - however in explaining fq_codel, I think I need to
Dave> add multiple cups, and an eye-dropper for the ant packets.
sure... in explaining fq_codel, I can see that you need more than the
fountain.
I think that most people need bufferbloat clearly articulated before
they will see that there is a problem that needs fixing, and most
non-network people are still there.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
next prev parent reply other threads:[~2012-11-26 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4092.1353748990.1742.cerowrt-devel@lists.bufferbloat.net>
2012-11-26 1:11 ` Richard Brown
2012-11-26 11:49 ` Dave Taht
2012-11-26 15:37 ` Jim Gettys
2012-11-26 12:26 ` Michael Richardson
2012-11-26 14:00 ` Dave Taht
2012-11-26 15:28 ` Michael Richardson [this message]
[not found] ` <A2E41EFF-2507-457D-9086-06E718192D22@intermapper.com>
2012-12-09 16:56 ` [Cerowrt-devel] Bufferbloat at LUG talk - Meeting Report Richard Brown
2012-12-09 17:32 ` Maciej Soltysiak
2012-12-10 0:16 ` Richard Brown
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=11838.1353943680@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=richard.e.brown@dartware.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