TCPIP Network Administration, 3rd Edition (Craig Hunt) (Z-Library)

# TCP/IP Network Administration, 3rd Edition — Reading Guide ## 【One-Line Pitch】 A comprehensive, practical handbook for Unix/Linux system administrators who need to set up, configure, and troubleshoot TCP/IP networks — from protocol fundamentals to advanced routing, DNS, mail, web, and security services. If you run networked Unix systems and want one authoritative reference that covers both concepts and real configuration files, this is your book. --- ## 【Book Arc】 - **Opening (~0%–9%)**: Introduces the TCP/IP protocol suite, the RFC standards process (including the difference between standards-track, experimental, historic, and informational RFCs), and the layered data communications model. Establishes the book's audience — Unix administrators with some experience, not beginners or experts. - **Early (~9%–25%)**: Dives into IP addressing — class-based addressing, subnet masks, CIDR blocks, and route aggregation — explaining why the original class structure failed and how address masks solved the scaling problem. Covers ARP, protocols, ports, and sockets for delivering data to the right process. - **Early (~25%–34%)**: Explains network services: DNS hierarchy and domain registration (including ICANN's role), SMTP/POP/IMAP/MIME for email, and how these services scale beyond simple host tables. - **Middle (~34%–47%)**: Moves into practical configuration — subnetting decisions (topological and organizational reasons), kernel configuration for TCP/IP on Linux and BSD systems, startup files, and the inetd/xinetd internet daemons. Shows how Red Hat's xinetd.d directory structure works. - **Late (~47%–end)**: Covers routing configuration (RIPv2, OSPF, BGP, and gated), DNS configuration (BIND 8/9), network servers (Apache, sendmail, Samba, PPP, DHCP), security tools (OpenSSH, stunnel, gpg, iptables, xinetd access control), and troubleshooting. Appendices serve as command references for gated, pppd, named, dhcpd, and sendmail. --- ## 【Key Takeaways】 - **RFC literacy is a core admin skill** (Early): Knowing which RFCs matter — standards-track vs. informational vs. Best Current Practices — helps you evaluate protocol documentation and operational guidelines. Focus on RFCs with STD numbers as a starting point. - **Class-based addressing was a design failure** (Early): The original A/B/C class structure wasted enormous address space and strained routing tables. CIDR and address masks solved this by decoupling the network/host boundary from byte boundaries, enabling route aggregation. - **DNS is a hierarchical, distributed database** (Early): No server has complete information; root servers only point to top-level domain servers, which point further down. Understanding this delegation model is essential for configuring and troubleshooting name resolution. - **Subnetting solves both technical and organizational problems** (Middle): Beyond overcoming Ethernet distance limits and interconnecting dissimilar networks, subnets let you delegate administration and filter traffic — making them a management tool, not just a technical one. - **Kernel configuration varies dramatically across Unix flavors** (Middle): Solaris configures everything for you, Linux encourages kernel tuning for efficiency, and BSD sits in between with its GENERIC config file approach. Know which model your system uses before touching kernel files. - **xinetd exists primarily for security** (Middle): Red Hat's per-service config files in /etc/xinetd.d and the disable = yes directive give you finer-grained access control than traditional inetd. This is a security feature, not just a configuration convenience. - **MIME extends email beyond ASCII** (Early): SMTP alone can only deliver 7-bit text. MIME's Content-Type and Content-Transfer-Encoding headers enable binary attachments, international character sets, and complex message bodies — essential for modern mail. --- ## 【Reading Tips】 - **Skim the RFC taxonomy section** (~6%–9%) unless you work with protocol standards regularly; the key takeaway is just knowing which RFC categories exist and where to find operational guidance (BCPs like RFC 1918). - **Deep-read the IP addressing chapters** (~9%–25%): CIDR, subnet masks, and route aggregation are the conceptual foundation for everything else. If you understand why class B exhaustion happened, the rest of the book clicks into place. - **Use the configuration chapters as reference, not linear reading** (Middle–Late): The kernel config, inetd/xinetd, and service-specific chapters (DNS, sendmail, Apache) are best consulted when you actually need to configure those systems. Note the Linux vs. BSD vs. Solaris differences for your platform. - **Pay special attention to the xinetd security discussion** (~47%): The access control features covered in Chapter 12 are critical for production systems. Understand how disable = yes and per-service files work before deploying any network service. - **Don't skip the troubleshooting chapter** (Late): The book's practical value peaks here — this is where theory meets real-world failure diagnosis, and the arp command examples show the kind of hands-on debugging you'll actually do. --- ## 【Coverage Limits】 The excerpts cover roughly the first half of the book (through kernel configuration and xinetd). Detailed content on advanced routing protocols (RIPv2, OSPF, BGP), DNS configuration specifics, Apache, sendmail, Samba, PPP, DHCP, security tools, and the troubleshooting chapter is listed in the table of contents but not fully represented in the sampled material. --- ##