Network+ Complete
Course Module
Everything you need to know about networking concepts for the CompTIA Network+ exam. OSI model, protocols, topologies, IPv4, cloud, and more — all in one place.
The OSI Model
The Open Systems Interconnection (OSI) model is a conceptual framework that standardizes network communication into seven distinct layers. Each layer has a specific role and communicates with the layers above and below it. Think of it as a recipe — each step depends on the one before it.
Bottom-up: "Please Do Not Throw Sausage Pizza Away" (Physical → Application)
Layer Deep Dives
Layer 1 — Physical
Deals with raw bit transmission over a physical medium. Defines electrical, optical, and radio specifications. Devices: hubs, repeaters, cables. When there's a "bad cable," that's a Layer 1 problem.
Layer 2 — Data Link
Provides node-to-node transfer and error detection using MAC addresses. Split into two sublayers: LLC (Logical Link Control) for flow control, and MAC (Media Access Control) for addressing. Devices: switches, bridges.
Layer 3 — Network
Handles logical addressing and routing. IP addresses live here. Routers inspect Layer 3 headers to make forwarding decisions. Protocols: IP, ICMP (ping), OSPF, BGP. This is where subnetting lives.
Layer 4 — Transport
TCP provides reliable, ordered, error-checked delivery (3-way handshake: SYN, SYN-ACK, ACK). UDP is connectionless and fast — no guarantees. Port numbers live at Layer 4 to multiplex services.
Layer 5 — Session
Manages sessions between applications — opening, maintaining, and terminating conversations. Enables full-duplex vs half-duplex modes. Examples: NetBIOS for Windows networking, SIP for VoIP, RPC.
Layer 6 — Presentation
Translates, encrypts, and compresses data. Converts from application format to network format and back. TLS/SSL encryption happens here. File formats like JPEG, MP4, and character encoding like ASCII.
Encapsulation / Decapsulation
Data travels down the OSI stack on the sending side (encapsulation) and up the stack on the receiving side (decapsulation). Each layer wraps data with its own header (and sometimes trailer).
FCS = Frame Check Sequence (CRC error detection at Layer 2)
Networking Appliances
Physical or virtual devices that perform specific network functions. Knowing which OSI layer each device operates at is crucial — it determines what they can "see" and what decisions they can make.
Network Topologies
A network topology defines how devices are physically and logically connected. Physical topology is the actual cable/hardware layout. Logical topology is how data flows through the network, which may differ from physical.
⭐ Star / Hub-and-Spoke
All devices connect to a central hub/switch. Single point of failure at the center, but individual node failures don't affect others. Most common LAN topology today.
🕸 Full Mesh
Every device connects directly to every other device. Highly redundant — no SPOF. Used in WANs and critical backbone networks. Formula: n(n-1)/2 connections needed.
⭕ Ring (Logical)
Data travels in one direction around a ring. Token Ring uses a token-passing system — only device holding the token can transmit. Single break can break the whole ring. Largely historical (Token Ring, FDDI).
🍃 Spine and Leaf
Modern data center topology. Every leaf switch connects to every spine switch. Provides predictable latency (always 2 hops), east-west traffic optimization, and easy horizontal scaling. Replace the Three-Tier model in modern DCs.
🏢 Three-Tier Hierarchical
Traditional enterprise topology with Core (fast backbone), Distribution (routing/policies), and Access (endpoint connection) layers. Predictable, well-understood, but more latency for east-west traffic than Spine-Leaf.
↔ Point-to-Point
A direct connection between exactly two devices. Used in WAN links (leased lines, T1/T3), serial connections, and PPP. Simple but doesn't scale. Very common in WAN environments and wireless backhaul.
🔀 Hybrid
Combines two or more topology types. Most real-world networks are hybrid — e.g., a star LAN connected via a mesh WAN. Provides flexibility to optimize different parts of the network for their specific needs.
🗜 Collapsed Core
Merges the Core and Distribution layers into one. Used in smaller networks where the cost and complexity of separate layers isn't justified. Reduces hardware cost but may become a bottleneck as the network grows.
Ports & Protocols
Port numbers identify specific services running on a device. Well-known ports are 0–1023, registered ports 1024–49151, dynamic/ephemeral ports 49152–65535. Know these cold for the exam.
UDP = connectionless, fast, no guarantees — used for DNS, streaming, gaming, VoIP.
| Port | Protocol | Transport | Full Name | Description |
|---|---|---|---|---|
| 20/21 | FTP | TCP | File Transfer Protocol | Port 21 = control (commands). Port 20 = data transfer (active mode). Cleartext — not secure. Use SFTP or FTPS instead. |
| 22 | SSH / SFTP | TCP SECURE | Secure Shell / Secure FTP | Encrypted remote access shell. SFTP tunnels file transfers over SSH. Replaced Telnet and FTP for secure management. Uses public key or password auth. |
| 23 | Telnet | TCP | Teletype Network | Remote access — CLEARTEXT. Credentials and data sent in plain text. Never use in production. Replaced by SSH. Still appears on exam — know it's insecure. |
| 25 | SMTP | TCP | Simple Mail Transfer Protocol | Sends outbound email between mail servers. Also used by clients to submit email. Port 587 (STARTTLS) or 465 (SMTPS) for secure submission. |
| 53 | DNS | TCP+UDP | Domain Name System | Resolves hostnames to IP addresses. UDP for queries (fast, small). TCP for zone transfers between DNS servers (large data). Hierarchical: root → TLD → authoritative. |
| 67/68 | DHCP | UDP | Dynamic Host Config Protocol | Port 67 = server, 68 = client. Auto-assigns IP config. Process: DORA — Discover, Offer, Request, Acknowledge. Leases IPs for a time period. |
| 80 | HTTP | TCP | Hypertext Transfer Protocol | Unencrypted web traffic. Request/response model. Methods: GET, POST, PUT, DELETE, HEAD. Stateless — cookies maintain sessions. OSI Layer 7. |
| 443 | HTTPS | TCP SECURE | HTTP Secure (over TLS) | HTTP encrypted via TLS. Uses certificates (PKI) for authentication. TLS 1.3 is current standard. HSTS forces HTTPS. Essential for any production web service. |
| 161/162 | SNMP | UDP | Simple Network Mgmt Protocol | 161 = queries to devices (GET). 162 = traps sent FROM devices to NMS (unsolicited alerts). v1/v2c use community strings (insecure). v3 adds encryption and auth. |
| 389 | LDAP | TCP+UDP | Lightweight Directory Access Protocol | Queries/modifies directory services (Active Directory). LDAPS on port 636 adds TLS encryption. Used for authentication, user/group lookup. Think "phone book for the network." |
| 3389 | RDP | TCP | Remote Desktop Protocol | Microsoft's remote GUI access protocol. Full graphical desktop session over the network. Should always be behind VPN or have NLA enabled. Common attack target — keep it off the public internet. |
| 5060/5061 | SIP | TCP+UDP | Session Initiation Protocol | Initiates, modifies, terminates VoIP sessions. Port 5060 = cleartext, 5061 = TLS encrypted. Works with RTP (Real-Time Transport, UDP) for actual voice/video payload. |
Protocol Analysis Tips
Secure vs Insecure Pairs
UDP Protocols
These use UDP because speed matters more than reliability:
DHCP DORA Process
Traffic Types
Network traffic is classified by how it's addressed and delivered. Understanding these distinctions is key for designing efficient networks and configuring devices correctly.
One-to-one communication. Traffic sent from a single source to a single specific destination. Most normal web browsing, file transfers, and connections are unicast. Every device has a unique IP address for unicast.
One-to-many (specific group) communication. A single source sends to a defined multicast group. Efficient for streaming, video conferencing, routing protocol updates. IPv4 multicast range: 224.0.0.0–239.255.255.255 (Class D).
One-to-nearest communication. Traffic is sent to one address but multiple nodes share it — routing sends traffic to the topologically nearest one. Used in CDNs, DNS (Cloudflare 1.1.1.1, Google 8.8.8.8), and IPv6. Provides redundancy and performance.
One-to-all communication within a broadcast domain. Delivered to all devices on the local subnet. IPv4 broadcast address: 255.255.255.255 (limited) or subnet directed (e.g., 192.168.1.255). Routers do NOT forward broadcasts — they stop at router boundaries. IPv6 has no broadcast (uses multicast instead).
Broadcast Domain: Devices that receive broadcasts. Only routers break broadcast domains. Switches do NOT reduce broadcasts (unless VLANs are configured).
Transmission Media
The physical or wireless medium used to carry network signals. Different media have different bandwidth, range, interference susceptibility, and cost characteristics.
Wireless
5 GHz = shorter range, faster, less congested
Uses licensed spectrum bands. Network divided into cells with base stations (towers). Handoff between cells as device moves. 5G uses millimeter wave (mmWave) for ultra-fast short range and sub-6GHz for broad coverage.
GEO: traditional, high latency, good coverage. LEO: Starlink/OneWeb, low latency, better for realtime traffic. Used for remote/rural connectivity where no terrestrial option exists. Weather-sensitive. Line-of-sight required.
Wired
MMF: Multiple light paths, OM1–OM5, used in data centers. OM5 supports SWDM.
Connectors & Transceivers
Physical connectors terminate cables and mate with ports. Transceivers convert between electrical and optical signals. Knowing connector types is critical for real-world work and the exam.
Fiber Connectors
Copper Connectors
Transceivers (SFP / QSFP)
SFP / SFP+
Small Form-factor Pluggable. Hot-swappable transceiver module used in switches, routers, and NICs. SFP supports up to 1 Gbps. SFP+ supports 10 Gbps. Can carry fiber or copper (via DAC). Enables flexible, modular port design.
QSFP / QSFP+
Quad Small Form-factor Pluggable. Carries 4 lanes of data. QSFP supports 40G (4×10G). QSFP+ also 40G. QSFP28 supports 100G (4×25G). Used in spine switches, high-bandwidth server links, and data center interconnects.
BiDi (Bidirectional)
Transmits and receives on a single fiber strand using two different wavelengths (WDM — Wavelength Division Multiplexing). Useful when fiber runs are expensive or limited. Must be paired with matching BiDi on other end (TX wavelength A ↔ RX wavelength B).
IPv4 Addressing
IPv4 uses 32-bit addresses written in dotted decimal notation (four octets, each 0–255). Understanding address types, classes, and special ranges is foundational to networking.
Address Classes
| Class | First Octet Range | First Bits | Default Subnet Mask | Private Range (RFC 1918) | Networks / Hosts | Purpose |
|---|---|---|---|---|---|---|
| A | 1–126 |
0xxxxxxx |
255.0.0.0 /8 |
10.0.0.0–10.255.255.255 |
128 networks / 16.7M hosts | Large organizations, ISPs |
| B | 128–191 |
10xxxxxx |
255.255.0.0 /16 |
172.16.0.0–172.31.255.255 |
16,384 networks / 65,534 hosts | Medium-large orgs |
| C | 192–223 |
110xxxxx |
255.255.255.0 /24 |
192.168.0.0–192.168.255.255 |
2M+ networks / 254 hosts | Small networks, home/office |
| D | 224–239 |
1110xxxx |
N/A | N/A | N/A | Multicast groups only |
| E | 240–255 |
1111xxxx |
N/A | N/A | N/A | Reserved / Experimental |
Special Address Ranges
Special Purpose Addresses
Public vs Private
Private IPs (RFC 1918): Not routable on the public internet. Used internally. Translated to public IPs via NAT (Network Address Translation) at the router/firewall.
Public IPs are assigned by IANA and RIRs (ARIN, RIPE, APNIC). Every public address is globally unique. NAT allows thousands of internal devices to share a single public IP.
Subnetting & CIDR
Subnetting divides a large network into smaller sub-networks. CIDR (Classless Inter-Domain Routing) replaces class-based addressing with flexible prefix lengths. VLSM (Variable Length Subnet Masking) allows different subnet sizes within the same address space.
The subnet mask determines which bits are the network portion and which are the host portion.
| CIDR | Subnet Mask | Wildcard | Hosts (Usable) | Addresses | Subnets from /24 | Notes |
|---|---|---|---|---|---|---|
| /8 | 255.0.0.0 | 0.255.255.255 | 16,777,214 | 16,777,216 | — | Class A size |
| /9 | 255.128.0.0 | 0.127.255.255 | 8,388,606 | 8,388,608 | — | |
| /16 | 255.255.0.0 | 0.0.255.255 | 65,534 | 65,536 | — | Class B size |
| /17 | 255.255.128.0 | 0.0.127.255 | 32,766 | 32,768 | — | |
| /20 | 255.255.240.0 | 0.0.15.255 | 4,094 | 4,096 | 16 subnets | |
| /21 | 255.255.248.0 | 0.0.7.255 | 2,046 | 2,048 | 8 subnets | |
| /22 | 255.255.252.0 | 0.0.3.255 | 1,022 | 1,024 | 4 subnets | |
| /23 | 255.255.254.0 | 0.0.1.255 | 510 | 512 | 2 subnets | |
| /24 | 255.255.255.0 | 0.0.0.255 | 254 | 256 | 1 subnet | Most common LAN |
| /25 | 255.255.255.128 | 0.0.0.127 | 126 | 128 | 2 subnets | |
| /26 | 255.255.255.192 | 0.0.0.63 | 62 | 64 | 4 subnets | |
| /27 | 255.255.255.224 | 0.0.0.31 | 30 | 32 | 8 subnets | |
| /28 | 255.255.255.240 | 0.0.0.15 | 14 | 16 | 16 subnets | |
| /29 | 255.255.255.248 | 0.0.0.7 | 6 | 8 | 32 subnets | Small segments |
| /30 | 255.255.255.252 | 0.0.0.3 | 2 | 4 | 64 subnets | Point-to-point links |
| /31 | 255.255.255.254 | 0.0.0.1 | 2 (no net/bcast) | 2 | 128 subnets | P2P (RFC 3021) |
| /32 | 255.255.255.255 | 0.0.0.0 | 1 | 1 | — | Host route (loopback) |
How to Subnet — Step by Step
Example: You have 192.168.10.0/26. Find the network, broadcast, host range, and number of subnets from /24.
/25 → block = 128 → subnets: .0, .128
/26 → block = 64 → subnets: .0, .64, .128, .192
/27 → block = 32 → subnets: .0, .32, .64, .96, .128, .160, .192, .224
VLSM — Variable Length Subnet Masking
VLSM allows using different subnet sizes within the same network. Instead of giving every subnet the same size (wasting addresses), you allocate exactly what's needed. Key principle: allocate largest subnets first.
Scenario: Given 172.16.0.0/16, create subnets for:
Cloud Concepts
Cloud networking extends traditional networking concepts into virtualized, on-demand infrastructure. Understanding cloud deployment and service models, virtual networking constructs, and security is increasingly important for modern network professionals.
Deployment Models
☁️ Public Cloud
Infrastructure owned and managed by a third party (AWS, Azure, GCP). Resources shared across multiple customers (multi-tenant). Pay-as-you-go. No upfront hardware cost. Highly scalable. Data leaves your premises — security/compliance concern for some industries.
🏢 Private Cloud
Infrastructure dedicated exclusively to one organization. Can be on-premises (owned hardware) or hosted by a third party. Full control over security, compliance, and customization. Higher upfront cost. Common in government, healthcare, finance. OpenStack, VMware vSphere.
🔀 Hybrid Cloud
Combination of public and private cloud, connected via VPN or dedicated link (AWS Direct Connect, Azure ExpressRoute). Sensitive workloads stay on-prem; scalable burst workloads move to public cloud. Requires consistent network policies and identity across both.
Service Models
IaaS — Infrastructure as a Service
Provider manages hardware, networking, and storage. You manage: OS, middleware, runtime, applications, and data. Most control, most responsibility. Think AWS EC2, Azure VMs. Good for custom configurations and migrations.
PaaS — Platform as a Service
Provider manages infrastructure AND OS and middleware. You only manage applications and data. Faster development — no server patching. Examples: Heroku, Google App Engine, AWS Elastic Beanstalk. Less control over underlying environment.
SaaS — Software as a Service
Everything managed by the provider. You just use the application. No infrastructure management whatsoever. Examples: Google Workspace, Microsoft 365, Salesforce, Zoom. Least control, least responsibility. Pay per user/subscription.
Cloud Networking Concepts
VPC — Virtual Private Cloud
An isolated, logically segmented section of a cloud provider's network. You define IP ranges (CIDR), subnets, route tables, and gateways. VPCs are isolated by default — traffic doesn't cross between VPCs unless explicitly peered. Think of it as your own virtual data center in the cloud.
Contains: subnets (public and private), internet gateways, NAT gateways, route tables, security groups, and NACLs.
Network Security Groups (NSGs)
Virtual firewall that controls inbound and outbound traffic at the VM/instance level or subnet level. Rules specify: protocol, port range, source/destination IP. Stateful — if you allow inbound, return traffic is automatically allowed.
NFV — Network Functions Virtualization
Replaces dedicated hardware appliances with software running on standard servers/VMs. Virtual routers, firewalls, load balancers, IDS/IPS, WAN optimization — all virtualized. Benefits: faster deployment, lower cost, flexibility, centralized management. Examples: Cisco CSR, Palo Alto VM-Series, F5 Virtual Edition.
Cloud Gateways
Allows VPC resources to connect to the internet. Required for public subnets.
Allows private subnet instances to reach the internet without being directly accessible. Outbound only.
Connects VPC to on-premises network over encrypted IPsec VPN tunnel.
Connects multiple VPCs. Transit Gateway is a hub; VPC Peering is direct 1:1.
VPC Architecture Visual
Glossary of Terms
Quick-reference definitions for all key networking concepts covered in this module.
Open Systems Interconnection model — 7-layer framework standardizing how network communication functions are divided and defined.
Protocol Data Unit — the form data takes at each OSI layer. Bit (L1), Frame (L2), Packet (L3), Segment (L4), Data (L5-7).
48-bit hardware address burned into NIC. Used at Layer 2 for local network communication. Format: AA:BB:CC:DD:EE:FF.
32-bit (IPv4) or 128-bit (IPv6) logical address used at Layer 3 to identify devices globally and enable routing across networks.
32-bit value that defines the network and host portions of an IP address. Written in dotted decimal (255.255.255.0) or CIDR notation (/24).
Classless Inter-Domain Routing — flexible IP address allocation using prefix length notation (/24) replacing fixed class boundaries.
Variable Length Subnet Masking — using different prefix lengths within the same network to allocate address space efficiently based on actual needs.
Group of devices that receive each other's broadcast messages. Routers separate broadcast domains; switches do not (without VLANs).
Network segment where data packets can collide. Each switch port creates its own collision domain. Hubs share one collision domain.
Layer 3 device that forwards packets between different networks based on IP addresses. Maintains routing tables. Breaks broadcast domains.
Layer 2 device that forwards frames using MAC address CAM table. Creates separate collision domains per port. Supports VLANs.
Security device that filters network traffic based on rules. Stateless (packet-by-packet) or stateful (connection-aware). NGFW adds L7 inspection.
Intrusion Detection System — passive monitoring tool that detects and alerts on suspicious activity. Does not block traffic.
Intrusion Prevention System — active inline device that detects AND blocks malicious traffic in real time.
Distributes incoming traffic across multiple servers to optimize performance, availability, and prevent overload.
Intermediary server between clients and the internet. Forward proxy hides clients; reverse proxy hides servers.
Network Attached Storage — file-level storage device on a network. Uses NFS/SMB. Has own IP. Multiple clients can access simultaneously.
Storage Area Network — dedicated high-speed network for block-level storage. Uses Fibre Channel or iSCSI. Appears as local disk to servers.
Wireless Access Point — device that allows wireless clients to connect to a wired network. Operates at Layer 1-2.
Transmission Control Protocol — connection-oriented Layer 4 protocol. Provides reliable, ordered delivery via 3-way handshake and acknowledgments.
User Datagram Protocol — connectionless Layer 4 protocol. Fast but no delivery guarantees. Used for DNS, streaming, gaming, DHCP.
File Transfer Protocol — TCP port 20 (data) and 21 (control). Transfers files over a network. Cleartext — insecure. Replaced by SFTP/FTPS.
SSH File Transfer Protocol — secure file transfer over SSH (port 22). Encrypts all data and credentials. Replacement for FTP.
Secure Shell — encrypted protocol (TCP 22) for remote command-line access. Replaced Telnet. Uses public/private key or password auth.
TCP port 23. Remote access protocol that transmits all data in cleartext. Insecure — should never be used in production. Replaced by SSH.
Simple Mail Transfer Protocol — TCP port 25. Sends outbound email between mail servers. Port 587 for TLS submission, 465 for SMTPS.
Domain Name System — resolves hostnames to IP addresses. UDP port 53 for queries, TCP 53 for zone transfers. Hierarchical distributed database.
Dynamic Host Configuration Protocol — UDP 67/68. Auto-assigns IP config. Process: DORA (Discover, Offer, Request, Acknowledge).
Hypertext Transfer Protocol — TCP port 80. Unencrypted web protocol. Stateless request/response model. Layer 7 application protocol.
HTTP Secure — TCP port 443. HTTP over TLS encryption. Uses SSL/TLS certificates for authentication and encryption.
Simple Network Management Protocol — UDP 161/162. Monitors and manages network devices. v3 adds encryption. Traps are unsolicited alerts.
Lightweight Directory Access Protocol — TCP/UDP 389. Queries directory services like Active Directory. LDAPS (636) adds TLS encryption.
Remote Desktop Protocol — TCP 3389. Microsoft's GUI remote access protocol. Keep behind VPN; common attack target on public internet.
Session Initiation Protocol — TCP/UDP 5060 (5061 for TLS). Sets up, modifies, terminates VoIP/video sessions. Works with RTP for media.
One-to-one network communication. Traffic sent from single source to single specific destination. Most internet traffic is unicast.
One-to-many communication to a defined group. Efficient for streaming. IPv4 range: 224.0.0.0–239.255.255.255 (Class D).
Traffic sent to one address shared by multiple nodes — delivered to the topologically nearest one. Used in CDNs and DNS.
One-to-all within a broadcast domain. Address 255.255.255.255. Routers do not forward broadcasts. IPv6 eliminates broadcast in favor of multicast.
Transmission medium using light pulses through glass/plastic. Immune to EMI. SMF for long distance, MMF for short range. Extremely high bandwidth.
Cable with copper core surrounded by metallic shield. Used for cable TV (F-type) and legacy Ethernet. RG-6 for broadband, RG-59 for CCTV.
Direct Attach Copper — twinaxial cable with SFP+/QSFP connectors. Cheaper than fiber for short data center connections. Passive or active variants.
Single-Mode Fiber — single light path, 9μm core, yellow jacket. Long-distance (100+ km). Used in WAN and ISP infrastructure. OS2 standard.
Multi-Mode Fiber — multiple light paths, 50/62.5μm core, orange/aqua jacket. Short range (~2km). OM1–OM5 grades. Used in data centers.
IEEE standard for Wi-Fi wireless networking. Multiple amendments (a/b/g/n/ac/ax) define frequencies, speeds, and features.
Subscriber Connector — square push-pull fiber connector. Older standard, still found in legacy fiber deployments. Larger than LC.
Lucent Connector — small form-factor fiber connector with latch. Most common modern fiber connector. Half the size of SC. Used in high-density environments.
Multi-fiber connector carrying 12 or 24 fibers. Used for 40G/100G high-density connections. MTP is a high-performance MPO brand.
8P8C connector for Ethernet twisted-pair cabling (Cat5e, Cat6, Cat6a). Standard wired network connector in offices and homes.
6P2C/4C connector smaller than RJ45. Used for telephone lines and DSL modems. Not compatible with Ethernet.
Bayonet Neill-Concelman — twist-lock coaxial connector. Used in CCTV cameras, legacy 10BASE2 Ethernet, and test equipment.
Screw-on coaxial connector used for cable TV, satellite dishes, and broadband internet (DOCSIS modems).
Small Form-factor Pluggable — hot-swappable transceiver for 1 Gbps (SFP) or 10 Gbps (SFP+). Fiber or copper via DAC cable.
Quad SFP — 4-lane transceiver. QSFP28 = 100G. Used in high-bandwidth spine switches and server links.
All devices connect to a central switch/hub. Most common LAN topology. Easy troubleshooting but center is a single point of failure.
Every device connects to every other. Highly redundant. n(n-1)/2 connections needed. Used in WAN/critical networks.
Modern data center topology. Every leaf connects to every spine. Equal latency (2 hops), optimized for east-west traffic.
Core/Distribution/Access layers. Traditional enterprise design. Core for speed, Distribution for routing/policy, Access for endpoints.
Core and Distribution layers merged. Cost-effective for smaller networks. Risk of becoming a bottleneck as network grows.
Defines private IP address ranges not routable on the internet: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16.
Automatic Private IP Addressing — 169.254.0.0/16. Self-assigned when DHCP fails. Indicates DHCP is broken. Only communicates locally.
Network Address Translation — translates private IPs to public IPs at the router/firewall. PAT (Port Address Translation) shares one public IP among many devices.
Virtual Private Cloud — isolated virtual network in a cloud provider. You control subnets, routing, gateways, and security rules.
Network Functions Virtualization — replacing dedicated hardware appliances (routers, firewalls) with software on commodity servers.
Virtual firewall at instance level in cloud environments. Stateful — return traffic automatically permitted. Applied to VMs/instances.
Network Access Control List — stateless firewall at subnet level in cloud. Rules processed in numbered order. Must define both inbound and outbound rules.
Infrastructure as a Service — cloud model where provider manages hardware; you manage OS, runtime, and applications.
Platform as a Service — provider manages infrastructure and OS; you manage applications and data only.
Software as a Service — provider manages everything; you just use the application. Examples: Gmail, Microsoft 365, Salesforce.
Cloud component that allows VPC resources in public subnets to communicate with the internet.
Cloud component that lets private subnet instances reach the internet for outbound traffic without being publicly accessible.
Address Resolution Protocol — maps IP addresses to MAC addresses on a local network. Broadcasts "who has IP x.x.x.x?" and caches responses.
Open Shortest Path First — link-state interior routing protocol. Uses Dijkstra algorithm. Fast convergence. Hierarchical with areas.
Border Gateway Protocol — the internet's routing protocol. Path-vector. Used between ISPs and for cloud multi-homing. Exterior Gateway Protocol.
Virtual LAN — logically segments a switch into separate networks. Devices on different VLANs cannot communicate without a router (Layer 3 switch).
Spanning Tree Protocol — prevents Layer 2 loops in switched networks by blocking redundant paths and electing a root bridge.
Transport Layer Security / Secure Sockets Layer — cryptographic protocol providing encryption, authentication, and integrity. TLS 1.3 is current standard.
Wavelength Division Multiplexing — transmitting multiple wavelengths of light simultaneously on a single fiber. DWDM for ultra-dense deployments.
Control And Provisioning of Wireless Access Points — protocol used between wireless LAN controller and lightweight access points.