Day 17 - Debian Package Management and Network Tools on Day 17
A Deep Dive into dpkg, apt, and Key Networking Tools

Todayโs DevOps journey focused on managing packages and performing network diagnostics on a Debian-based system. I worked with .deb packages using dpkg, handled dependency-aware installs with apt, managed users, and explored essential networking tools like dig, ss, and telnet.
๐งโ๐ป User Management & sudo Access
useradd devops
su - devops
userdel -r devops
adduser devops
id devops
๐ Grant sudo access:
export EDITOR=vim
visudo
๐ฆ Installing .deb Packages with dpkg
wget http://archive.ubuntu.com/ubuntu/pool/universe/t/tree/tree_1.7.0-3_amd64.deb
dpkg -i tree_1.7.0-3_amd64.deb
tree
Check or remove:
dpkg -l | grep tree
dpkg -r tree
๐ฅ Using apt Properly
apt update
apt search tree
apt install tree
Install, remove & purge Apache:
๐ Network Troubleshooting Tools
๐ traceroute or mtr
Trace the path packets take to a host:
traceroute google.com
mtr google.com
๐ง dig
DNS lookup tool:
dig google.com
Returns A records and DNS resolution path.
๐งช telnet
Test open ports:
telnet <IP> <PORT>
e.g. telnet 192.168.1.10 22 โ useful for checking SSH access.
๐ netstat (legacy) vs ss (modern)
netstat -antp | grep LISTEN
ss -tunlp
Shows listening ports, associated services, and open sockets.
๐ฃ๏ธ route -n
Display network gateways:
route -n
๐ก What I Learned
โ dpkg is for local .deb files, apt handles dependencies
โ adduser vs useradd โ interactive vs raw
โ ss is a modern replacement for netstat
โ dig, telnet, mtr = must-have tools for debugging connectivity
๐ Real-World Use Cases Test if Jenkins or Apache is reachable
Diagnose DNS misconfigurations
Confirm firewall rules with telnet or ss
๐ฎ Next Steps
On Day 18, I plan to dive into cron jobs and automating system tasks like log backups or service checks.




