Chapter 11 — Computer Networks

What is a Computer Network?
A computer network is a collection of two or more interconnected devices (computers, servers, printers, routers, switches, IoT devices) that can communicate and share resources (files, printers, internet connection). Networks enable data exchange using standardized rules called protocols.

Why networks?
To share resources and information, centralize data, communicate (email, chat, video call), and provide services (web, file transfer, remote access). Networks reduce cost, improve collaboration, and enable distributed computing.

Basic components

• End devices (hosts): PCs, smartphones, servers.
• Transmission media: Copper cable, optical fiber, wireless (Wi‑Fi, cellular).
• Intermediary devices: Switches (link-layer), routers (network-layer), hubs, access points.
• Protocols: Rules for communication, e.g., TCP/IP, HTTP, DNS.

Types of networks by scale

• PAN (Personal Area Network) – very small, e.g., Bluetooth devices.
• LAN (Local Area Network) – single building or campus, e.g., school network.
• MAN (Metropolitan Area Network) – city-wide.
• WAN (Wide Area Network) – covers large geographic areas, e.g., the Internet.

Topologies (physical/logical layouts): Bus, Star, Ring, Mesh, Tree. Choice affects performance, fault tolerance and cost.

Switching techniques

• Circuit switching: A dedicated path is reserved for the duration of a connection (e.g., traditional telephone networks).
• Packet switching: Data is broken into packets routed independently; efficient and robust (used on the Internet).

Network models

• OSI model: 7 layers (Application, Presentation, Session, Transport, Network, Data Link, Physical) — conceptual for learning.
• TCP/IP model: 4 layers (Application, Transport, Internet, Network Access) — practical for the Internet.

Addressing and naming

• MAC address: Hardware address assigned to network interface (link-layer).
• IP address: Logical address for routing (IPv4: dotted decimal, IPv6: hexadecimal).
• DNS: Domain Name System maps human-friendly names to IP addresses.

Common services and applications: Web browsing (HTTP/HTTPS), email (SMTP/IMAP/POP), file transfer (FTP/SFTP), remote login (SSH), streaming, VoIP, online gaming.

Performance metrics (brief): Bandwidth (capacity), Throughput (actual data rate), Latency (delay), Jitter (variability of delay), Packet loss. These determine user experience for applications like video conferencing and gaming.

Security basics: Authentication, encryption (TLS/SSL), firewalls, access control, VPNs. Security protects confidentiality, integrity and availability of data.

Advantages of networking: Resource sharing, centralized management, improved communication, scalability. Disadvantages: Security risks, complexity, potential congestion and single points of failure if not designed well.

A computer network is a set of devices connected to share resources and exchange data. Networks are classified mainly by their geographic scope, ownership and purpose. The common types are:

• Personal Area Network (PAN): Very small network around one person (range ~1–10 m). Typically uses Bluetooth, USB or Zigbee to connect a smartphone, headset, keyboard, or smartwatch.
• Local Area Network (LAN): Connects devices within a limited area such as a home, office or school (range ~10 m to a few km). Often uses Ethernet or Wi‑Fi. LANs are usually owned and managed by a single organization and provide high data rates.
• Campus/Corporate Area Network (CAN): Larger than a LAN, covering a campus or business complex (tens of km). Connects multiple buildings using high‑speed links and often centralized services.
• Metropolitan Area Network (MAN): Spans a city or metropolitan area (up to ~50 km). MANs connect multiple LANs and are typically provided by a municipality or telecom provider using fiber‑optic backbones.
• Wide Area Network (WAN): Covers large geographic areas — regions, countries or continents. WANs interconnect LANs and MANs using leased lines, satellite links or long‑distance fiber. The Internet is an example of a global WAN.
• Global/Internet (GAN): A network of networks spanning the globe. The Internet is the primary example: it interconnects many WANs and MANs to provide worldwide communication.
• Storage Area Network (SAN): A specialized high‑speed network that provides block‑level storage access, typically inside data centers to connect servers and storage devices.

Key distinguishing factors: coverage area (range), ownership/administration (private vs public), typical technologies, and typical data rates. Smaller networks (PAN, LAN) give higher speeds and more direct control; larger networks (MAN, WAN) cover greater distances but rely on intermediate providers and often have higher latency.

Related concepts often shown with types of networks: typical topologies used inside networks (star, bus, ring, mesh) and common devices (NICs, switches, routers, modems) that connect different network types.

Definition: Network topology is the arrangement or layout of nodes (computers, printers, switches, routers) and the physical or logical connections between them. Topology affects performance, fault tolerance, cost and scalability of a network.

Common topologies:

• Bus topology: All devices share a single central cable (backbone). Each device is connected to the backbone via a drop line. Easy and cheap for small networks but performance and reliability degrade with more nodes; requires terminators at ends.
• Star topology: Every node connects to a central device (hub/switch). If a peripheral node fails, only that node is affected; if the central device fails, the whole network goes down. Easy to manage and expand.
• Ring topology: Nodes form a closed loop; each node connects to two neighbors. Data travels in one or both directions. Predictable performance, but a single break can disrupt the network unless there is redundancy (dual ring).
• Mesh topology: Every node has a link to every other node (full mesh) or some nodes have multiple interconnections (partial mesh). Provides high redundancy and fault tolerance but high cost and cabling complexity.
• Tree (hierarchical) topology: Combination of star topologies arranged in levels (rooted tree). Useful for large networks with clear hierarchy (campus, organization networks).
• Hybrid topology: Any combination of two or more topologies (e.g., star–bus, star–ring). Chosen to meet specific requirements for cost, performance and reliability.

Key characteristics to compare:

• Cost (cabling, devices)
• Scalability (ease of adding nodes)
• Reliability and fault tolerance
• Performance (collision domains, latency)
• Ease of maintenance and troubleshooting

Advantages / Disadvantages (summary):

• Bus: inexpensive for small nets; hard to troubleshoot and limited cable length.
• Star: easy to manage and extend; depends on central device.
• Ring: orderly access with predictable delays; vulnerable to break unless redundant.
• Mesh: excellent redundancy and minimal single-point failures; expensive and complex.
• Tree: scalable and easy to expand; depends on higher-level nodes (partial single points of failure).
• Hybrid: flexible to meet needs; complexity varies with combination.

When to choose which topology: For small home or office networks, star (switch/Wi‑Fi) is most common. For high-availability backbones, partial/full mesh is preferred. Tree/hierarchical suits campuses and large organizations. Bus is mostly historical (older Ethernet coax, simple fieldbuses) and is rarely used for new installations.

Overview
Network devices are hardware components that connect computers and other devices to form a network, forward data, control traffic, and provide services (security, access, translation). Each device operates at one or more OSI layers and has specific functions and intelligence.

Common Network Devices and Their Roles

