Computer Networking - Complete
Guide
Foundations, routing, switching, security, operations and interview revision
Original educational reference material. Suitable for study, revision and technical
reference.
Computer Networking - Complete Guide Page 1
Table of Contents
1. Networking Foundations
2. OSI and TCP/IP Models
3. Ethernet, Switching and VLANs
4. IPv4 Addressing and Subnetting
5. IPv6
6. Routing Fundamentals
7. OSPF and IS-IS Concepts
8. BGP and Internet Routing
9. MPLS, VRF and VPNs
10. Transport and Application Protocols
11. Network Security
12. Wireless Networking
13. Network Monitoring and Troubleshooting
14. High Availability and Network Design
15. Practical Interview and Revision Guide
16. Subnetting Practice Lab
17. VLAN and Trunk Lab
18. STP Troubleshooting Lab
19. Static Routing Lab
20. OSPF Troubleshooting Lab
21. BGP Policy Lab
22. MPLS and VRF Lab
23. Firewall and NAT Lab
24. DNS and DHCP Lab
25. Packet Capture Lab
26. High Availability Lab
27. Network Monitoring Lab
28. Enterprise Design Case Study
29. Service Provider Design Case Study
30. Interview Question Bank
Computer Networking - Complete Guide Page 2
1. Networking Foundations
What a network does
A computer network connects endpoints so they can exchange information and share services. The important ideas
are addressing, forwarding, naming, transport, security and operations.
Network communication can be viewed as a sequence: an application creates data, transport adds reliability or flow
control when required, the network layer provides logical addressing and routing, the data-link layer provides local
delivery, and the physical layer carries bits.
Concept Purpose
Endpoint Device or software process participating in communication
Link Communication path between interfaces
Protocol Rules governing message format and behavior
Address Identifier used to locate or identify a node/interface
Route Decision describing where traffic should be forwarded
LAN, WAN and Internet concepts
A LAN normally covers a limited administrative or geographic area. A WAN interconnects sites across larger
distances, often through service-provider infrastructure. The Internet is an interconnected collection of autonomous
networks using common protocols and routing policies.
Common topologies include star, partial mesh, full mesh, ring and point-to-point. Modern enterprise networks
commonly use hierarchical designs with access, distribution and core functions, although collapsed-core designs are
also common.
Computer Networking - Complete Guide Page 3
2. OSI and TCP/IP Models
OSI model
The seven OSI layers are Physical, Data Link, Network, Transport, Session, Presentation and Application. The model
is a troubleshooting framework rather than a literal implementation requirement.
Layer-oriented troubleshooting asks: Is the interface physically healthy? Is the local segment working? Is the
destination reachable? Is transport established? Is the application responding?
TCP/IP model
The practical Internet stack is usually described as Link, Internet, Transport and Application. Ethernet and Wi-Fi
operate at the lower layers; IP provides internetworking; TCP and UDP provide transport; DNS, HTTP, SSH, DHCP
and many other protocols live above transport.
Layer Examples
Link Ethernet, Wi-Fi, VLAN, ARP/ND
Internet IPv4, IPv6, ICMP
Transport TCP, UDP, SCTP
Application DNS, HTTP(S), SSH, DHCP, SMTP
Computer Networking - Complete Guide Page 4
3. Ethernet, Switching and VLANs
Ethernet basics
Ethernet uses MAC addresses for local delivery. A switch learns source MAC addresses and builds a forwarding
table. Known unicast traffic is forwarded toward the learned destination port; unknown unicast, broadcast and some
multicast traffic may be flooded according to switch behavior.
Full-duplex switched Ethernet avoids collisions on modern links. Duplex mismatch, errors, CRC faults and
physical-layer problems remain important troubleshooting areas.
VLANs and trunks
A VLAN creates a separate Layer-2 broadcast domain. Access ports normally carry one VLAN for an endpoint.
Trunks carry multiple VLANs using tagging, commonly IEEE 802.1Q.
Native VLAN behavior must be consistent across connected devices. VLAN pruning and allowed-VLAN lists reduce
unnecessary propagation and help limit mistakes.
Spanning Tree
Spanning Tree Protocol prevents Layer-2 loops by placing redundant paths into a controlled state. RSTP improves
convergence. Root bridge selection, root ports, designated ports, edge ports and protection features are central
operational concepts.
Computer Networking - Complete Guide Page 5
4. IPv4 Addressing and Subnetting
IPv4 structure
IPv4 uses 32-bit addresses, normally written as four decimal octets. A prefix length determines how many bits identify
the network. For example, /24 leaves 8 host bits.
Addresses Typical usable hosts*
4 2
8 6
16 14
32 30
256 254
*Traditional host counts exclude network and broadcast addresses; point-to-point and special subnet behavior can
differ.
Subnetting method
To split a network, decide the number of required subnets or hosts, select a prefix, calculate block size, and list
network/broadcast boundaries. In a /24 divided into /26 networks, the block size is 64, producing network starts at .0,
.64, .128 and .192.
VLSM allows different prefix lengths to be used within a larger allocation, reducing address waste.
Computer Networking - Complete Guide Page 6
5. IPv6
Addressing
IPv6 uses 128-bit addresses. Global unicast, link-local, unique local, multicast and special-purpose addresses have
different roles. Link-local addresses are essential for neighbor discovery and many control-plane operations.
IPv6 uses Neighbor Discovery rather than ARP. SLAAC can derive addresses from router advertisements, while
DHCPv6 can provide additional configuration depending on deployment.
Transition concepts
Dual stack operates IPv4 and IPv6 together. Tunneling carries one protocol across another. Translation mechanisms
can help when networks or applications are not fully dual-stack.
Computer Networking - Complete Guide Page 7
6. Routing Fundamentals
How routers forward packets
A router examines the destination IP and selects the most specific matching route. Longest-prefix match is
fundamental. Administrative preference and route metrics determine which route is installed when multiple sources
compete.
Route type Example use
Connected Directly attached subnet
Static Explicit operator-defined path
Default Catch-all route when no specific route exists
Dynamic Learned using a routing protocol
Static routing
Static routes are predictable and simple, but large networks can become difficult to maintain. A floating static route
can provide backup when assigned a worse preference than the primary route.
Computer Networking - Complete Guide Page 8
7. OSPF and IS-IS Concepts
OSPF
OSPF is a link-state interior gateway protocol. Routers form adjacencies, exchange link-state information and
calculate shortest paths. Areas improve scalability. Area 0 is the backbone in conventional OSPF designs.
Important operational checks include neighbor state, interface area, timers, authentication, MTU consistency, router
IDs and route filtering.
IS-IS overview
IS-IS is another link-state IGP widely used by service providers. It separates Level-1 and Level-2 routing domains and
carries routing information using TLVs, making it extensible.
Computer Networking - Complete Guide Page 9
8. BGP and Internet Routing
BGP fundamentals
BGP is a path-vector protocol used between autonomous systems and also extensively inside service-provider
networks. Important attributes include AS_PATH, NEXT_HOP, LOCAL_PREF, MED, ORIGIN and communities.
Route selection is policy-driven. A shorter AS path does not automatically mean the preferred path because local
policy can override it.
iBGP, eBGP and communities
eBGP exchanges routes between autonomous systems; iBGP distributes external routes within an AS. Route
reflectors reduce the need for a full iBGP mesh. Communities attach policy tags to routes and can simplify large-scale
control.
Computer Networking - Complete Guide Page 10
9. MPLS, VRF and VPNs
MPLS basics
MPLS forwards traffic using labels. In a provider network, label distribution and forwarding can be separated from the
customer IP routing view. LDP, RSVP-TE and segment-routing approaches have been used for different transport
requirements.
In Layer-3 VPNs, customer routes are separated using VRFs. MP-BGP can carry VPN routes with route
distinguishers and route targets.
VRF and route targets
A VRF creates an independent routing table on a router. A route distinguisher makes overlapping prefixes unique in
the provider control plane. Route targets control VPN route import and export policy.
Computer Networking - Complete Guide Page 11
10. Transport and Application Protocols
TCP and UDP
TCP provides connection-oriented reliable byte-stream transport using sequencing, acknowledgments,
retransmission and congestion control. UDP is connectionless and has minimal transport overhead.
Protocol Typical use
TCP HTTP(S), SSH, database sessions
UDP DNS, streaming, many real-time applications
SCTP Telecom signaling and multi-stream transport
QUIC Modern encrypted transport over UDP
DNS, DHCP and HTTP
DNS maps names to resource records. DHCP provides dynamic host configuration. HTTP is an application protocol
commonly secured with TLS as HTTPS. Troubleshooting should separate name resolution, reachability, transport
establishment and application behavior.
Computer Networking - Complete Guide Page 12
11. Network Security
Security principles
Use segmentation, least privilege, strong authentication, encryption, logging and controlled administrative access.
Firewalls enforce policy between zones; IDS/IPS can detect or prevent suspicious traffic; VPNs protect traffic across
untrusted paths.
AAA stands for authentication, authorization and accounting. Centralized identity systems improve control over
administrator access.
NAT and ACLs
Network Address Translation changes address information between zones. PAT maps many internal sessions to a
shared public address using ports. ACLs permit or deny traffic according to defined criteria and should be reviewed
for order and shadowing.
Computer Networking - Complete Guide Page 13
12. Wireless Networking
Wi-Fi fundamentals
Wireless LANs use radio channels and access points to connect clients. Channel width, interference, transmit power,
roaming and client density influence performance. 2.4 GHz generally offers longer reach but fewer non-overlapping
channels; 5 GHz and newer bands offer more capacity with different propagation characteristics.
WPA2 and WPA3 provide stronger security than legacy open or obsolete encryption approaches. Enterprise Wi-Fi
commonly integrates 802.1X authentication.
Computer Networking - Complete Guide Page 14
13. Network Monitoring and Troubleshooting
Methodology
A disciplined process is: define the symptom, establish scope, check recent changes, verify physical and logical
layers, isolate the failure domain, collect evidence, change one variable at a time, validate and document.
Useful evidence includes interface counters, ARP/ND tables, MAC tables, routing tables, protocol neighbors, firewall
sessions, DNS responses, packet captures, logs and performance graphs.
Common commands
ping traceroute show route / show ip route show arp / show mac address-table show interfaces nslookup
Packet capture is often the fastest way to distinguish a routing problem from an application or transport problem. Look
at source/destination addresses, ports, flags, retransmissions, TTL, fragmentation and ICMP errors.
Computer Networking - Complete Guide Page 15
14. High Availability and Network Design
Redundancy
Redundancy can be provided at links, devices, power, routing paths and sites. First-hop redundancy protocols allow
multiple gateways to present a resilient virtual gateway to endpoints.
A design should avoid single points of failure and should define convergence expectations, failure domains and
maintenance procedures.
Capacity planning
Plan for peak traffic, growth, control-plane scale, interface utilization, memory, CPU, session counts and failure
scenarios. Headroom is part of reliability, not wasted capacity.
Computer Networking - Complete Guide Page 16
15. Practical Interview and Revision Guide
Rapid questions
Know the difference between switching and routing, TCP and UDP, static and dynamic routing, OSPF and BGP,
access and trunk ports, NAT and firewalling, VRF and VLAN, MTU and MSS, latency and throughput.
For troubleshooting questions, answer in a sequence rather than listing random commands: physical -> interface ->
VLAN -> IP -> route -> transport -> application.
Mini design exercise
Design a two-site enterprise network with redundant WAN links, separate user/server/management VLANs, dynamic
routing, centralized authentication, firewall zones, monitoring and backup connectivity. Document addressing, routing
policy, failure behavior and operational checks.
Computer Networking - Complete Guide Page 17
16. Subnetting Practice Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Subnetting Practice Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 18
17. VLAN and Trunk Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for VLAN and Trunk Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 19
18. STP Troubleshooting Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for STP Troubleshooting Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 20
19. Static Routing Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Static Routing Lab. Start with a written topology,
addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 21
20. OSPF Troubleshooting Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for OSPF Troubleshooting Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 22
21. BGP Policy Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for BGP Policy Lab. Start with a written topology,
addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 23
22. MPLS and VRF Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for MPLS and VRF Lab. Start with a written topology,
addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 24
23. Firewall and NAT Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Firewall and NAT Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 25
24. DNS and DHCP Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for DNS and DHCP Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 26
25. Packet Capture Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Packet Capture Lab. Start with a written topology,
addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 27
26. High Availability Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for High Availability Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 28
27. Network Monitoring Lab
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Network Monitoring Lab. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 29
28. Enterprise Design Case Study
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Enterprise Design Case Study. Start with a
written topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 30
29. Service Provider Design Case Study
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Service Provider Design Case Study. Start with a
written topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 31
30. Interview Question Bank
Practical exercise
Objective: build and troubleshoot a realistic networking scenario for Interview Question Bank. Start with a written
topology, addressing plan and expected traffic path. Validate each assumption with observable evidence.
Procedure: verify interfaces first, then local Layer-2 state, IP addressing, routing, transport and application behavior.
Record commands, outputs and conclusions in a lab notebook.
Success criteria: the intended traffic path works, failure behavior is understood, and the configuration can be
explained without relying on trial-and-error.
Checklist
Check Expected result
Physical/link Interface up and counters healthy
Layer 2 Correct VLAN/MAC/neighbor state
Layer 3 Correct address and route
Policy ACL/firewall permits intended traffic
Transport Session establishes correctly
Application Service responds as expected
Computer Networking - Complete Guide Page 32