Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
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: Wed, 18 Dec 2013 23:43:13 +0100	[thread overview]
Message-ID: <1FA2FD44-D715-4B50-BB5A-BAF61070970B@gmx.de> (raw)
In-Reply-To: <0E267F91-3CC8-48F4-92C0-AD8BACA98FCC@gmail.com>

Hi Rich,


On Dec 18, 2013, at 14:58 , Rich Brown <richb.hanover@gmail.com> wrote:

> I like David Lang’s questions:
> 
> 1) If we had “full knowledge” of the customer’s link, how many different cases would we have to take into account?
> 
> 2) What happens if we get it wrong?
> 
> And I think I understand Sebastian Moeller’s answers:
> 
> 1) People using ATM-based carriers need the ATM link layer adaptation calculation; others (PTM, Cable, Fiber, etc.) don’t need that calculation.

	Except even with PTM or Fiber there still might be the need to specify an overhead (e.g. 8 bytes for PPPoE) in this case one needs to select the "ethernet" link layer...

> 
> 2) Getting it wrong hurts in each case, but it seems worse where people are using PTM or Ethernet-based links since they lose 10% of their bandwidth due to the 48 in 53 bytes encapsulation. Failure to use the ATM calculation over an ATM-based link makes VoIP etc. less good and fails to make CeroWrt stand out as a great solution, but it’s the status quo for the entire world.

	Or we could say, the default should be ATM so that the ATM latency is under control again, while PTM users just sacrifice some (considerable) amount of bandwidth :)


> 
> If the choices are as “simple” as this (and please correct me if I’m wrong :-) we really want to find a way to encourage people to use the ATM calculation when it’s warranted. We could hope that they find their way to the AQM tab (before their eyes glaze over), but that seems too big a hurdle.

	So I changed the link layer tab a bit, hopefully making clearer which link layer to select...

> 
> Perhaps we could extend the Interface configuration page to add a “Link uses DSL/ADSL:” checkbox right below the Protocol dropdown. Default would be off, but when customers go to the GE00 interface to enter their PPPoE/PPPoATM/ISP credentials, they’d see this additional checkbox. Checking it would feed that info to the AQM tab. (And perhaps there could be a link there either to the AQM tab, or to the wiki for more information.)

	I am happy to include a link to a wiki, but I guess we first need a wiki page :) 

Best
	Sebastian

> 
> Best,
> 
> Rich


  reply	other threads:[~2013-12-18 22:43 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
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 [this message]
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=1FA2FD44-D715-4B50-BB5A-BAF61070970B@gmx.de \
    --to=moeller0@gmx.de \
    --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