• Network Interface Card (NIC) (Layer 1/2): Physical adapter in a computer that converts data to electrical/optical/radio signals and provides a MAC address for frames.
• Repeater (Layer 1): Regenerates and amplifies signals to extend transmission distance; no filtering or addressing.
• Hub (Layer 1): Multiport repeater; broadcasts incoming frames to all ports (creates single collision domain).
• Bridge (Layer 2): Connects two LAN segments, filters traffic by MAC address, reduces collision domains.
• Switch (Layer 2, sometimes Layer 3): Forwards frames to specific ports using a MAC address table; isolates collision domains; Layer 3 switches add routing between VLANs.
• Router (Layer 3): Routes packets between different networks/subnets using IP addresses and routing tables; performs path selection and packet forwarding.
• Modem (Layer 1/2): Modulates digital signals to analog for transmission over phone lines/cable and demodulates on reception — used by ISPs to connect homes to the network.
• Gateway (Multi-layer / Application): Translates between different protocols or architectures (e.g., email gateway, VoIP gateway). Often operates at higher OSI layers.
• Wireless Access Point (AP) (Layer 2/1): Provides wireless clients access to a wired network; manages RF, authentication (often works with a controller).
• Firewall (Layer 3–7): Enforces security policies by filtering traffic based on IP/port/application rules; can be packet-filtering, stateful, or application firewall.
• Proxy Server (Application Layer): Intermediary for client requests, used for caching, filtering and logging.
• Load Balancer (Layer 4–7): Distributes incoming traffic across multiple servers to improve availability and performance.

Key Properties to Compare

• OSI Layer(s) of operation (intelligence increases at higher layers)
• Forwarding decision basis: electrical signal, MAC, IP, application data
• Domain control: collision domains vs broadcast domains
• Typical use: home (modem+router+AP) vs enterprise (core switches, routers, firewalls)

How They Work Together (simple flow)

In a typical home setup: NIC (PC) ↔ AP/switch ↔ router (NAT & DHCP) ↔ modem ↔ ISP network. In enterprise: hosts → access switches → distribution switches → core routers → Internet/DMZ, with firewalls and load balancers protecting services.

Practical Notes

• Switches divide collision domains; routers divide broadcast domains (subnets).
• Choose devices by scale and features: unmanaged vs managed switches, consumer vs enterprise firewalls/routers.
• Performance metrics: throughput, latency, port density, supported protocols (VLANs, QoS).

What is Transmission Media?
Transmission media are the physical pathways that connect computers, devices and networks so that data can be transmitted from one point to another. They determine the speed, distance, cost and reliability of communications.

Classification

• Guided (Wired) Media – Signals are confined to a physical conductor or optical fibre.
  • Twisted Pair Cable (UTP/STP): Pairs of insulated copper wires twisted to reduce interference. Used for telephone lines, Ethernet (LAN). Pros: cheap, easy to install. Cons: limited bandwidth, susceptible to EMI.
  • Coaxial Cable: Inner conductor, insulating layer, metallic shield and outer jacket. Used for cable TV, broadband. Pros: better shielding and bandwidth than twisted pair. Cons: bulkier, more expensive than UTP.
  • Optical Fibre: Glass or plastic fibres that transmit light. Types: single-mode (long distance) and multi-mode (shorter distance). Pros: very high bandwidth, low attenuation, immune to EMI, secure. Cons: higher installation cost and fragility.
• Unguided (Wireless) Media – Signals propagate through the air or space without a physical conductor.
  • Radio Waves (including Wi-Fi, broadcast): Low-to-medium frequency, long range, penetrates obstacles depending on frequency.
  • Microwave (point-to-point, satellite uplinks): Higher frequency, line-of-sight, used for long-distance terrestrial links and satellite communication.
  • Infrared (IR): Short-range, line-of-sight, used for remote controls and short-range device links.
  • Bluetooth: Short-range (≈10 m), low-power wireless for peripheral devices and PANs.
  • Satellite: Uses microwave frequencies to cover very large areas and provide global links.

Key Characteristics & Selection Criteria

• Bandwidth (capacity): How much data can be carried per second. Fibre > coax > twisted pair > wireless (varies).
• Attenuation: Signal loss with distance; optical fibre has very low attenuation.
• Noise and Interference: Electromagnetic interference (EMI) affects copper cables more than fibre; wireless is affected by interference and fading.
• Latency: Time delay in transmission — affected by medium and distance (satellite introduces high latency).
• Cost & Installation: UTP is cheapest; fibre and satellite are costlier to install but may offer better long-term performance.
• Security: Guided media (especially fibre) are harder to tap; wireless is easier to intercept unless encrypted.

Typical Uses (CBSE perspective)

• UTP: LANs, telephones, office networks (Ethernet).
• Coaxial: Cable TV, broadband access.
• Optical Fibre: Internet backbone, long-distance telecom, data centres.
• Wi-Fi: Home/office wireless networking.
• Bluetooth: Peripheral device connectivity (headphones, mice).
• Satellite/Microwave: Remote area connectivity, TV broadcasting, global links.

Summary: Choice of transmission media depends on required bandwidth, distance, cost, environment and security. Fibre optics provide the highest performance for modern high-speed networks, while copper and wireless solutions remain common for local and mobile connectivity.

Overview: Data transmission modes describe how data flows between two devices on a communication link. Switching techniques describe how a network forwards data from source to destination across intermediate nodes. Both are fundamental to understanding how networks carry information.

1. Transmission (Direction) Modes

• Simplex: Data flows in only one direction; the sender always transmits and the receiver only receives. Example: broadcast TV. Key point: no return channel.
• Half-duplex: Data flows in both directions but not at the same time. Devices take turns transmitting. Example: walkie-talkies, CB radios. Key point: shared medium, collision/turn-taking control required.
• Full-duplex (Duplex): Data flows simultaneously in both directions. Example: telephone calls, modern Ethernet switches, mobile phones. Key point: requires separate channels or echo cancellation.

2. Data Transfer Types

• Serial vs Parallel
  • Serial: Bits sent sequentially over one channel (or pair). Used for long-distance links (USB, Ethernet, fiber).
  • Parallel: Multiple bits sent simultaneously over multiple wires. Used for short distances (older printer ports, memory buses). Parallel wires can suffer from skew at higher speeds.
• Asynchronous vs Synchronous
  • Asynchronous: Data sent character-by-character with start/stop bits; receiver uses these to frame each character (example: keyboard serial). Good for irregular traffic.
  • Synchronous: Data sent as a continuous stream with shared clocking; framing uses special sync patterns (example: streaming audio/video, high-speed backbone links). Efficient for large, steady transfers.

3. Switching Techniques

• Circuit Switching
  • A dedicated path (circuit) is established between sender and receiver before data transfer and released after the session (example: traditional PSTN telephone networks).
  • Characteristics: setup delay, constant bandwidth reserved, low jitter during call, inefficient resource use if idle.
• Message Switching
  • Entire message is sent to an intermediate node, stored, then forwarded to the next node (store-and-forward). No dedicated path; variable delay. Example: early telegraph/telex and some store-and-forward email relays.
  • Characteristics: no need for continuous path, can handle variable-length messages, can cause long delays and requires storage at nodes.
• Packet Switching
  • Messages are divided into smaller packets. Each packet is routed independently; nodes perform store-and-forward per packet. Example: the Internet (IP packets).
  • Characteristics: efficient resource sharing, better for bursty traffic, variable latency and possible reordering of packets. Two approaches: connectionless (datagram) and connection-oriented (virtual circuit).

