From: Michael Richardson <mcr@sandelman.ca>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Bufferbloat at upcoming LUG talk
Date: Mon, 26 Nov 2012 07:26:40 -0500 [thread overview]
Message-ID: <10146.1353932800@obiwan.sandelman.ca> (raw)
In-Reply-To: <54532012A5393D4E8F57704A4D55237E3CDE473A@CH1PRD0510MB381.namprd05.prod.outlook.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2170 bytes --]
>>>>> "Richard" == Richard Brown <richard.e.brown@dartware.com> writes:
Richard> - I can see how the CeroWrt de-bloating algorithms help
Richard> protect against bad latency when I'm *uploading* big
Richard> files. I'm not sure whether using CeroWrt with its
Richard> CoDel/FQ/SFQ/etc. helps when I'm downloading big files,
Richard> though. What can I say about this?
If the link from the broadband to the laptop is wireless, than it's
quite possible that the wireless link experiences bufferbloat.
This would be true:
- if the laptop is far from the base station the rate could be
lower than the broadband download link. (Especially now that
cable offers 50Mb/s downlinks...)
- if the wireless is bridged to wired, and there are many windows
boxes, broadcasting a lot, then the wireless link may be
otherwise saturated
bad uplink latency will affect TCP ACKs, and can totally ruin your
interactive ssh day too.
But, in general, either the ISP has to debloat too, or it has to rate
limit to below the actual bandwidth.
Richard> - I believe the default DNS server in Sugarland is dnsmasq,
Richard> not bind. Is DNSSEC enabled by default? Also: there's a
Richard> report (Bug #411) that says that DNS is leaking internal
Richard> names to the outside world. What's the best advice for
Richard> closing this? ("list notinterface 'ge00'" is one
Richard> recommendation
)
(In general, leaking names is really not that much of a worry...)
Richard> My plan is to give a little of the science behind
Richard> bufferbloat mitigation and also put in a plug for
Richard> CeroWrt. Any topics I haven't already mentioned that I
Richard> should? Thanks!
Use the fountain images that Van Jacobson used at IETF84.
--
] 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 12:27 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 [this message]
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=10146.1353932800@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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