zlacker

[parent] [thread] 3 comments
1. renewi+(OP)[view] [source] 2023-07-31 20:28:34
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 :)
replies(3): >>dylan6+07 >>dekhn+xC >>owenma+VD
2. dylan6+07[view] [source] 2023-07-31 21:00:27
>>renewi+(OP)
Luckily for me, I just had to go down the hall to the data center, and then reset it with the local terminal. Compared to you, I learned the lesson on the cheap, but you got the bonus of a nice get out of jail free card. Neat CYA trick that I will keep in mind.
3. dekhn+xC[view] [source] 2023-08-01 00:17:50
>>renewi+(OP)
There's a feature in many business data centers called "remote hands". Mainly to avoid the drive/flight to admin a remote machine.
4. owenma+VD[view] [source] 2023-08-01 00:29:23
>>renewi+(OP)
> 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]