Skip to content
DevOps AI ToolKit
Newsletter
Learning path · 15 lessons · Beginner → Intermediate

Kali Linux Networking for DevOps

Master Linux networking, DNS, routing, TCP/IP, ports, packet capture, firewalls, and service troubleshooting using Kali Linux.

Learn how traffic actually moves through Linux, Docker, cloud, and modern infrastructure — and how to find where it breaks.

Start Learning → View Curriculum

New to Kali? Start with Kali Linux for DevOps Engineers: Getting Started.

Why networking matters in DevOps

The skills behind most outages

  • DNS

    Most "the app is down" incidents are really name-resolution failures.

  • Routing

    Understand why a VM, container, or node picks one network path over another.

  • TCP/IP

    Read handshakes, resets, and timeouts to separate network from application faults.

  • Ports

    Know exactly what is listening, on which address, and who can reach it.

  • Firewalls

    Trace a blocked connection through cloud, host, and container layers.

  • Packet Capture

    Prove what the network actually did — not what the app claims happened.

What you will learn

From interfaces to packet capture

  • Interfaces
  • IP Addresses
  • CIDR
  • Routing
  • ARP
  • TCP/UDP
  • Ports
  • DNS
  • Nmap
  • Traceroute
  • tcpdump
  • Wireshark
  • Firewalls
  • TLS
The mental model

Networking as a troubleshooting stack

Learn to identify which layer is broken before trying to fix it.

   Application   ← HTTP, SSH, the app itself
       ↓
      TLS         ← certificates, handshake
       ↓
      Port        ← is anything listening?
       ↓
      DNS         ← does the name resolve?
       ↓
    Gateway       ← is the next hop reachable?
       ↓
     Route        ← which path does the kernel pick?
       ↓
   Interface      ← is the NIC up, with an IP?
Course curriculum

The 15-lesson path

Decision guide

Which tool should I use?

Hostname doesn't resolve?  →  dig
Can't reach the server?    →  ip route / ping
Port won't connect?        →  nc / nmap
HTTP failing?              →  curl -v
TLS failing?               →  openssl s_client
Still unclear?             →  tcpdump
Methodology

The DevOps network troubleshooting workflow

Start at the lowest layer you can verify and work upward — don't restart the app before you know packets even reach the host.

  1. 1Define the expected behavior
  2. 2Check the local interface (ip addr)
  3. 3Check the IP address
  4. 4Check the route (ip route get)
  5. 5Check gateway reachability (ping / ip neigh)
  6. 6Check DNS (dig)
  7. 7Test the TCP/UDP port (nc / ss)
  8. 8Check TLS if applicable (openssl)
  9. 9Check the application (curl -v)
  10. 10Capture packets if still unclear (tcpdump)
Quick reference

Network command cheat sheet

Common DevOps networking goals mapped to Linux commands
GoalCommand
Show interfacesip addr
Show routesip route
Show neighbor (ARP) tableip neigh
Which route to a targetip route get 8.8.8.8
Show listening portsss -lntup
Test DNSdig +short example.com
Reverse DNSdig -x 192.0.2.10
Test a TCP portnc -vz host 443
Test HTTP end to endcurl -v https://host
Inspect a TLS certificateopenssl s_client -connect host:443
Trace the pathtraceroute host
Discover lab portsnmap -p 22,80,443 192.168.56.10
Capture packetstcpdump -i eth0 port 443
Tools you will use

The Kali networking toolkit

  • ip
  • ss
  • dig
  • curl
  • nc
  • traceroute
  • mtr
  • nmap
  • tcpdump
  • Wireshark
  • openssl
Recommended before starting

Where this fits in the curriculum

  • ✓ Basic Linux and command-line familiarity (no strong networking knowledge assumed)
  • ✓ Kali Linux: Getting Started — recommended if you're new to Kali
  • ✓ Kali Linux on Docker — optional, useful to run the labs in containers
  • ✓ A local Kali VM or container to run the exercises safely
Additional Kali Linux resources

Recommended Reading

Optional references. The tutorials are the primary learning path.

Recommended Kali Linux Books

Affiliate Disclosure: Some links on this page are affiliate links. If you purchase through one of these links, DevOps AI Toolkit may earn a commission at no additional cost to you. See our affiliate disclosure.

FAQ

Kali Linux networking — common questions

Is networking important for DevOps?

Critically. A large share of production incidents — failed deploys, unreachable services, intermittent latency — are network problems: DNS, routing, firewalls, or a service bound to the wrong address. Being able to isolate the failing layer is one of the highest-leverage DevOps skills.

Why use Kali Linux for network troubleshooting?

Kali ships the full networking toolkit — dig, ss, nmap, tcpdump, traceroute, mtr, openssl, Wireshark — already installed and current. You can run it as a disposable VM or container and have every diagnostic ready without polluting a production host.

What networking commands should a DevOps engineer know?

Start with ip addr, ip route, ip neigh, ss -lntup, dig, nc -vz, curl -v, traceroute, and tcpdump. This course teaches each one in the order you would actually reach for it while troubleshooting.

What is the difference between ping and Nmap?

ping tests basic reachability at the IP layer (ICMP) — it tells you a host answers, not that any service works. Nmap probes specific TCP/UDP ports to tell you which services are actually listening and reachable. A host can answer ping while the port you need is closed or filtered.

What is the difference between tcpdump and Wireshark?

Both analyze packets. tcpdump is a lightweight command-line capture tool ideal on servers with no GUI — you capture to a .pcap file. Wireshark is a graphical analyzer for reading that capture: following TCP streams, applying display filters, and inspecting DNS, HTTP, and TLS. A common workflow is capture with tcpdump, analyze in Wireshark.

How do I troubleshoot DNS on Linux?

Use dig to query records directly (dig +short name, dig name A, dig -x ip for reverse, dig +trace to follow the delegation). Check which resolver you are actually using with resolvectl. The course covers wrong records, stale caches, split DNS, search domains, and container DNS.

How do I check which ports are listening?

Use ss -lntup to list listening TCP and UDP sockets with their local address and owning process. Pay attention to the bind address: 127.0.0.1 is local-only, while 0.0.0.0 accepts connections from any interface — a frequent cause of "works locally, not remotely".

How do I determine which route Linux will use?

Run ip route get <destination>. It shows the exact interface, gateway, and source IP the kernel would use, applying longest-prefix matching across the routing table — far more precise than reading ip route by eye.

Can I use Kali Linux for Docker network troubleshooting?

Yes. The same tools work inside containers and against Docker bridge networks, and the companion Kali Linux on Docker series builds a containerized lab. This course links networking concepts — bridges, veth pairs, embedded DNS, port publishing, NAT — back to Docker.

Can these skills be applied to Kubernetes?

Directly. Pod IPs, Services, DNS, and NetworkPolicies are the same primitives — DNS, routing, ports, and firewalls — applied at cluster scale. You will apply these same fundamentals in the upcoming Kali Linux + Kubernetes learning path.

Learn How Networks Actually Work

Start with interfaces and IP addresses, then progress through routing, DNS, TCP, ports, packet analysis, and real-world DevOps troubleshooting.

Start Part 1: Networking Fundamentals →