From: Mark Seiden <mis@seiden.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] dhcp/network usage logs (unrelated to bufferbloat)
Date: Wed, 5 Jun 2024 17:10:55 +0200 [thread overview]
Message-ID: <73440958-79CA-44E1-9BA1-95C65B8E3E50@seiden.com> (raw)
(sorry if this is too far off-topic, but you are the sort of people who are likely to just know about this, and i can’t get any info out of
spacex, so far.)
i am looking into a possible PII breach (but certainly exceeding authorized access) coming from a couple
starlink ip addresses. the addresses are shown as being in either starlink (denver) or starlink (dallas).
we actually believe these are coming from a place in kansas that might talk via either adjacent state, but i deeply do not
understand how the data flows between the, uh, dish, and customer equipment, and ground stations. (the last ground
station list i can find by web search is 3 years old.)
at the moment we believe this is usage coming from my client’s own starlink equipment, i.e. this is an attack from the inside.
so we asked starlink support for any sort of usage logs for the customer’s own device (particularly ip address assignments)
for specific dates, and they so far refuse to provide such information other than, they say, to law enforcement, who is not yet
involved in the case.
it’s unusual, in my experience, for an ISP to refuse to provide a customer’s own historical usage data to that same customer.
has anyone had a similar experience of asking for their own ip address assignments and usage data and being turned down?
has anyone actually gotten dhcp address assignment logs from spacex and, if so can you send me a few sample lines so i can
look at what they could provide?
does anyone know what other data starlink actually logs? (presumably location, at least).
does anyone know what the retention period is? (we are looking for 6 months of 2024 data).
(btw, my understand is that starlink uses cg-nat, and the logs we have of the abused service do not include port numbers,
just ip addresses, sigh.)
thanks for any helpful info or pointers to Them That Might Know.
—
mark seiden
reply other threads:[~2024-06-05 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=73440958-79CA-44E1-9BA1-95C65B8E3E50@seiden.com \
--to=mis@seiden.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