Network health overview with mtr, ss, lsof and iperf3

We said many times in the past that personal and home network <a href="https://medium.com/codex/privacy-security-principles-and-practice-f1f7f3934ad3" rel="noopener">security</a> is a <a href="https://raduzaharia.medium.com/privacy-and-security-the-habits-f5948aeea30c" rel="noopener">habit</a>. It’s not the operating system you install, it’s not how careful you are when browsing the Internet, it’s not even about the antivirus choice. You can either trust that your network is not compromised, or you can <a href="https://raduzaharia.medium.com/understanding-the-home-network-security-fda87830f133" rel="noopener">build</a> a few habits that keep you sure. The most important habit would be of course the dreaded continuous log scanning. Logs are weird and scanning them is time consuming, if not sometimes impossible, but taking the time to have a good <code><a href="https://raduzaharia.medium.com/how-to-automate-log-scanning-with-fail2ban-a8771460da3f" rel="noopener">fail2ban</a></code> configuration means we take one worry out of the way. Log scanning allows us to create a few rules that automatically react when something goes wrong. But sometimes the malicious activity is not entirely recognized nor understood from the default Linux logs. Sometimes our Internet connection seems weird, and we don’t understand why. We know something is wrong, but we cannot really pinpoint the issue. And other times, there is weird file access that goes undetected simply because we don’t know what to look for. In these instances, we have a few tools that Linux provides which help us understand our environment. Let’s talk about them one at a time. <a href="https://raduzaharia.medium.com/network-health-overview-with-mtr-ss-lsof-and-iperf3-8d0d2d191781">Website</a>