Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: Jared Mauch <jared@puck.nether.net>
Cc: Nathan Owens <nathan@nathan.io>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dishy's ethernet chips?
Date: Sun, 6 Jun 2021 02:17:14 -0700	[thread overview]
Message-ID: <FF1C6526-2262-4C50-8680-498365B1C79C@teklibre.net> (raw)
In-Reply-To: <C61FAD06-40D7-463C-9F2B-761929FD082D@puck.nether.net>

Source: MS-NLB-PhysServer-02_03 (02:02:00:00:00:03)
    Address: MS-NLB-PhysServer-02_03 (02:02:00:00:00:03)
    .... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
    .... ...0 .... .... .... .... = IG bit: Individual address (unicast)



> On Jun 5, 2021, at 6:35 PM, Jared Mauch <jared@puck.nether.net> wrote:
> 
> 
> 
>> On Jun 5, 2021, at 6:00 PM, Dave Taht <davet@teklibre.net> wrote:
>> 
>> normally they would have just copy/pasted some ethernet IP from some other chipset in their line….
>> 
>> I am curious which ethernet device driver that might be.
> 
> I haven’t powered mine on yet, can you tell from the Mac address of the chipset, or is the OUI assigned to Starlink/SpaceX?
> 
> - jared
> 
>> 
>> I’m not very knowledgable about st’s other chips
> 


  reply	other threads:[~2021-06-06  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05  2:05 Dave Taht
2021-06-05 21:16 ` Nathan Owens
2021-06-05 22:00   ` Dave Taht
2021-06-06  1:35     ` Jared Mauch
2021-06-06  9:17       ` Dave Taht [this message]
2021-06-06 16:10         ` Nick Buraglio

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=FF1C6526-2262-4C50-8680-498365B1C79C@teklibre.net \
    --to=davet@teklibre.net \
    --cc=jared@puck.nether.net \
    --cc=nathan@nathan.io \
    --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