If you have a Ripe atlas probe version 3, you might be face this error with your probe.
It is happen to me on my probes in many times.
You can easily to solve this error. You just need a bit time and computer.
Few weeks ago, my Amsterdam instance out of space. My all projects is in my workstation (also Github and Gitlab) and I make a sync with mirrorfy to server. I can purge or re install my server without losing (because everything has a backup) any data but I try to truncate log files to gain a bit space in server. I made a huge mistake while emptying log files 😁. Normally I have to write truncate command with
*/* arg while in /var/log folder to truncate files but lack of sleep cause to write a
/*/* and most of the binaries and some important system files is gone 😂.
In my network based or related to network projects, for debugging I execute another shell at same container and I install network tools to these container.
Most of the users use a proxy (like a nginx) front of containers to serve own services to global. In many case this is very basic, useful and cost is not noticeable, but if you serve network services cost is definitely noticeably.
Many years I use my own Gateway device which is Banana Pi.
Banana Pi is not a new device and I wondered what if I get a gigabit connection, this device can handle my bandwidth ? And also I have other questions in mind. “Does the Firewall have a huge effects on interface ? How many bandwidth reduced with bridging interfaces ? “