When to use which: Circuit switching suits continuous, real-time streams with reserved bandwidth (e.g., voice calls in older networks). Packet switching is preferred for data networks with bursty traffic and efficient multiplexing (e.g., web, email, streaming over IP).

Important practical notes:

• Modern networks mix concepts: e.g., mobile networks use virtual circuits internally but carry IP packets; Ethernet switched links provide full-duplex serial communication.
• Choice between serial/parallel and async/sync depends on distance, speed, and traffic pattern.

What are Network Models?

Network models are standardized layered frameworks that describe how data is transmitted across a network. They divide network communication into smaller, well-defined tasks (layers). Each layer provides services to the layer above and uses services of the layer below. Models ensure interoperability between different hardware, software and vendors by defining functions and protocols at each layer.

Why use models?

• Abstraction: hides lower-layer details from upper layers.
• Interoperability: standardizes protocols and interfaces.
• Modularity: allows independent development and troubleshooting.

Two main models studied in Class 12:

1. OSI (Open Systems Interconnection) Model — 7 layers

• Application (Layer 7): Interface for user applications (e.g., email client, web browser). Protocols: HTTP, SMTP, FTP.
• Presentation (6): Data translation, encryption, compression (e.g., SSL/TLS does encryption; converts formats like JPEG).
• Session (5): Manages sessions/communications (establish, maintain, terminate). Examples: RPC, NetBIOS.
• Transport (4): End-to-end delivery, segmentation, error control, flow control. Protocols: TCP (reliable), UDP (unreliable).
• Network (3): Logical addressing and routing between networks. Protocols: IP, ICMP. Responsible for packet forwarding and routing decisions.
• Data Link (2): Framing, MAC addressing, error detection/correction on a single link. Sub-layers: LLC and MAC. Protocols/tech: Ethernet, PPP, ARP.
• Physical (1): Transmission of raw bit stream over physical medium: cables, voltages, bit rates, connectors.

Key OSI concepts: encapsulation (each layer adds header/trailer), headers contain control information for corresponding layer.

2. TCP/IP (Internet) Model — 4 layers

• Application: Combines OSI Application/Presentation/Session. Protocols: HTTP, SMTP, FTP, DNS.
• Transport: TCP/UDP — segmentation, reliability (TCP), multiplexing via ports.
• Internet (Network): IP — logical addressing (IPv4/IPv6), routing, packet delivery.
• Link (Network Access/Host-to-Network): Physical + Data Link responsibilities — Ethernet, Wi-Fi, ARP.

Mapping OSI to TCP/IP: Application (OSI 5–7), Transport (OSI 4), Internet (OSI 3), Link (OSI 1–2).

Encapsulation example (sending an HTTP request):

1. Application layer creates HTTP request (text).
2. Transport (TCP) splits into segments, adds TCP header (source/dest ports, seq/ack).
3. Network (IP) packages segments into IP packets, adds IP header (source/dest IPs).
4. Data Link frames the packet, adds MAC addresses and frame check sequence.
5. Physical layer transmits bits over the medium.

How models help in troubleshooting: When network issues arise, technicians identify the affected layer (e.g., no physical link → Physical layer; incorrect IP routing → Network layer; DNS resolution failure → Application layer).

Summary: Network models (OSI, TCP/IP) provide layered blueprints for designing, implementing and troubleshooting networks. They define where protocols operate and how data is packaged, routed and delivered across heterogeneous systems.

Protocols are agreed rules and procedures that two or more communicating entities follow to exchange information correctly and reliably. A protocol defines the syntax (format of data), semantics (meaning of each section of bits), and timing (when data is sent and how fast).

Standards are formal documents published by recognized bodies that specify how protocols, hardware and formats must behave so different vendors and systems interoperate. Standards ensure compatibility, safety, quality and wide adoption.

Why they are needed:

• Interoperability: devices from different vendors can communicate.
• Reliability: error detection, retransmission and ordering rules.
• Scalability: consistent addressing and routing across large networks.
• Security: agreed mechanisms (e.g., TLS) for confidentiality and integrity.

Key properties of protocols:

• Connection-oriented vs connectionless (e.g., TCP is connection-oriented; UDP is connectionless).
• Stateful vs stateless (HTTP is stateless unless session mechanisms are used).
• Layered operation: protocols operate at specific layers of a model (OSI or TCP/IP).

Common protocols by layer (examples):

• Application: HTTP/HTTPS (web), FTP (file transfer), SMTP/IMAP/POP3 (email), DNS (name resolution)
• Transport: TCP (reliable, ordered delivery), UDP (fast, unreliable), SCTP
• Network: IP (routing and addressing), ICMP (control messages), ARP (address resolution)
• Data Link / Physical: Ethernet (IEEE 802.3), Wi‑Fi (IEEE 802.11), PPP
• Security: TLS/SSL (secure channels), IPSec (secure IP)

Standards organizations: IETF (RFCs), IEEE (802.x family), ISO (OSI standards), ITU, W3C. Example standards: IEEE 802.3 specifies Ethernet; IEEE 802.11 specifies Wi‑Fi; RFCs define many Internet protocols.

How protocols work — typical tasks:

• Encapsulation: data is wrapped with headers/footers at each layer (Data → Segment → Packet → Frame → Bits).
• Addressing and routing: IP addresses, MAC addresses and routing tables deliver packets to the destination.
• Error detection and correction: parity, checksum, CRC; retransmission on error (e.g., TCP).
• Flow and congestion control: prevent sender from overwhelming receiver or network (TCP windowing, congestion algorithms).

Example protocol interaction — TCP three-way handshake:

• Client sends SYN (synchronize) with initial sequence number.
• Server replies SYN-ACK (synchronize-acknowledge).
• Client replies ACK (acknowledge). Connection established.

Error detection methods (brief):

• Parity bit — simple odd/even parity for single-bit error detection.
• Checksum — sum of bytes/words modulo a value (used in simple protocols).
• CRC (Cyclic Redundancy Check) — polynomial division method with high error-detection capability.

Importance in everyday life: Without agreed protocols and standards, web pages, email, VoIP calls, streaming video and secure transactions would not work reliably across different devices and networks.

What is an IP address?
An IP (Internet Protocol) address is a 32-bit number (IPv4) used to uniquely identify a host on an IP network. It is usually written in dotted-decimal form: four octets (bytes) separated by dots, e.g. 192.168.1.10.

Binary structure and parts
An IPv4 address has 32 bits divided into a network portion and a host portion. Which bits belong to each portion depends on the subnet mask (or prefix).

Notation
- Dotted decimal: 192.168.1.10
- CIDR (prefix) notation: 192.168.1.10/24 (means the first 24 bits are network bits)

Classful addressing (historical, for understanding)
Classes defined ranges and default masks:

• Class A: 1.0.0.0 – 126.255.255.255, default mask /8 (255.0.0.0)
• Class B: 128.0.0.0 – 191.255.255.255, default mask /16 (255.255.0.0)
• Class C: 192.0.0.0 – 223.255.255.255, default mask /24 (255.255.255.0)
• Class D: 224.0.0.0 – 239.255.255.255 (multicast)
• Class E: 240.0.0.0 – 255.255.255.255 (experimental)

