From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Measuring the Satellite Links of a LEO Network
Date: Mon, 4 Mar 2024 09:39:14 +0100 [thread overview]
Message-ID: <da2a5577-6e32-4b81-8798-802261efcc87@gmail.com> (raw)
In-Reply-To: <ZeRPrFar_YlgfSAc@Space.Net>
Le 03/03/2024 à 11:23, Gert Doering via Starlink a écrit :
> Hi,
>
> On Tue, Feb 13, 2024 at 07:11:16PM +0100, Alexandre Petrescu via Starlink wrote:
>> sorry, it could be that I have it on the wrong side.
>>
>> If VRRP and starlink like to have that IPv6 LL address with ff:fe inside,
>> and always constant, so be it. There might be some reasons for it to be that
>> way.
> It's not unusual to standardize IPv6 gateway addresses to have always
> well-known fe80:: addresses (like, fe80::1).
I am not sure fe80::1 as a default route is standardized in an RFC, so
to say?
I can agree though it is often used in practice.
> There is nothing for an adversary to be gained here. If you are on-link,
> you know, and if you are not, anything fe80:: is of no use to you.
Yes, I agree.
Just that some times one can get on-link because one legitimately has
the credentials, yet one does not know the default route, because it
does not come from an RA but from a link-layer message exchange which
might be difficult (impossible some times) to capture.
I am not saying it is good or bad, just I detail the perspective, for
the sake of discussion.
Alex
>
> Gert Doering
> -- NetMaster
prev parent reply other threads:[~2024-03-04 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 6:59 J Pan
2024-02-12 14:13 ` Alexandre Petrescu
2024-02-13 17:12 ` J Pan
2024-02-13 17:39 ` Alexandre Petrescu
2024-02-13 17:43 ` Alexandre Petrescu
2024-02-13 17:44 ` Alexandre Petrescu
2024-02-13 18:11 ` Alexandre Petrescu
2024-03-03 10:23 ` Gert Doering
2024-03-04 8:39 ` Alexandre Petrescu [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=da2a5577-6e32-4b81-8798-802261efcc87@gmail.com \
--to=alexandre.petrescu@gmail.com \
--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