Networking Fundamentals
What the exam tests
Networking Fundamentals covers IP addressing, persistent configuration, troubleshooting, and client-side DNS. Expect command output interpretation and configuration-file locations.
Core rules
- IPv4 private ranges are
10.0.0.0/8,172.16.0.0/12, and192.168.0.0/16; loopback is127.0.0.0/8; link-local is169.254.0.0/16. IPv6 loopback is::1, link-local isfe80::/10, global unicast is2000::/3, and multicast isff00::/8. CIDR/24gives 256 addresses, 254 usable. - Ports and protocols: TCP 22 SSH, 25 SMTP, 53 DNS, 80 HTTP, 123 NTP, and 443 HTTPS;
/etc/servicesmaps names to ports. ICMP supportsping; UDP is connectionless. - Persistent config: NetworkManager uses
nmcli con modand stores profiles in/etc/NetworkManager/system-connections/;nmtuiis the text UI. systemd-networkd uses.networkfiles. Debian ifupdown uses/etc/network/interfaces. - Troubleshooting:
ip addr,ip route,ss -tulpn,ping,traceroute,dig,host,getent hosts, andresolvectl. Check link, address, route, then name resolution. - DNS client:
/etc/resolv.conflistsnameserverandsearch;/etc/hostsprovides static entries;/etc/nsswitch.confcontrols order, commonlyhosts: files dns.
Worked example
A host can ping 192.0.2.10 but not db.lab. ip route shows a default route, and ping 192.0.2.10 succeeds, so L3 connectivity is fine. cat /etc/resolv.conf shows no nameserver. Add nameserver 192.0.2.53, then test with getent hosts db.lab and dig db.lab. Reasoning: getent uses NSS and reflects application behavior; dig queries DNS directly. If getent fails while dig succeeds, inspect /etc/nsswitch.conf and /etc/hosts.
Traps
Editing /etc/resolv.conf directly may be overwritten by NetworkManager or resolvconf; change the connection profile. ping uses ICMP and may be blocked while TCP works. A route to a host does not guarantee DNS. ss -l shows listening sockets; ss -t shows TCP sockets. Do not confuse the default gateway with a DNS server. IPv6 link-local addresses need a zone ID such as %eth0.