Private addresses
RFC 1918 reserved ranges for private networks (not routed on the public internet): 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16.

Special addresses
- Network address: all host bits 0 (identifies the subnet)
- Broadcast address: all host bits 1 (sent to all hosts in subnet)
- Loopback: 127.0.0.1

Subnetting — why and how
Subnetting divides a larger network into smaller sub-networks (subnets). This improves management, security and reduces broadcast domains.

Subnet mask and prefix
The subnet mask is also 32 bits and shows which bits are network bits (1s) and host bits (0s). Example masks: 255.255.255.0 = /24, 255.255.255.192 = /26.

Basic steps to subnet

1. Identify the original network and its prefix (for example 192.168.10.0/24).
2. Decide how many subnets or how many hosts per subnet are required.
3. Borrow bits from host portion to make more subnets. If you borrow s bits, new prefix = original_prefix + s.
4. Number of subnets = 2^s. Number of usable hosts per subnet = 2^(host_bits) - 2 (subtract network and broadcast).
5. Find subnet increments (block size) in the octet where mask changes: increment = 256 - value_of_mask_octet.

Calculating network and broadcast addresses
Network address = (IP address) AND (subnet mask)
Broadcast address = (network address) OR (invert(subnet mask)). Use bitwise operations or work in the octet with the block size.

CIDR and aggregation
Classless Inter-Domain Routing (CIDR) uses prefixes like /20 to allocate blocks of addresses without class boundaries, allowing efficient use of address space.

Example summary
If you split 192.168.10.0/24 into /26 subnets, you borrow 2 bits (24 -> 26), so you get 2^2 = 4 subnets. Host bits = 6, usable hosts per subnet = 2^6 - 2 = 62. Subnets are: 192.168.10.0/26 (hosts .1–.62, broadcast .63), 192.168.10.64/26 (hosts .65–.126, broadcast .127), 192.168.10.128/26, 192.168.10.192/26.

VLSM (Variable Length Subnet Mask)
VLSM allows using different subnet sizes on the same network to allocate addresses efficiently (useful in routing and WAN links).

Practical points for Class 12
Understand binary conversion of octets, how to apply masks, how to compute network/broadcast addresses, and how many subnets/hosts result from changing the prefix.

Overview
Routing and switching are two complementary functions used to move data across networks. Switching is the process inside a local network (LAN) that forwards frames between devices. Routing is the process used between networks (WAN or internetworks) to determine optimal paths and forward packets from source to destination across multiple networks.

Switching (Layer 2 and below)

• Definition: Forwarding of frames within a network segment based primarily on MAC addresses (Layer 2) or circuit connections (layer 1).
• Types of switching:
  • Circuit switching: A dedicated path is established for the duration of a session (example: traditional telephone network).
  • Packet switching: Data is split into packets which are routed independently; each packet may follow a different path (example: the Internet).
  • Message switching: Whole messages are sent and stored at intermediate nodes and forwarded when possible (store-and-forward).
• Ethernet switch behavior:
  • MAC learning: switch builds a MAC address table by observing source addresses and associates them with ports.
  • Forwarding methods: store-and-forward (checks CRC then forwards), cut-through (starts forwarding once destination MAC seen), fragment-free (checks first 64 bytes to avoid collisions).
• Switch vs Hub: Switch forwards to specific port (reduces collisions), hub repeats to all ports.

Routing (Layer 3)

• Definition: Selecting paths in a network along which to send packets from source to destination using IP addresses and routing tables.
• Routing functions:
  • Build and maintain routing tables.
  • Forward packets to next-hop based on destination IP and route lookup.
• Static vs Dynamic routing:
  • Static: Admin configures fixed routes. Simple and predictable but not adaptive.
  • Dynamic: Routers exchange routing information using protocols (RIP, OSPF, BGP) to adapt to topology changes.
• Routing metrics: Hop count, bandwidth, delay, reliability, cost, load. Routing protocols use metrics to choose best path.
• Routing algorithms (brief):
  • Distance Vector (e.g., RIP): Each router maintains a vector of distances to all destinations; routers iteratively exchange vectors with neighbors (uses Bellman-Ford principle).
  • Link State (e.g., OSPF): Each router builds complete map of network topology by flooding link-state advertisements and computes shortest paths with Dijkstra's algorithm.
• Forwarding vs Routing: Routing decides the path (control plane). Forwarding moves packets to the next hop using the routing table (data plane).

Performance & Delays — Useful relations
Packet delivery time across a link is affected by several components:

• Transmission delay = packet length (L in bits) / link bandwidth (R in bits/s)
• Propagation delay = distance (d) / propagation speed (s)
• Processing delay = time router/switch takes to examine header (variable)
• Queuing delay = time packet waits in queue (depends on congestion)
• End-to-end delay = sum over all links of (transmission + propagation + processing + queuing)

Practical notes
Routers connect different IP networks and perform NAT, filtering, and route aggregation. Switches segment collision domains, provide VLANs, and operate at wire speed for local traffic. In modern networks, devices can be combined (layer 3 switches).

Summary
Switching handles local delivery of frames; routing determines inter-network paths. Packet switching and routing are fundamental to how the Internet moves data; choice of switching/routing methods affects latency, reliability and bandwidth usage.

Overview
Network services and applications are the software services and end-user programs that run on top of computer networks to provide communication, resource sharing and information access. These operate largely at the Application Layer of the TCP/IP model and use transport (TCP/UDP) and lower-layer services to move data between hosts.

Major categories

• Web services (HTTP/HTTPS): Accessing web pages and REST/APIs. Browser (client) sends an HTTP request to a server; the server responds with status codes (200 OK, 404 Not Found, 301 Moved) and content. HTTPS adds TLS/SSL for encryption and authentication.
• Email (SMTP, POP3, IMAP): Sending uses SMTP between Mail User Agent (MUA) and Mail Transfer Agent (MTA). Receiving can use POP3 (download & optionally delete) or IMAP (server-side folder management). Components: MUA, MTA, MDA (Mail Delivery Agent).
• File transfer (FTP, SFTP): Upload/download of files. FTP uses control (port 21) and data connections (active vs passive modes). SFTP/FTPS provide secure file transfer over SSH/TLS.
• Remote login/management (Telnet, SSH, RDP): Remote shell and desktop access. SSH is encrypted and preferred for secure administration; Telnet is unencrypted (deprecated for secure use).
• Name resolution (DNS): Translates domain names to IP addresses via iterative/recursive queries and caching. DNS is critical for virtually all internet services.
• Dynamic addressing (DHCP): Automatically assigns IP addresses and network configuration (gateway, DNS server) to hosts on a network for easy management.
• Real-time communication (VoIP, Video conferencing): Voice and video over IP using RTP/RTCP on top of UDP (often with SIP for session control). Requires low latency, jitter control and sufficient bandwidth.
• Streaming media: Audio/video delivered via progressive download or adaptive streaming (HLS, DASH). Content Delivery Networks (CDNs) cache content near users to reduce latency and load.
• Instant messaging / presence: Text, file sharing and presence info using XMPP, proprietary protocols (WhatsApp, Telegram). Often use persistent TCP/WebSocket connections and encryption.
• Network management & security services: SNMP for management, DHCP for addressing, firewalls and proxies for security, NAT for address translation, SSL/TLS for encrypted channels, VPN for secure remote networks.

