From: Jonathan Morton <chromatix99@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Valent Turkovic <valent@otvorenamreza.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] routers you can throw off the back of a truck
Date: Tue, 19 Jan 2016 01:06:10 +0200 [thread overview]
Message-ID: <6ACF3DA5-AEA7-43DD-A3BA-33F680374F09@gmail.com> (raw)
In-Reply-To: <23342.1453133686@dooku.sandelman.ca>
> On 18 Jan, 2016, at 18:14, Michael Richardson <mcr@sandelman.ca> wrote:
>
> Jonathan Morton <chromatix99@gmail.com> wrote:
>> I haven’t yet found a robust way to automatically sense link capacity from
>> the upstream side. You’ll therefore need to set a conservative static
>> value for the uplink capacity.
>
> As the maintainer of a PPPoE concentrator, and operator of some networks,
> I've been considering whether one can estimate the bandwidth using round
> trip PPP IPCP keep alives. Clearly, if both ends participate in time
> stamping then it is much better, but I've been wondering if we can do some
> incremental deployment on one side or the other.
>
> Sadly, I mostly just think about this while cycling; I haven't written any
> code yet.
In most PPPoE deployments I know about, there is also a modem from which the actual, precise link rates can usually be queried. Where that’s not the case, IPCP (or is it LPCP?) probes would be a reasonable workaround, but it must still be understood that the signal it provides is only valid under saturating traffic, which complicates implementation.
- Jonathan Morton
next prev parent reply other threads:[~2016-01-18 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 18:46 Dave Taht
2016-01-17 20:31 ` Outback Dingo
2016-01-18 0:45 ` Valent Turkovic
2016-01-18 8:30 ` Jonathan Morton
2016-01-18 9:43 ` Valent Turkovic
2016-01-18 10:51 ` Alan Jenkins
2016-01-18 11:29 ` Jonathan Morton
2016-01-18 14:07 ` Valent Turkovic
2016-01-18 14:07 ` Valent Turkovic
2016-01-18 14:16 ` Valent Turkovic
2016-01-21 23:40 ` Valent Turkovic
2016-01-22 6:37 ` Jonathan Morton
2016-01-22 7:11 ` [Cerowrt-devel] [Make-wifi-fast] " moeller0
2016-03-13 11:17 ` Valent Turkovic
2016-01-18 23:01 ` [Cerowrt-devel] " Jonathan Morton
2016-01-18 16:14 ` Michael Richardson
2016-01-18 23:06 ` Jonathan Morton [this message]
2016-01-19 1:06 ` Michael Richardson
2016-01-22 7:23 ` moeller0
2016-01-22 7:05 ` moeller0
2016-01-18 20:26 ` Dave Taht
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=6ACF3DA5-AEA7-43DD-A3BA-33F680374F09@gmail.com \
--to=chromatix99@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
--cc=valent@otvorenamreza.org \
/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