From: Nick Buraglio <buraglio@forwardingplane.net>
To: Dave Taht <davet@teklibre.net>
Cc: Jared Mauch <jared@puck.nether.net>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dishy's ethernet chips?
Date: Sun, 6 Jun 2021 11:10:20 -0500 [thread overview]
Message-ID: <CAGB08_dVtTrQOLOUPKqjQu_-tQACEkcDtNX3a-b70H4ULO4Scw@mail.gmail.com> (raw)
In-Reply-To: <FF1C6526-2262-4C50-8680-498365B1C79C@teklibre.net>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Can confirm, mine is also 02:02:
nb
On Sun, Jun 6, 2021 at 4:17 AM Dave Taht <davet@teklibre.net> wrote:
> 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
> >
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1976 bytes --]
prev parent reply other threads:[~2021-06-06 16:10 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
2021-06-06 16:10 ` Nick Buraglio [this message]
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=CAGB08_dVtTrQOLOUPKqjQu_-tQACEkcDtNX3a-b70H4ULO4Scw@mail.gmail.com \
--to=buraglio@forwardingplane.net \
--cc=davet@teklibre.net \
--cc=jared@puck.nether.net \
--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