From: Michael Richardson <mcr@sandelman.ca>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Valent Turkovic <valent@otvorenamreza.org>,
"cerowrt-devel\@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] routers you can throw off the back of a truck
Date: Mon, 18 Jan 2016 20:06:26 -0500 [thread overview]
Message-ID: <31692.1453165586@obiwan.sandelman.ca> (raw)
In-Reply-To: <6ACF3DA5-AEA7-43DD-A3BA-33F680374F09@gmail.com>
Jonathan Morton <chromatix99@gmail.com> 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.
Yes, you are rtight, I want to do LPCP echo requests.
The modem might know what speed it has with the tower/DSLAM, but won't know how
congested the backhaul link is. There are some third party/white label 3G
arrangements in Canada that use PPP/L2TP back to the third-party provider,
but most route the IPv4 (only) packets via IPsec or MPLS.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2016-01-19 1:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 18:46 [Make-wifi-fast] " Dave Taht
2016-01-17 20:32 ` [Make-wifi-fast] [Cerowrt-devel] " Outback Dingo
[not found] ` <CAGOios74tbFyHaKHDYhTatBUX0_Xt+My0UZ3OqaMbTcN6Yy_GA@mail.gmail.com>
2016-01-18 8:30 ` Jonathan Morton
[not found] ` <CAGOios4VMSHV5r8OrFvKn+JJG84YBk7sSg-TL=YPij1mXz+tMg@mail.gmail.com>
2016-01-18 10:51 ` Alan Jenkins
2016-01-18 11:29 ` Jonathan Morton
[not found] ` <CAGOios4JvvHjNkiCRt0f4DPb2em71+pkV2kd8hD-BHk_SE8+nQ@mail.gmail.com>
2016-01-18 23:01 ` Jonathan Morton
[not found] ` <CAGOios6-S=mJfdLkwNS2JCqWx_jNApy3sLsDofXgAfXWLSd-4A@mail.gmail.com>
[not found] ` <CAGOios6EKmbX29zBOcJZG7P3Gd=bGr2XBjWJwoF0Y=Q=WPFK7Q@mail.gmail.com>
2016-01-21 23:40 ` Valent Turkovic
2016-01-22 6:37 ` Jonathan Morton
2016-01-22 7:11 ` moeller0
2016-03-13 11:17 ` Valent Turkovic
2016-01-18 16:14 ` Michael Richardson
2016-01-18 23:06 ` Jonathan Morton
2016-01-19 1:06 ` Michael Richardson [this message]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31692.1453165586@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--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