From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: David Lang <david@lang.hm>, cake@lists.bufferbloat.net
Subject: Re: [Cake] bringing up a new router/connection
Date: Wed, 3 Feb 2021 16:15:53 -0800 (PST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2102031612380.10981@qynat-yncgbc> (raw)
In-Reply-To: <91BCCD0A-BE88-49A8-AEE0-960A1B363A9D@gmail.com>
On Thu, 4 Feb 2021, Jonathan Morton wrote:
>> On 3 Feb, 2021, at 11:24 pm, David Lang <david@lang.hm> wrote:
>>
>> when plugged directly into the ISP router, I am getting the advertised speeds, when going through the c2600 I top out at 200-300Mb download and 10-15mb upload
>
> That sounds about right for a consumer CPE router. I believe there is usually a hardware bottleneck between the SoC and the Ethernet complex that is significantly narrower than the Ethernet ports and switch fabric. Once the downstream gets saturated there is also no room for upstream traffic.
note this is still without cake, and neither core seems to be saturated yet.
I do have a Turris Omni that I plan to move this to, but I was expecting this
one to give me reasonable speeds on just a raw connection.
I will need a device with at least 3 ethernet ports (DSL, cablmodem, LAN)
David Lang
> You could set it up for 100Mbit down, 25Mbit up using Cake, and see how that works. It'll be a major improvement over 8/1 DSL, even if it isn't using the full advertised capacity of the cable.
>
> One device that should be able to keep up is a Raspberry Pi 4 (not the earlier versions) supplemented with a USB3-attached GigE dongle. Pete Heist has established that it can sustain 600Mbit through Cake without much CPU load or added latency. Above that level the characteristics do degrade a bit.
>
> - Jonathan Morton
>
>
next prev parent reply other threads:[~2021-02-04 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 21:24 David Lang
2021-02-04 0:03 ` Jonathan Morton
2021-02-04 0:15 ` David Lang [this message]
2021-02-04 5:51 ` Pete Heist
2021-02-04 1:11 ` xnor
2021-02-04 5:24 ` David Lang
2021-02-04 4:53 ` Y
2021-02-04 5:14 ` David Lang
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2102031612380.10981@qynat-yncgbc \
--to=david@lang.hm \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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