How they work — key principles

• Client-Server model: Clients request resources; servers respond and host resources (websites, mailboxes, files).
• Peer-to-Peer (P2P): End systems act both as client and server (file-sharing, some VoIP architectures).
• Protocols: Define message formats, request/response flows, error handling and security (examples: HTTP, SMTP, DNS, FTP, SIP, RTP).
• Performance concerns: Bandwidth, latency, jitter, packet loss — different applications have different tolerances (e.g., VoIP requires low latency; bulk file transfer tolerates higher latency but benefits from high bandwidth).

Security and reliability
Applications often use TLS/SSL for confidentiality and integrity (HTTPS, SMTPS, IMAPS). Firewalls, proxies, intrusion detection/prevention, and authentication/authorization mechanisms protect services. Redundancy (multiple servers, load balancers, CDNs) improves availability.

Common real-life scenarios
Browsing websites, sending/receiving email, using cloud storage (Google Drive, OneDrive), video calls (Zoom/Meet), streaming (Netflix/YouTube), remote server administration (SSH), online gaming, IoT device telemetry and firmware updates.

Overview
A socket is a software endpoint used for network communication. A port is a numerical identifier on a host that lets the operating system direct incoming network packets to the correct application. Client-server communication uses sockets and ports so clients can connect to servers, exchange data, and terminate connections.

What is a socket?

A socket is defined by an IP address, a port number and a protocol (TCP or UDP). It provides the interface for sending and receiving data over a network. For TCP, a socket represents an end of a reliable, ordered byte stream. For UDP, a socket sends and receives independent datagrams.

Ports and their ranges

• Port numbers range from 0 to 65535.
• Well-known ports: 0–1023 (HTTP 80, HTTPS 443, SSH 22, SMTP 25).
• Registered ports: 1024–49151 (used by applications registered with IANA).
• Dynamic / private (ephemeral) ports: 49152–65535 (client-side ephemeral ports).

How client-server communication works

Typical steps (TCP):

• Server: create a socket, bind it to a local IP and port, listen for connections.
• Client: create a socket and connect to the server's IP and port.
• Server: accept the connection (returns a new socket for that client), then both sides exchange data using send/receive calls.
• Either side closes the connection when done.

Socket API sequence (common calls)

Server side (conceptual):

socket()
bind(address, port)
listen(backlog)
while (true):
    client_socket = accept()
    recv/send on client_socket
    close(client_socket)
close(server_socket)

Client side (conceptual):

socket()
connect(server_address, server_port)
send/recv
close(socket)

TCP vs UDP

• TCP: connection-oriented, reliable, ordered, uses a three-way handshake (SYN, SYN-ACK, ACK) to establish a connection and a defined teardown (FIN/ACK). Used for HTTP, SSH, SMTP.
• UDP: connectionless, low overhead, no guarantee of delivery or order. Used for DNS queries, streaming, VoIP, real-time games.

Identifying a connection

A TCP connection is uniquely identified by the 4-tuple (source IP, source port, destination IP, destination port). Including protocol (TCP/UDP) gives the 5-tuple used in network tools and firewalls.

Multiplexing and multiple clients

A server listens on one well-known port but can handle many clients: accept() returns a new socket per client connection (different source ports), letting the server maintain multiple simultaneous sessions.

Security and firewalls

Firewalls and NATs inspect port numbers to allow or block traffic. Servers must bind to ports permitted by the OS and firewall rules; clients usually use ephemeral ports assigned by the OS.

Common pitfalls & best practices

• Remember to close sockets to free resources.
• Use TLS/SSL for sensitive data even if using TCP.
• Be aware of port conflicts—only one process can bind to a port on a given IP:port pair.
• Handle partial reads/writes with TCP streams (loops until all bytes sent/received).

Overview
Wireless networking and mobile communication enable devices to exchange data without physical cables using radio waves or infrared. Wireless networks can be short-range (PAN), local (WLAN/Wi‑Fi), metropolitan (WiMAX), or wide-area (cellular and satellite). Mobile communication deals with supporting nodes that move while maintaining connectivity (handover, roaming).

Key components

• Mobile Station (MS) — the user device (phone, tablet, laptop).
• Base Station / Access Point (BS/AP) — radio node that provides wireless coverage for a cell or WLAN.
• Base Station Controller / Controller — manages multiple base stations.
• Mobile Switching Centre (MSC) / Core Network — routes calls/data and interacts with databases (HLR, VLR).
• Home Location Register (HLR) & Visitor Location Register (VLR) — databases to track subscriber profiles and location.

Types of wireless networks

• PAN (Bluetooth, ZigBee) — short range (~1–100 m) for peripherals and sensors.
• WLAN (Wi‑Fi, IEEE 802.11 family) — local area wireless for homes, offices, hotspots.
• Cellular networks (1G → 5G) — wide-area mobile coverage organized into cells served by base stations.
• WiMAX / LTE — metropolitan and broadband mobile data technologies.
• Satellite — global coverage useful where terrestrial infrastructure is absent.

Wireless LAN (Wi‑Fi) essentials

• Modes: Infrastructure (clients ↔ AP ↔ wired network) and Ad‑hoc (peer‑to‑peer).
• Access method: CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance).
• Security: WEP (obsolete), WPA/WPA2/WPA3 — encryption & authentication protocols.
• SSID identifies the network; channels/frequencies (2.4 GHz, 5 GHz, 6 GHz) affect interference and bandwidth.

Cellular systems and mobility

• Cells: geographic areas served by a base station; frequency reuse allows capacity scaling.
• Handover (handoff): transfer of an active connection from one base station to another as a user moves. Types: hard (break before make) and soft (make before break).
• Roaming: allowing a subscriber to use services outside the home network via inter‑operator agreements.
• Generations: 1G (analog voice) → 2G (digital voice, SMS) → 3G (mobile data) → 4G/LTE (IP-based high-speed data) → 5G (very high throughput, low latency, massive IoT).

Radio propagation and performance factors

• Path loss: signal power decreases with distance and obstacles (free‑space loss, shadowing, multipath fading).
• Interference and noise reduce effective data rates; techniques like OFDM and MIMO mitigate these effects.
• Throughput vs latency: capacity (how much data per second) and delay (time to deliver a packet) are key QoS metrics.

Protocols and technologies

• Bluetooth: short range, pairing for audio and peripherals.
• NFC: very short range for contactless payments.
• Mobile IP / cellular signaling: manage mobility, authentication, billing.
• LTE and 5G use advanced radio techniques (OFDMA, MIMO, carrier aggregation) to increase spectral efficiency.

Practical considerations

