I have a failsafe service for one of my servers, it pings the router and if it hasn’t reached it once for an entire hour then it will reboot the server.
This won’t save me from all mistakes but it will prevent firewall, link state, routing and a few other issues when I’m not present.
I didn’t consider it as valid, one on (phone and internal nvme1), the second one on nvme2 and the third one in the cloud.
Though I have only two copies of normal data myself, I consider live and cloud to be enough for most data. Everything very important has more backups in other ways (bitwarden has an exportable local version on every logged in device, images are stored in immich on my server making it 3 devices)
You have 3 copies, one on your phone and nvme, one on the backup nvme and one in the cloud. You have 2 media, internal SSD and cloud (your phone would count as a third if it wasn’t auto synced) You have 1 off-site in the cloud
Find a new service you like, add it using rootless podman. That way you can test it without affecting your running system.
The buff/cache will free automatically when an application needs ram, until then it’s useful for speeding up the system.
Try sysctl -w net.ipv4.conf.all.rp_filter=2 on the PC (not vps) or =0 if that doesn’t work
Do a ping of 8.8.8.8 from your user, then open a new console and run tcpdump -i <interface> with first your uplink, then wg0. The packets should be seen on wg0 if they’re routed correctly and the problem then is on the vps side. Otherwise it’s a problem on your local config.
Did you add the vps IP to the routing table of your user? ip r add 10.0.0.2/32 dev wg0 table 1070?
Layer 8, next question.
To shreds you say?
Our Database
So, when is the first party cable going to be launched? The device only hast an adapter shipped with it, which won’t help you connect to the PSU 12VHPWR.
And it burns, burns, burns
The gpu of fire
The gpu of fire
Just after it’s too late
Larme
You must be at Least this high to work here.
Tap for spoiler
What even are they snorting?