zlacker

[return to "NASA mistakenly severs communication to Voyager 2"]
1. hutzli+79[view] [source] 2023-07-31 11:41:35
>>belter+(OP)
In short, it was remote bricked, by giving it commands to rotate a bit. After successfully executing those commands - no further commands could be received, as now the antennas are not facing earth anymore.

But luckily it automatically readjust itself to earth automatically every half year exactly for these events. So on 15.10 we will know, if it is really lost. In either case, the end of its mission is near anyway, because the nuclear batteries are near its end.

edit: Nasa has a blog post on this https://blogs.nasa.gov/sunspot/2023/07/28/mission-update-voy...

◧◩
2. dylan6+2H1[view] [source] 2023-07-31 18:50:13
>>hutzli+79
reminds me of the time I forgot i was on a remote connection, and could not figure out why the thing quit responding when i typed eth0 down
◧◩◪
3. renewi+302[view] [source] 2023-07-31 20:28:34
>>dylan6+2H1
Had a node that I was connected to over wireguard. Wanted to reset the wireguard conf.

    sudo wg-quick down wg0
Nice one, mate. Had to drive back to log in and bring up that interface. I still do this, FWIW, but now I use `at` to schedule "up" 1 min in future haha. So far so good though it's not smart :)
◧◩◪◨
4. owenma+YD2[view] [source] 2023-08-01 00:29:23
>>renewi+302
> FWIW, but now I use `at` to schedule "up" 1 min in future

Any time I’m ever doing a pfctl to change my router’s firewall rules I schedule a “revert to the n-1 rule set” job two minutes from now to avoid the trip to the basement & hunt for the serial cable.

I do +2 because once I was too close to the next minute, fat-fingered the update command & instinctively corrected it. But the change had reverted before I hit enter on the new update, so of course I blocked too much traffic and wedged my SSH connection, triggering the cursing and trip to the basement with the serial cable.

[go to top]