• Site planning: cell placement, antenna height, and power affect coverage and capacity.
• Security: always secure Wi‑Fi with WPA2/WPA3, use VPN on public networks, keep firmware updated.
• Power and battery: wireless radios consume power—important for mobile device design.

Summary
Wireless networking provides flexible connectivity across scales from personal devices to global coverage. Mobile communication adds mechanisms to maintain service while users move (handover, roaming) and requires specialized infrastructure (cells, MSC, HLR). Understanding radio behavior, protocols, and security is essential for reliable wireless services.

What is Network Security?
Network security is the set of policies, practices and technologies used to protect computer networks and the data transmitted over them from unauthorized access, misuse, modification or denial of service. Its main goals are confidentiality, integrity and availability (the CIA triad).

Core objectives (CIA triad)

• Confidentiality — ensure that only authorized users can read data (e.g., encryption).
• Integrity — ensure that data is not altered or tampered with (e.g., hashes, digital signatures).
• Availability — ensure services and data are available when needed (e.g., protection against DoS attacks).

Types of threats

• Passive attacks: eavesdropping, traffic analysis (attacker listens but does not alter traffic).
• Active attacks: modification of messages, replay attacks, man-in-the-middle (MITM), spoofing, session hijacking.
• Malware: viruses, worms, trojans, ransomware that compromise hosts and networks.
• Denial of Service (DoS/DDoS): overload a service so legitimate users cannot access it.
• Phishing & social engineering: trick users into revealing credentials or installing malware.

Basic security mechanisms

• Encryption: symmetric (same key for encrypt/decrypt; fast) and asymmetric (public/private keys; used for secure key exchange and signatures).
• Authentication: verifying identity using passwords, certificates, biometrics, or two‑factor authentication (2FA).
• Integrity checks: cryptographic hash functions (e.g., SHA family) and digital signatures to detect tampering.
• Access control: firewalls, routers, and ACLs that limit which users or IPs access network resources.
• Secure protocols: TLS/SSL for web security (HTTPS), SSH for secure remote login, IPsec for secure IP-layer communication, WPA2/WPA3 for Wi‑Fi security.
• Monitoring & detection: Intrusion Detection Systems (IDS) and Intrusion Prevention Systems (IPS) to detect and respond to attacks.
• Network segmentation and DMZ: separate parts of the network (e.g., public web servers in a DMZ) to limit damage from breaches.
• Backup and patch management: regular backups and timely software updates reduce vulnerability and speed recovery.

Example: How TLS (HTTPS) protects web traffic

• Client and server negotiate cipher suite and exchange keys (using asymmetric cryptography) to establish a secure session key.
• Once keys are exchanged, symmetric encryption protects confidentiality and MACs/hashes ensure integrity for subsequent data.
• Certificates (signed by Certificate Authorities) authenticate the server to the client.

Best practices for network security (Class 12 level)

• Use strong, unique passwords and enable two-factor authentication where possible.
• Keep operating systems and applications up to date with security patches.
• Enable firewalls and configure them to restrict unnecessary inbound/outbound traffic.
• Use HTTPS and secure Wi‑Fi standards (WPA2/WPA3) for wireless networks.
• Educate users about phishing and social engineering risks.
• Regularly back up important data and test restore procedures.

For exam-level understanding, focus on the goals (CIA), common attacks, basic countermeasures (encryption, authentication, firewalls, VPN/TLS), and simple examples like HTTPS and Wi‑Fi security.

Performance and QoS (Quality of Service) in computer networks describe how well a network carries data and how reliably it meets the needs of different applications. Performance is measured by numeric metrics such as bandwidth, throughput, delay and packet loss. QoS is a set of techniques and policies that control and guarantee certain performance levels for traffic classes (for example, voice, video, or file transfer).

Key performance metrics

• Bandwidth (Capacity): The maximum data rate a link can carry, typically in bits per second (bps).
• Throughput: The actual rate at which data is successfully delivered across the network (bps). Throughput ≤ bandwidth.
• Delay (Latency): Time taken for a packet to travel from source to destination. Components include:
• Transmission delay = packet size / link bandwidth
• Propagation delay = distance / propagation speed (speed of signal in medium)
• Processing delay = time for routers/switches to examine packet headers
• Queuing delay = time a packet waits in queue at a router (variable, depends on congestion)
• Jitter: Variation in packet delay; important for real-time apps such as VoIP and video conferencing.
• Packet loss: Fraction or rate of packets dropped due to errors or congestion.
• Availability and Reliability: Percent of time network services are up; reliability often measured with MTBF/MTTR.

Why QoS matters

• Different applications have different needs: voice/video need low delay and low jitter; file transfer needs high throughput but can tolerate delay.
• QoS mechanisms prioritize, shape, or reserve resources so critical traffic gets required performance even when the network is congested.

Common QoS techniques

• Classification and marking: Identify traffic (e.g., voice, video, best-effort) and mark packets for treatment.
• Prioritization: Give high-priority queues to delay-sensitive traffic.
• Traffic shaping and policing: Smooth bursts and limit rate to agreed levels.
• Resource reservation: Reserve bandwidth for critical flows (e.g., IntServ/RSVP concepts).
• DiffServ: Simple scalable model that marks packets into classes and routers apply per-class policies.
• Congestion control: Mechanisms (often in transport layer, e.g., TCP) that reduce sending rate when loss or delay indicates congestion.
• Caching, load balancing and link aggregation: Improve perceived performance and throughput by distributing load or combining links.

Trade-offs

• Improving one metric can affect others: prioritizing voice may reduce throughput available for bulk transfer.
• Complex QoS (fine-grained reservations) is harder to scale; simpler class-based schemes sacrifice strict guarantees for scalability.

Understanding these ideas helps design and manage networks to meet users expectations for speed, responsiveness and reliability.

Overview
When digital data is transmitted or stored, noise and faults can flip one or more bits producing errors. Error detection locates the presence of errors; error correction reconstructs the original data without needing retransmission (or indicates that retransmission is needed). Techniques are used at different layers (link, transport, storage).

Types of errors

• Single-bit error: exactly one bit flipped.
• Multiple-bit error: two or more bits flipped (can be contiguous or random).
• Burst error: a sequence of consecutive bits corrupted.

Basic approaches

• Automatic Repeat reQuest (ARQ) — detection only (e.g., checksum/CRC); on detection receiver requests retransmission.
• Forward Error Correction (FEC) — send extra redundancy so receiver can correct some errors (e.g., Hamming codes, Reed–Solomon, convolutional codes).

Simple detection methods

• Parity bit: Add 1 bit so total number of 1s is even (even parity) or odd (odd parity). Detects any odd number of bit flips (1, 3, 5 ...), but fails for two-bit errors.
• Checksum: Break data into words, sum them (often modulo 2^16 or 2^32) and send one's complement. Used in IP/TCP. Detects many common errors but not all patterns.
• Cyclic Redundancy Check (CRC): Treat bit sequence as polynomial M(x), choose generator polynomial G(x). Append r zeros (r = degree of G), divide M(x)·x^r by G(x), remainder R(x) is CRC. Receiver divides received polynomial by G(x); nonzero remainder indicates error. Strong for burst errors.

