From: Richard Brown <richard.e.brown@dartware.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Bufferbloat at upcoming LUG talk
Date: Mon, 26 Nov 2012 01:11:31 +0000 [thread overview]
Message-ID: <54532012A5393D4E8F57704A4D55237E3CDE473A@CH1PRD0510MB381.namprd05.prod.outlook.com> (raw)
In-Reply-To: <mailman.4092.1353748990.1742.cerowrt-devel@lists.bufferbloat.net>
Folks,
I am planning to give a talk about Bufferbloat to the local Linux User Group next week (http://dlslug.org). All this traffic on the list is fantastic, because it gives me a lot of background on the current state of bufferbloat. I've pulled together a bunch of general questions about CeroWrt that I would like to be able to cover if they come up:
- Is it true that the latest CeroWrt is Sugarland 3.3.8-26 from mid-September? (My router is using this build - r33460.)
- I see the "QoS" item in the Network tab of the web GUI. Is this important for Sugarland? Or does some other router configuration take care of this now?
- What's the relationship between the QoS GUI item above and the debloat.sh and simple_qos.sh scripts that have been mentioned on this list? What's the best practice here for getting a router up and running?
- I can see how the CeroWrt de-bloating algorithms help protect against bad latency when I'm *uploading* big files. I'm not sure whether using CeroWrt with its CoDel/FQ/SFQ/etc. helps when I'm downloading big files, though. What can I say about this?
- I believe the default DNS server in Sugarland is dnsmasq, not bind. Is DNSSEC enabled by default? Also: there's a report (Bug #411) that says that DNS is leaking internal names to the outside world. What's the best advice for closing this? ("list notinterface 'ge00'" is one recommendation…)
- I've been assembling information about the various de-bloating techniques implemented in CeroWrt. It seems that Infoblox has recently reorganized their blogs, and the links published earlier this week have all broken. Here are updates:
http://www.infoblox.com/community/blog/application-analysis-using-tcp-retransmissions-part-1
http://www.infoblox.com/community/blog/application-analysis-using-tcp-retransmissions-part-2
http://www.infoblox.com/community/blog/router-buffer-tuning
http://www.infoblox.com/community/blog/rethinking-interface-error-reports
My plan is to give a little of the science behind bufferbloat mitigation and also put in a plug for CeroWrt. Any topics I haven't already mentioned that I should? Thanks!
Rich Brown
Hanover, NH USA
next parent reply other threads:[~2012-11-26 1:12 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 [this message]
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
[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=54532012A5393D4E8F57704A4D55237E3CDE473A@CH1PRD0510MB381.namprd05.prod.outlook.com \
--to=richard.e.brown@dartware.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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