From: Fearghas Mckay <fearghas@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Cc: Dave Taht <dave.taht@gmail.com>,
Starlink <Starlink@lists.bufferbloat.net>
Subject: Re: [NNagain] starlink IXP peering progress
Date: Tue, 27 Feb 2024 00:02:45 -0800 [thread overview]
Message-ID: <CAAS9mxM6Yurq+-G04etfJ2Wk6rny5pyyoBjkRrQ1yr-V7fic_w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6Tc26-6Gz7ukp16yxb3z92VzO9KEj6gGFjNjSCRzErmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
On 27 Feb 2024 at 14:51:29, Dave Taht via Nnagain <
nnagain@lists.bufferbloat.net> wrote:
> One of the things I learned today was that starlink has published an
> extensive guide as to how existing BGP AS holders can peer with them
> to get better service. I am curious if there is a way to see how many
> have peered already, how many they could actually peer with?, and
> progress over time since inception.... is there a tool for that?
>
> https://starlink-enterprise-guide.readme.io/docs/peering-with-starlink
This is just standard BGP peering over route servers. It is not BGP over
your starlink satellite service, you need to have connectivity to an
appropriate IXP.
It tells you to use Peering dB to find the appropriate locations -
https://www.peeringdb.com/net/18747
So if you connect to one of the IXPs linked on that page you can peer with
Starlink, just like another BGP network that does public peering over
routes.
The IXPs may have local data on who has been peering over the route
servers.
f
[-- Attachment #2: Type: text/html, Size: 1790 bytes --]
next prev parent reply other threads:[~2024-02-27 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 20:31 [NNagain] A Multifaceted Look at Starlink Performance the keyboard of geoff goodfellow
2024-02-27 7:51 ` [NNagain] starlink IXP peering progress Dave Taht
2024-02-27 8:02 ` Fearghas Mckay [this message]
2024-02-27 18:43 ` [NNagain] A Multifaceted Look at Starlink Performance rjmcmahon
[not found] <CAA93jw5C-enhS1G4MZZ-js9RG5VQLmjEHg_r6uouQemuD8rP-A@mail.gmail.com>
2024-02-27 21:50 ` [NNagain] starlink ixp peering progress Bill Woodcock
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAS9mxM6Yurq+-G04etfJ2Wk6rny5pyyoBjkRrQ1yr-V7fic_w@mail.gmail.com \
--to=fearghas@gmail.com \
--cc=Starlink@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nnagain@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