Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nathan Owens <nathan@nathan.io>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	starlink@lists.bufferbloat.net,
	 Sebastian Moeller <moeller0@gmx.de>,
	 Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] Of interest: Comcast AQM Paper
Date: Wed, 4 Aug 2021 13:18:37 -0700	[thread overview]
Message-ID: <CALjsLJv5VrUheyKP6f4CiJCDWBRBWt_TGbAjU9ft606G0f3y0Q@mail.gmail.com> (raw)
In-Reply-To: <CAHtUBug3wnHAtSNO-eYrHCWrTg5gYNcvCaQRQ5dOz4=2AQn-HA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

Isn't that what CZnic has done with the Turris router?

https://www.turris.com/en/mox/overview/

On Wed, Aug 4, 2021 at 1:08 PM Jonathan Bennett <
jonathanbennett@hackaday.com> wrote:

>
>
>
>>
>>
>> The Compute Module 4 exposes the same integrated Ethernet port, and a
>> PCIe lane in place of the USB 3 chipset (the latter being attached to
>> the former in the standard Pi 4B).  This obviously allows attaching at
>> least one real GigE port (with a free choice of PCIe-based chipset) at
>> full line rate, without the intermediate step of USB.  I think it
>> would be reasonable to include a small Ethernet switch downstream of
>> this, matching the connectivity of typical CPE on the LAN side.  If a
>> PCIe switch is inserted, then a choice of Mini-PCIe Wifi cards can be
>> installed, with cables running to the normal array of external
>> antennae, sidestepping the problem of USB Wifi dongles.
>>
>
> I would hype the heck out of a router-style carrier board.  I'd even buy a
> bunch myself, for that matter. I used to make good money by putting OpenWRT
> on cheap routers for small businesses.
>
> I've had good success chatting with Eben about Hackaday articles. If this
> were to become more than a pipe dream, we could reach out to him, to see if
> the Pi Foundation had any interest in backing a Pi router carrier board
> that beats bufferbloat.
>
> --Jonathan Bennett
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 2403 bytes --]

  reply	other threads:[~2021-08-04 20:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01 20:20 Livingood, Jason
2021-08-01 21:39 ` Dick Roy
2021-08-04 11:49   ` Jonathan Morton
2021-08-04 12:46     ` Mikael Abrahamsson
2021-08-04 13:03       ` Sebastian Moeller
2021-08-04 13:06         ` Mikael Abrahamsson
2021-08-04 13:43           ` Sebastian Moeller
2021-08-04 18:28             ` Jonathan Morton
2021-08-04 20:44               ` David Lang
2021-08-04 20:51               ` Sebastian Moeller
2021-08-04 18:31           ` Juliusz Chroboczek
2021-08-04 18:58             ` Jonathan Morton
2021-08-04 20:08               ` Jonathan Bennett
2021-08-04 20:18                 ` Nathan Owens [this message]
2021-08-04 20:46                   ` Jonathan Bennett
2021-08-05  0:24                     ` Michael Richardson
2021-08-05 15:11                       ` Frank Carmickle
2021-08-07 23:59                         ` Michael Richardson
2021-08-07 20:31   ` Dave Taht
  -- strict thread matches above, loose matches on Subject: below --
2021-08-01 20:21 Livingood, Jason
2021-07-30 21:28 [Starlink] " Livingood, Jason
2021-07-31 17:50 ` [Starlink] [Bloat] " Simon Barber
2021-07-31 19:26   ` Aaron Wood
2021-07-31 22:55     ` Neal Cardwell
2021-08-01 13:13       ` Michael Richardson

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALjsLJv5VrUheyKP6f4CiJCDWBRBWt_TGbAjU9ft606G0f3y0Q@mail.gmail.com \
    --to=nathan@nathan.io \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=jonathanbennett@hackaday.com \
    --cc=moeller0@gmx.de \
    --cc=starlink@lists.bufferbloat.net \
    /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