CRC concept (brief)
If message bits represent polynomial M(x) and generator is G(x) of degree r, then transmitted codeword is C(x) = M(x)·x^r + R(x) where R(x) = (M(x)·x^r) mod G(x). Receiver computes C(x) mod G(x); if result ≠ 0 → error.

Error correction — Hamming code (single-bit correction)

• Hamming codes are linear block codes that can detect 2-bit errors and correct single-bit errors.
• Place parity bits at positions that are powers of two: 1, 2, 4, 8, ... Each parity bit covers positions whose binary index has that bit = 1.
• Number of parity bits r must satisfy: 2^r ≥ m + r + 1, where m = number of data bits; this ensures unique syndromes.
• At receiver, compute parity checks → form syndrome (binary number). If syndrome = 0 → no error; else syndrome value = position of the erroneous bit, which can be flipped to correct.

Hamming example (m=4)
Data bits: d1,d2,d3,d4 = 1,0,1,1 (for example). Place parity bits p1 at pos1, p2 at pos2, p3 at pos4 → positions: 1(p1),2(p2),3(d1),4(p3),5(d2),6(d3),7(d4). Compute p1,p2,p3 so covered parities are even. Transmit 7-bit codeword. Receiver recomputes parities; syndrome gives error position.

Hamming distance and capabilities
Hamming distance d between two codewords = number of bit positions in which they differ. A code with minimum distance d_min can detect up to (d_min − 1) bit errors and can correct up to floor((d_min − 1)/2) bit errors.

When to use which method

• Low-latency links with retransmission allowed: use CRC (detection) + ARQ.
• Real-time or one-way links (e.g., satellite, streaming, memory): use FEC (Hamming, Reed–Solomon).
• Storage (hard disks, RAM): ECC memory uses Hamming-like codes for single-bit correction and multi-bit detection.

Summary
Error detection finds corrupted data (parity, checksum, CRC). Error correction reconstructs original bits (Hamming, Reed–Solomon). CRC is powerful for detecting burst errors; Hamming is simple for single-bit correction. Choice depends on error characteristics, latency and overhead.

Multiplexing

Multiplexing is the technique of combining two or more signals for transmission over a single communication channel or medium so that the channel is utilized efficiently. At the receiver end, the signals are separated by demultiplexing. Multiplexing is used to share expensive resources (cables, fiber, wireless spectrum) among many users.

Why multiplexing is needed

• Reduce cost by sharing a high-capacity link among many low-rate channels.
• Efficient utilization of bandwidth and physical media.
• Support many simultaneous users or data streams.

Main types of multiplexing

• Frequency Division Multiplexing (FDM): Each signal modulates a different carrier frequency. The carriers are spaced to avoid overlap and guard bands reduce interference. Used in analog radio broadcasting and cable TV.
• Wavelength Division Multiplexing (WDM): Optical equivalent of FDM used in fiber optics. Different data channels are carried on different light wavelengths (colors).
• Time Division Multiplexing (TDM): Each user gets the entire channel capacity but only for a short time slot in a repeating frame. Can be synchronous TDM or statistical TDM (dynamic allocation). Used in digital telephony and digital data links.
• Code Division Multiplexing (CDM/CDMA): All users transmit simultaneously over the same frequency band but are separated by unique codes. Widely used in some cellular systems.

Modulation

Modulation is the process of modifying a high-frequency carrier signal with a lower-frequency information (message) signal so the message can be transmitted efficiently over a physical medium. The reverse process is demodulation.

Why modulation is needed

• Allow transmission of low-frequency signals over antennas and long distances.
• Enable frequency multiplexing of many signals on one medium.
• Improve signal propagation and reduce antenna size by using high carrier frequency.

Analog modulation

• Amplitude Modulation (AM): The amplitude of the carrier is varied in proportion to the message. Used in AM radio.
• Frequency Modulation (FM): The carrier frequency is varied according to the message amplitude. Used in FM radio.
• Phase Modulation (PM): The carrier phase is changed according to the message.

Digital modulation

• ASK (Amplitude Shift Keying) — discrete amplitude levels represent bits.
• FSK (Frequency Shift Keying) — different frequencies represent different bit values.
• PSK (Phase Shift Keying) — different carrier phases represent symbols (BPSK, QPSK).
• QAM (Quadrature Amplitude Modulation) — combines amplitude and phase variations to transmit multiple bits per symbol, used in modern modems and Wi-Fi.

How multiplexing and modulation work together

Multiplexing combines multiple signals into one channel. Modulation shifts signals to different carrier frequencies or encodes them for transmission. For example, in FDM each input signal is modulated onto a distinct carrier; in TDM the digital signals are placed in distinct time slots and then may be modulated for transmission over the physical medium.

Demultiplexing and demodulation

At the receiver, demodulation extracts the baseband message from its carrier, and demultiplexing separates the combined channels either by filtering (for FDM/WDM), by time slot extraction (for TDM), or by decoding (for CDMA).

Important practical notes

• Guard bands and filtering are necessary in FDM/WDM to avoid inter-channel interference.
• Synchronous TDM wastes bandwidth if slots are unused; statistical TDM allocates slots dynamically to improve utilization.
• Modern systems often use OFDM (orthogonal FDM) to pack carriers tightly without guard bands, used in Wi-Fi, LTE, and digital TV.

Overview
Network Administration and Management is the set of activities required to keep a computer network running reliably, securely and efficiently. It covers configuring devices, assigning addresses, controlling access, monitoring performance, backing up data, and responding to faults.

Key responsibilities

• User and account management: create/delete user accounts, set permissions and groups.
• IP address management: plan and assign static IPs and manage DHCP pools (using CIDR/subnetting).
• Device configuration: routers, switches, firewalls, wireless access points and servers.
• Security: implement firewalls, access controls, VPNs, authentication, patching and antivirus.
• Monitoring and logging: watch network traffic, device health, and logs to detect problems.
• Backup and recovery: regular backups of critical data and configuration, and disaster recovery plans.
• Performance management: measure throughput, latency and utilization; tune QoS and bandwidth allocations.
• Incident response and change management: procedures to handle failures and controlled rollout of changes.

Important protocols and tools

• DHCP — automatic IP assignment.
• DNS — name resolution (hostnames to IPs).
• SNMP — monitoring and management of devices.
• SSH/HTTPS — secure remote administration.
• RADIUS/LDAP/Active Directory — centralized authentication and authorization.
• Network monitoring tools — e.g., Nagios, Zabbix, SolarWinds, Wireshark for traffic analysis.

Security practices

• Least privilege: give users only required access.
• Segmentation: use VLANs or subnets to separate traffic (e.g., guest Wi‑Fi vs internal network).
• Firewalls & ACLs to control traffic entering/exiting network segments.
• Regular patching, strong passwords, two‑factor authentication, and logging/alerting.

IP addressing & subnetting (simple explanation)
IPv4 addresses have 32 bits. Subnetting divides an address space into smaller networks. In CIDR notation an address looks like 192.168.10.0/26 where /26 is the prefix (number of fixed network bits).

