From: David Lang <david@lang.hm>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.24-5 dev build released
Date: Tue, 17 Dec 2013 20:34:32 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1312172030440.10231@nftneq.ynat.uz> (raw)
In-Reply-To: <22176178-A50F-48F2-A3A1-D3853764AD0E@gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 1181 bytes --]
On Tue, 17 Dec 2013, Rich Brown wrote:
> - From what you’ve said, I don’t have much hope for doing it automagically.
> But maybe we can provide clues to help the customer do to the right thing.
> Perhaps the first dropdown could be “Link Layer Adjustments (used on DSL or
> ATM)” with options for “None/ADSL/SDSL/VDSL over PTM/VDSL over ATM/PPPoATM”
> and maybe others. CeroWrt could automatically set the proper link layer
> adaptations for each. We could also include a link to the wiki for a flow
> chart for setting each of these cases, especially the questions they should
> ask their ISP.
Let's start with the first question, what is the difference between these as far
as what the config should be?
forget the GUI or automated settings. If I am configuring a Cerowrt box
mmanually, what should I set differently for the different types of configs?
What is the impact of getting it wrong? (if it's like VPN overhead where setting
the rate just slightly too high results is lots of wasted 'airtime' by setting
it too low results is a amall amount of wasted 'airtime' then a low enough value
to be reasonalbe everywere is a good default)
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 164 bytes --]
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-12-18 4:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 7:23 Dave Taht
2013-12-16 7:34 ` Dave Taht
2013-12-16 13:45 ` Rich Brown
2013-12-16 14:15 ` Sebastian Moeller
2013-12-17 3:45 ` Rich Brown
2013-12-17 9:31 ` Sebastian Moeller
2013-12-18 3:06 ` Rich Brown
2013-12-18 4:34 ` David Lang [this message]
2013-12-18 10:33 ` Sebastian Moeller
2013-12-18 11:27 ` Fred Stratton
2013-12-18 11:59 ` Sebastian Moeller
2013-12-18 13:24 ` Fred Stratton
2013-12-18 13:58 ` Rich Brown
2013-12-18 22:43 ` Sebastian Moeller
2013-12-19 4:12 ` Rich Brown
2013-12-19 10:49 ` Sebastian Moeller
[not found] ` <52B2D917.6080006@imap.cc>
2013-12-19 11:32 ` Fred Stratton
2013-12-19 13:13 ` Sebastian Moeller
2013-12-19 13:35 ` Fred Stratton
2013-12-20 18:01 ` Dave Taht
2013-12-20 20:51 ` Sebastian Moeller
2013-12-21 2:39 ` Dave Taht
2013-12-20 21:01 ` Sebastian Moeller
2013-12-21 0:34 ` Dave Taht
2013-12-21 9:36 ` Sebastian Moeller
2013-12-19 13:42 ` [Cerowrt-devel] CeroWrt 3.10 AQM page Rich Brown
2013-12-19 14:24 ` Fred Stratton
2013-12-19 15:07 ` Sebastian Moeller
2013-12-19 15:27 ` Fred Stratton
2013-12-20 10:12 ` Sebastian Moeller
2013-12-20 10:33 ` Fred Stratton
2013-12-20 10:45 ` Sebastian Moeller
2013-12-20 17:34 ` Dave Taht
2013-12-20 21:25 ` Rich Brown
2013-12-20 21:40 ` Sebastian Moeller
2013-12-21 0:37 ` Rich Brown
2013-12-21 10:01 ` Sebastian Moeller
2013-12-18 9:16 ` [Cerowrt-devel] cerowrt-3.10.24-5 dev build released Sebastian Moeller
2013-12-16 14:48 ` Fred Stratton
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.1312172030440.10231@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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