Week 8: Network Services, Ports, Wi-Fi, and Configuration

Last week we proved a local path:

endpoint
→ local link
→ valid IP configuration
→ gateway
→ remote IP path

Good.

That still does not guarantee the user can do anything useful.

A laptop can have strong Wi-Fi, a valid IP address, and a reachable gateway while a website still fails because DNS is broken. A printer can be reachable while the print service is misconfigured. Two departments can share the same physical switch while VLANs and policy keep them logically separated. A remote worker can have normal internet access while the organization VPN is unavailable.

The network is working at one layer and failing at another.

This week moves into that service layer.

The system question

Which network responsibility is actually failing when signal, addressing, routing, naming, transport, and applications can all succeed or fail independently?

Keep this stack in mind:

radio / cable
    ↓
local link
    ↓
IP configuration
    ↓
gateway / routing
    ↓
name resolution
    ↓
transport endpoint
    ↓
application service

A failure near the bottom can break everything above it. A failure near the top can leave the lower layers completely healthy.

That is why ping succeeding does not prove a web application works, and why strong Wi-Fi bars do not prove DNS, DHCP, routing, or the internet works.

How the chapter moves

Lesson 1 separates DHCP, DNS, NAT, VLANs, and VPNs by the problem each mechanism solves.

Lesson 2 connects TCP and UDP behavior to the complete A+ port set without pretending a familiar port number proves the application behind it is healthy.

Lesson 3 treats Wi-Fi as radio plus an upstream path, then compares 2.4, 5, and 6 GHz, channel selection, Wi-Fi generations, Bluetooth, NFC, and RFID.

Lesson 4 builds the service layer: DNS, DHCP, file, print, mail, syslog, web, AAA, database, NTP, proxy, UTM, load balancer, spam gateway, VPN, IoT, and SCADA recognition.

Lesson 5 diagnoses service and Wi-Fi failures by identifying the first failed responsibility rather than restarting everything.

This week is about learning which claim each piece of network evidence actually supports.