From: Sebastian Moeller <moeller0@gmx.de>
To: bloat@lists.bufferbloat.net,Matt Taggart <matt@lackof.org>
Subject: Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem
Date: Wed, 25 Mar 2020 07:19:19 +0100 [thread overview]
Message-ID: <09E1A84E-975F-4C00-A722-93AD1577E82E@gmx.de> (raw)
In-Reply-To: <8a861134-f241-6fe4-b313-2f7e5f93e699@lackof.org>
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
So, for higher bandwidth plans people started using raspberry pi4bs with an additional usb3 Ethernet dongle. Its WiFi is not really up for the task but it does seem to make a mean wired only router, the quad A76 cores seem to be capable to reliably shape up to 1 gigabit with cpu cycles to spare.
So maybe get one of those and change your old wifi router into a wifi AP?
Disclaimer, I have not tried that myself, as I am on a 100/40 plan and already have a router well capable of that speed.
Best Regards
Sebastian
On March 25, 2020 6:29:17 AM GMT+01:00, Matt Taggart <matt@lackof.org> wrote:
>On 3/24/20 10:01 PM, Aaron Wood wrote:
>[snip]
>> At the moment, however, my WRT1900AC isn't up to the task of dealing
>> with these sorts of downstream rates.
>>
>> So I'm looking at the apu2, which from this post:
>>
>https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-openvpn/44724
>
>I recently got CenturyLink gig fiber and bought one of these:
>
>Qotom Q355G4
>https://www.amazon.com/gp/product/B077ZWR8Q9
>
>And it's running OpenWRT 19.07 just fine, boots from a small USB
>thumbdrive.
>It has no problem with CAKE + piece_of_cake up to 1gbit
>
>Here is a table I made comparing the Qotom models
>
>https://we.riseup.net/lackof/x86-router-candidates#qotom
>
>(compiled last December, so prices may have changed)
>
>--
>Matt Taggart
>matt@lackof.org
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 2129 bytes --]
next prev parent reply other threads:[~2020-03-25 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 5:01 Aaron Wood
2020-03-25 5:02 ` Aaron Wood
2020-03-25 5:29 ` Matt Taggart
2020-03-25 6:19 ` Sebastian Moeller [this message]
2020-03-25 15:46 ` Aaron Wood
2020-03-25 8:58 ` Toke Høiland-Jørgensen
2020-03-25 9:04 ` Sebastian Moeller
2020-03-25 11:03 ` Toke Høiland-Jørgensen
2020-03-25 15:44 ` Aaron Wood
2020-03-25 15:57 ` Aaron Wood
2020-03-25 19:18 ` Dave Taht
2020-03-28 22:46 ` Aaron Wood
2020-03-29 19:58 ` Dave Taht
2020-03-29 23:52 ` Aaron Wood
2020-03-25 18:13 ` Jim Gettys
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09E1A84E-975F-4C00-A722-93AD1577E82E@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=matt@lackof.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