Linux Networking Linux Networking Explained: Interfaces, IP Addresses, Routes, and the Default Gateway A Linux server can have several network interfaces
An IP address identifies a network destination, but a server usually runs many networked applications at the same time. A web server, SSH service, database
Run uptime or top on a Linux server and you will see three numbers called load average. They might look like 0.42, 0.68, 1.15. At first glance, they look
Run free -h on a busy Linux server and you may see something alarming: most of the RAM appears to be used, while the free column is surprisingly small.
A Linux server is rarely doing just one thing. A web server may be accepting requests, a database may be writing data, scheduled jobs may be running, and
You run uptime and see three numbers: load average: 0.42, 0.58, 0.61 Are they percentages? CPU usage? The number of running processes? And at what point
A Linux server can report very little free memory and still be perfectly healthy. That sounds contradictory, especially if you are used to treating unused
A server reports “No space left on device,” but which filesystem is full, and what is using it? Two Linux commands answer different parts of that question
You remember saving a configuration file, but not its directory. Or you need to identify which files changed during a deployment. The Linux find command
Linux does not let every user read, change, or run every file. Instead, each file and directory has an owner, a group, and a set of permissions that determine









