@futurebird Assuming they have some sort of gateway and IP connectivity, how would you tell?
NASA wouldn't tell us the address range for Artemis or the ISS. And in all likelyhood if it was some sort of IPv4 or IPv6 connectivity, it would be on a non-routable 10/8 network. So in your e-mail headers or your Apache log, all you'd see is regular IPv4 or IPv6 addresses. Best you could do is say "this IP address belongs to NASA or the U.S. government."
The only way to tell would be if they had a footer in their e-mail to indicate they had types or dictated it from space.
@trinsec @futurebird @funnymonkey Sorry to rain n your parade, but if it's in some NASA IP range, then geolocation would report back whever that range is recorded.
I know because when after logging onto my federal agency center's VPN, if I use Google to search for something, I get a lot of suggestions in the Maryland burbs outside DC. And I'm four states away from there via Amtrak.
Yeah, I knew this before making the joke.
Its kinda the entire point.
I could tell by whether or not they were trying to sell me some 💩.
Like say, for instance, Trump merch.
Oh come on don't disturb my remove Lindsey Graham from tRump's ass party please.
It's not a minor operation but hey Oompa Loompa might not survive it.
Hopium for everyone!
@Vive_Levant @sng @ai6yr @futurebird those are two of my favourite RFCs! 😜
in seriousness though, #NASA has done a lot of work on delay-tolerant networking and there are several related RFCs including RFCs 4838 & 5050
https://www.rfc-editor.org/rfc/rfc4838
https://www.rfc-editor.org/rfc/rfc5050
#DTN
^ what??!? it’s totally normal to have favourite RFCs, shut up! 🤪
@itgrrl @sng @ai6yr @futurebird I’m sure you know, but is the rest of the fediverse aware that rfc 1149 was implemented in 2001 and a desastrously inefficient ping was successfully executed by a Norwegian LUG in Bergen ?
Desastrously inefficient success :
9 packets transmitted, 4 packets received, 55% packet loss
round-trip min/avg/max = 3211900.8/5222806.6/6388671.9 ms
@sng @ai6yr @futurebird LEO? no, it's fine
The moon? 1.3s, which isn't insurmountable but sure is annoying
@astraluma @sng @ai6yr @futurebird so long as you manage to sort out the “500-mile email” problem… 🙃
@itgrrl @astraluma @sng @futurebird Ha!
Funny story, I was attempting to figure out how to do some configuration of various Internet utilities over AREDN (ham radio mesh), and -- due to mesh and RF involved -- it pushes up against a lot of these same timeout errors. It was extremely annoying... i.e. you knew there was a node you could theoretically get to, but there was no MODERN protocol able to communicate because of those latency timeouts. I was looking to see if anyone still supported UUCP to get around the problem!! (but then got distracted, and never figured it out).
@futurebird If it was from Major Tom, your reply would bounce.
(Sorry, not helpful)
@futurebird Astronauts would be using the Near Space Network. AFAICT, it's basically a private Internet with its own routing, and AFAICT a bridge to the public Internet.
The Network uses NASA ASN 297 blocks and the DSN block 192.243.16.0/22
So... it would probably be from there, being in that range doesn't guarantee the signal came from space.
@futurebird I had to go look it up. Couldn't leave it alone.
They have something called O2O. Laser communication via infrared. Gives them 620 Mbps, which is faster than what many of us have at home, though their latency must be quite high, and presumably very steady. Forget trying to play Fortnite.
And while they have wifi onboard for their devices, they have no direct link to the internet. They cannot browse the web or scroll tik toks. Which is not surprising if you want to maintain some sort of protection, you wouldn't open it up to the internet.
I'm curious to know how many physical stations and dishes on earth are needed to maintain steady communications via O2O. Some details here: https://www.nasa.gov/goddard/esc/o2o/
@futurebird their emails are generally batched up & sent via #NASA mail servers, and any web browsing opportunities will go through NASA proxies, so it could be tricky
it’s not that hard to generate a complete list of NASA mail servers & map those to back IP addresses in email headers, but that would likely only give you confidence that “someone at #JPL” emailed you – and if they used their NASA email address then it’s much easier to map the IPs from their email headers (back to a specific NASA mail server but it might not be specific enough to give you confidence that they were in space when they sent it 🙃)
the same technique can probably get you a reasonable subset of NASA proxy servers, but it might be difficult to map those proxies back to specific NASA orgs or business units - you’re unlikely to get any IPs in your web server logs that resolve back to (e.g.) integrity.orion.artemis.proxy.jpl.nasa[.]gov… 😜