Number of usable hosts in a subnet = 2^(32 - prefix) - 2  (subtract network and broadcast addresses)

Monitoring & performance metrics

• Throughput (actual rate of successful data transfer).
• Bandwidth (maximum possible data rate of a link).
• Latency / RTT (time for a packet to travel round trip).
• Packet loss percentage and error rates.
• Device CPU, memory, interface utilization and uptime.

Typical workflows

• Onboarding a new user: create account → allocate IP and storage → assign permissions → add to monitoring.
• Handling an outage: detect via monitoring → isolate the fault → restore service (failover/backup) → post‑mortem and patch.

Best practices

• Document network design, configuration and change history.
• Automate repetitive tasks (scripting, configuration management).
• Keep backups of device configurations and critical data offsite.
• Test disaster recovery and failover procedures periodically.

What is the Internet?
The Internet is a global system of interconnected computer networks that use the TCP/IP suite of protocols to communicate. It provides a platform for information exchange and services such as the World Wide Web, email, file transfer, streaming and many more.

Core components

• Hosts/Clients & Servers: End systems that request or provide services.
• Routers & Switches: Devices that forward packets through the network.
• Internet Service Provider (ISP): Provides access and connectivity.
• Protocols: Agreed rules for communication (TCP, IP, HTTP, FTP, SMTP, DNS, etc.).
• Domain Name System (DNS): Translates human-friendly domain names to IP addresses.

Key protocols & their roles

• IP (Internet Protocol): Packet addressing and forwarding (IPv4, IPv6).
• TCP (Transmission Control Protocol): Reliable, connection-oriented transport.
• UDP (User Datagram Protocol): Connectionless, low-overhead transport for real-time apps.
• HTTP/HTTPS: Web (hypertext) transfer; HTTPS adds TLS/SSL encryption for secure communication.
• SMTP, POP3, IMAP: Email delivery and retrieval.
• FTP/SFTP: File transfer (SFTP uses SSH for security).

How the Web works (simple request–response)
A user types a URL in a browser → DNS resolves domain to an IP → browser opens TCP connection (often TLS) to web server → browser sends an HTTP request → server responds with HTML/CSS/JS → browser renders page.

IP addressing & DNS
Each device on the internet has an IP address. IPv4 uses 32-bit addresses (e.g., 192.168.1.1); IPv6 uses 128-bit addresses. DNS maps readable names (example.com) to IP addresses so users don’t need to remember numeric addresses.

Types of internet connections

• Dial-up (obsolete), DSL, Cable, Fiber (FTTH), Mobile (3G/4G/5G), Satellite, and Wireless (Wi‑Fi).

Common Internet Services

• World Wide Web (WWW): Websites and web applications accessed via browsers.
• Email: Store-and-forward message service using SMTP/POP/IMAP.
• File Transfer: FTP, SFTP for uploading/downloading files.
• Search Engines: Index pages and return relevant results (Google, Bing).
• Streaming & VoIP: Video/audio streaming (YouTube, Netflix) and voice/video calls (Skype, WhatsApp) commonly use UDP or adaptive protocols.
• Cloud Services: Remote storage, computing (SaaS, PaaS, IaaS).
• Social Media, e-Commerce, Online Banking: Application-layer services that often require strong security.

Security & Privacy Basics
Important measures include TLS/SSL for encrypted web traffic (HTTPS), strong authentication (passwords, multi-factor), firewalls, antiviruses, and secure protocols (SFTP, SSH). Users must be aware of phishing, malware and data privacy concerns.

Performance concepts

• Bandwidth: Maximum data rate of a link (bps).
• Throughput: Actual achieved data rate (usually ≤ bandwidth).
• Latency (Delay): Time taken for a packet to travel from source to destination (ms).
• Jitter: Variation in packet delay — important for real-time apps.

Practical classroom points

• Understand roles of DNS, HTTP, TCP/IP and basic commands (ping, traceroute).
• Recognize difference between client-server and peer-to-peer models.
• Know examples of services and which protocols they use (e.g., email: SMTP/IMAP).

Summary
The Internet is a layered, protocol-driven global network enabling many services. Knowing how addressing, routing, protocols and security interact helps in understanding how everyday applications (web, email, streaming) function reliably and securely.

Overview
Practical Skills and Network Programming focuses on hands‑on abilities to build, test and debug networked applications and to use networking tools. The emphasis is on the client–server model, socket programming (TCP/UDP), simple web interaction, file transfer, basic debugging using command‑line tools and packet inspection, and on understanding protocol behaviour (handshakes, timeouts, retransmission).

What students should be able to do

• Use common network utilities: ping, traceroute, nslookup/dig, ifconfig/ip, netstat, telnet/openssl s_client.
• Write socket programs (TCP server/client and UDP sender/receiver), handle connections, message framing, timeouts and errors.
• Implement simple application protocols (e.g., text chat, file transfer, tiny HTTP server or client) and test them locally and across a LAN.
• Use packet capture tools (Wireshark/tcpdump) to observe protocol exchanges (TCP three‑way handshake, SYN/ACK, FIN).
• Apply basic security hygiene: avoid hard‑coded credentials, validate input, use TLS for sensitive data where possible.

Key concepts explained

• Sockets and ports: A socket is an endpoint identified by an IP and port. TCP provides reliable byte stream; UDP provides connectionless datagrams.
• Client–Server flow (TCP): Server binds to a port and listens; client connects; server accepts and a socket is created for that client; data exchanged; connection closed. Handle multiple clients by threads, processes, or I/O multiplexing (select/poll/async).
• Message framing: Because TCP is a stream, application messages need boundaries: use fixed‑length headers, newline delimiters, or length prefixes.
• File transfer basics: Split large files into chunks, send size or checksum metadata, acknowledge chunks, handle retransmission/timeouts.
• UDP use cases: Low-latency, loss-tolerant apps (like realtime sensors, simple discovery protocols). Add your own reliability if needed.
• Debugging & testing: Reproduce locally (localhost), on LAN, and across machines. Use Wireshark to view packet contents, check sequence numbers, flags, retransmissions.

Typical practical workflow (step-by-step)

1. Define the protocol: message format, commands, fields, delimiters.
2. Implement server: open socket, bind, listen, accept loop, per‑client handler (thread/async), parse requests, send responses, close connections gracefully.
3. Implement client: connect, send requests, implement retry/timeout logic, receive and validate responses.
4. Test small: unit test parsing and serialization, then integration tests (client↔server on same machine), then network tests (different hosts).
5. Capture traffic: run Wireshark/tcpdump while testing, verify flags, payload, round‑trip behaviour.
6. Measure and optimize: measure latency, throughput, and memory/CPU while increasing clients or message size. Optimize with pooling, non‑blocking I/O or batching.

Practical tips

• Always set socket timeouts to avoid blocking forever.
• Use length prefix or delimiter to avoid message concatenation problems with TCP.
• Close sockets in finally blocks/cleanup routines to free ports quickly.
• For file transfer, include file size and checksum (MD5/SHA1) to detect corruption.
• When teaching, show both blocking multithreaded server and single‑threaded async server to compare complexity/performance.