Chapter 8 — Computer Networks

What is a Computer Network?

A computer network is a collection of two or more interconnected devices (computers, printers, routers, switches, smartphones, etc.) that share resources and communicate using defined rules called protocols. Networks enable data exchange, resource sharing (files, printers, internet), and distributed computing.

Basic Components

• Nodes/Hosts: Devices that use or provide network services (PCs, servers, phones).
• Links/Media: Physical (copper, fiber) or wireless (Wi‑Fi, microwave) channels that carry signals.
• Network Interface Card (NIC): Hardware enabling a device to connect to a network.
• Switches: Connect devices within a local network and forward frames based on MAC addresses.
• Routers: Connect different networks and forward packets based on IP addresses.
• Modems: Convert digital data to forms suitable for transmission over telephone/cable lines.

Network Types

• LAN (Local Area Network): Small geographic area like a home, school or office.
• MAN (Metropolitan Area Network): City-wide network.
• WAN (Wide Area Network): Covers large geographic areas; the Internet is the largest WAN.
• PAN (Personal Area Network): Very small area around a person (Bluetooth devices).

Topologies (Logical/Physical)

Common physical layouts: bus, star, ring, mesh, and tree. Choice affects cost, performance, reliability and fault tolerance.

Protocols and Models

Protocols are rules for communication. Important protocol suite: TCP/IP (Internet Protocol Suite). Conceptual models: OSI (7 layers) and TCP/IP (4 layers) — they organize responsibilities such as physical transmission, routing, reliable transport, and application-level services (HTTP, FTP, SMTP).

Addressing and Naming

Every network device has identifiers: MAC address (hardware, local) and IP address (network-level, routable). DNS maps human-readable domain names to IP addresses.

Modes of Transmission

• Simplex: One-way only (e.g., keyboard to CPU).
• Half-duplex: Two-way but not simultaneously (e.g., walkie-talkie).
• Full-duplex: Two-way simultaneously (e.g., telephone, modern Ethernet).

Performance Metrics

• Bandwidth: Maximum data rate of a link (bps).
• Throughput: Actual achieved data transfer rate.
• Latency/Delay: Time taken for data to travel from source to destination.
• Jitter: Variation in packet delay (important for real-time apps).
• Packet loss: Percentage of packets lost during transmission.

Uses and Services

Networks provide internet access, email, file and print sharing, remote login, multimedia streaming, online gaming, cloud services and IoT connectivity.

Advantages and Challenges

• Advantages: Resource sharing, centralized data, communication, scalability.
• Challenges: Security risks (unauthorized access, malware), congestion, privacy, need for management and maintenance.

Simple Example Flow

When a student opens a webpage: the browser (client) sends an HTTP request to the web server's IP. Routers forward packets across networks. The server responds with webpage data; TCP ensures reliable delivery and the browser renders the page.

What is a Network? A computer network is a collection of two or more devices (computers, printers, routers, smartphones) connected to share data, resources and services. Networks are classified by size, geography, ownership and architecture. Below are the most common types studied in Class 11.

Classification by Geographical Scale

• PAN (Personal Area Network): Very short range (up to ~10 m). Connects personal devices (smartphone, laptop, Bluetooth headset). Typically wireless (Bluetooth, USB). Low cost and low power.
• LAN (Local Area Network): Covers a small area such as a home, office or school (tens to hundreds of meters). High data rates (100 Mbps to multi-Gbps). Uses switches, routers and Ethernet or Wi‑Fi. Example: school computer lab network.
• CAN (Campus/Controller Area Network) or Campus Area Network: Connects multiple LANs within a limited geographic area like a university or corporate campus (hundreds of meters to a few kilometers). Higher management/administration and faster backbone links.
• MAN (Metropolitan Area Network): Spans a city or a large campus (a few km to ~50 km). Often used by ISPs to connect customer LANs, municipal Wi‑Fi and telecommunication networks.
• WAN (Wide Area Network): Covers large geographical areas — regions, countries or global. The Internet is the largest WAN. Uses leased lines, fiber optics, satellites and long‑distance routing. Speeds and ownership are varied; costs and complexity are higher.

Classification by Architecture

• Client-Server Network: Central server provides resources/services; clients request them. Common in businesses and web services.
• Peer-to-Peer (P2P): Each node can act as client and server; simple home or small office networks often use this.

Classification by Transmission Medium

• Wired: Ethernet (copper), fiber optics — reliable and secure, usually higher throughput.
• Wireless: Wi‑Fi, Bluetooth, cellular (3G/4G/5G), satellite — offers mobility and ease of deployment.

Key Characteristics to Compare Networks: coverage area (range), typical data rate (speed), ownership/administration (private vs public), cost of setup and maintenance, reliability and latency.

Devices & Protocols: Hubs, switches, routers, access points, modems. Common protocols: Ethernet, IEEE 802.11 (Wi‑Fi), TCP/IP (Internet), Bluetooth.

What is a network topology? Network topology is the arrangement or mapping of various elements (links, nodes, switches, hubs) of a computer network. It describes how devices are connected and how data flows between them. Topologies can be physical (actual layout of cables and devices) or logical (how data travels logically).

Common topologies

• Bus topology: A single central cable (backbone) to which all devices are attached. Data sent by a device travels along the backbone and is received by all nodes; only the intended recipient processes it.
• Star topology: All devices connect individually to a central device (hub, switch, or router). Communication between devices goes through the central device.
• Ring topology: Each device is connected to two other devices, forming a closed loop. Data typically travels in one direction (token passing or circulating frames).
• Mesh topology: Every node has a direct connection to every other node (full mesh). Partial mesh connects some nodes directly. Mesh provides multiple redundant paths.
• Tree (hierarchical) topology: A set of star-configured networks connected to a linear bus backbone. It forms a hierarchical structure (root, branches, leaves).
• Hybrid topology: A combination of two or more different topologies (for example, star-ring or star-bus) used to meet specific network needs.

Advantages and disadvantages (summary)

• Bus: Low cable cost; simple to extend. But performance degrades with more nodes; single backbone is a single point of failure.
• Star: Easy to install, isolate faults, and add/remove nodes. Central device failure brings network down; more cabling than bus.
• Ring: Predictable performance under moderate load, easy to install. A single node or link failure can disrupt the entire ring unless dual/ring redundancy is used.
• Mesh: Highly reliable and fault tolerant because of multiple paths; good for critical networks. High cost and complex cabling/management for full mesh.
• Tree: Scalable and easy to manage; suitable for large networks. Root/backbone failure affects large segments; cabling cost can be high.
• Hybrid: Flexible and can be optimized for performance/reliability. Complexity and cost depend on combined topologies.

Selection criteria: Choose a topology based on cost, scalability, reliability, ease of installation and maintenance, and the physical layout of the environment.

Logical vs physical topology: The physical topology is the real cable and device layout. The logical topology describes how data moves over the network irrespective of physical connections (for example, Ethernet on a switched star has a star physical topology but can behave logically like a bus).

Practical notes: Modern LANs commonly use star topology with switches. Wide area networks (WANs) or backbone networks may use partial mesh or hybrid topologies for redundancy. Wireless networks often form star (AP-centric) or mesh (wireless mesh) topologies depending on design.

Transmission media are the physical pathways through which data signals travel from a sender to a receiver in a computer network. They determine the rate, distance, reliability and security of communication. Transmission media are broadly classified into guided (wired) media and unguided (wireless) media.

Guided (Wired) Media

• Twisted Pair Cable (UTP/STP): pairs of insulated copper wires twisted together to reduce electromagnetic interference. Common in telephone networks and Ethernet (RJ-45). Advantages: low cost, easy to install. Disadvantages: limited bandwidth and distance, susceptible to EMI.
• Coaxial Cable: central conductor, insulating layer, metallic shield and outer jacket (used for cable TV and some broadband). Higher bandwidth and better shielding than twisted pair but bulkier.
• Optical Fiber: glass or plastic fibers that transmit light pulses. Types: single-mode (long distance, high bandwidth) and multi-mode (shorter distance). Advantages: very high bandwidth, low attenuation, immune to EMI, secure. Disadvantages: higher cost and special handling/connectors (SC, LC).

Unguided (Wireless) Media

• Radio Waves: used for Wi-Fi, Bluetooth, mobile phones. Good for short to medium distances and area coverage; penetrates obstacles depending on frequency.
• Microwave (Line-of-Sight): used for point-to-point links and satellite uplinks. High frequency, high bandwidth, requires clear line-of-sight.
• Infrared: short-range, line-of-sight (e.g., TV remotes, some local links). Limited range and blocked by obstacles.
• Satellite: uses microwave frequencies to communicate via space satellites; useful for wide-area coverage but higher latency.

Key Physical Characteristics

• Bandwidth: frequency range the medium can carry — determines possible data rate.
• Attenuation: loss of signal strength with distance; expressed in dB/km.
• Noise & Interference: external or internal signals that degrade signal quality (EMI, crosstalk).
• Latency: propagation delay depending on medium and distance (speed of light in medium).
• Cost & Installation: material and maintenance costs, complexity of installation.
• Security: wired media are generally harder to tap than wireless; fiber is most secure.

How to choose a medium

Selection depends on required data rate (bandwidth), distance, environment (EMI presence, physical obstacles), budget and desired security. For example, use UTP for typical office LANs, fiber for backbone/ISP links and long-haul/high-bandwidth needs, and wireless for mobility and last-mile access.

Common Connectors and Standards

• UTP: RJ-45 (Ethernet standards: Cat5e, Cat6, Cat6a)
• Coaxial: BNC or F-type (cable TV)
• Fiber: SC, ST, LC connectors; standards like 100BASE-FX, Gigabit Ethernet over fiber
• Wireless: IEEE 802.11 (Wi-Fi), Bluetooth (IEEE 802.15), cellular standards (3G/4G/5G)

Understanding transmission media helps in designing networks that meet performance, reliability and cost requirements.

Modes of Data Transmission

Data transmission describes how digital information travels between devices. Two commonly taught classifications are by direction (simplex, half‑duplex, full‑duplex) and by physical wiring/timing (serial vs parallel). Each mode has specific behaviour, advantages and typical uses.

1. Directional Modes

• Simplex: Communication in one direction only. Sender → Receiver. Receiver cannot send data back on the same channel. Advantages: simple and inexpensive. Disadvantages: not interactive.
  • Examples: TV broadcast, keyboard → CPU (one‑way).
• Half‑duplex: Both ends can transmit, but not at the same time. Communication alternates directions on the same channel. Useful where two‑way communication is needed but simultaneous talking is not required.
  • Examples: Walkie‑talkies, CB radios, old Ethernet hubs.
• Full‑duplex: Both ends can transmit simultaneously on the same channel (or on separate subchannels). Provides concurrent two‑way communication and higher effective throughput.
  • Examples: Telephone calls, modern Ethernet (switches), many Internet connections.

2. Serial vs Parallel Transmission

• Serial transmission: Bits are sent sequentially over a single wire or pair. Simpler wiring, lower cost, suitable for long distances and high speeds (modern high‑speed links are serial).
• Parallel transmission: Several bits are sent simultaneously over multiple wires (e.g., an 8‑bit data bus uses 8 lines). Higher data transfer per clock cycle but suffers from timing skew and is practical only for short distances (inside computers or short cables).
• Examples: Old printer parallel ports (parallel); USB, SATA, Gigabit Ethernet, PCIe (serial).

3. Timing: Synchronous vs Asynchronous (brief)

Synchronous transmission requires a shared clock or timing so bits are sent in a continuous stream (used in many serial links). Asynchronous sends data in frames/characters with start and stop bits; useful for intermittent character‑based links (e.g., RS‑232 serial ports).

Key tradeoffs

• Simplex: simplest but one‑way only.
• Half‑duplex: two‑way but contention for channel time; lower effective throughput than full‑duplex.
• Full‑duplex: highest usability; requires either separate channels/frequencies or echo cancellation.
• Serial vs Parallel: serial = fewer wires, longer distance, high clock rates; parallel = more wires, higher per‑cycle throughput locally, but timing/skew limits range.

Understanding modes of transmission helps choose appropriate hardware and protocols for a network or device interface.

What are Network Devices?
Network devices are hardware components that connect computers and other devices to form a computer network. They forward, filter, amplify or translate data so that devices can communicate reliably and efficiently.

Common network devices and their roles (with OSI-layer mapping):

• Network Interface Card (NIC) — interface between a host and the physical network. (OSI: Physical + Data Link). Provides MAC address and converts between host bus and network signals.
• Repeater — regenerates and amplifies signals to extend physical reach. (OSI: Physical).
• Hub — multiport repeater that broadcasts incoming frames to all ports. Simple and inexpensive but not intelligent. (OSI: Physical).
• Bridge — connects two LAN segments and filters traffic by MAC addresses to reduce collisions. (OSI: Data Link).
• Switch — multiport bridge that forwards frames only to the destination port using a MAC table; reduces collisions and supports full-duplex. (OSI: Data Link).
• Router — forwards packets between different networks using IP addresses and routing tables; chooses best path. (OSI: Network).
• Gateway — translates between different protocols or architectures (e.g., mail gateway, protocol gateway). Can operate at multiple layers.
• Modem — modulates digital signals to analog for transmission over phone lines (and demodulates on receive). Used by ISPs to connect homes. (Physical).
• Wireless Access Point (AP) — provides wireless connectivity (Wi‑Fi) to a wired network; may include bridging/switching features. (Physical + Data Link).
• Firewall — enforces security policies by filtering traffic (packet filtering, stateful inspection, application layer). (Typically Network/Transport/Application).
• Proxy Server — intermediates client requests to external servers for caching, content filtering or anonymity. (Application).
• Load Balancer — distributes incoming network/application traffic across multiple servers for high availability and performance. (Network/Application).

Key differences (short):

• Hub vs Switch: Hubs broadcast; switches forward to specific ports and maintain MAC tables.
• Switch vs Router: Switches operate in a LAN using MAC addresses; routers connect different networks using IP routing.
• Modem vs Router: Modem converts between analog and digital; router creates and manages a local network (often including NAT, DHCP).

Why devices matter: Proper selection affects bandwidth, latency, security and scalability. For example, replacing a hub with a switch reduces collisions and increases effective throughput; adding a router enables multiple LANs to communicate and reach the Internet.

Performance considerations: throughput, latency (delays), packet loss, and security features (firewalling, filtering) influence how devices are chosen and configured.

Overview
Network models are abstract frameworks that describe how data is transmitted, routed and received in a computer network. The two main reference models studied in Class 11 are the OSI reference model (7 layers) and the TCP/IP model (4 layers). Models standardize functions, enable interoperability, and separate concerns so designers can build and troubleshoot networks more easily.

OSI Reference Model (7 layers)

• 7. Application: Interface for end-user applications. Protocols: HTTP, FTP, SMTP, DNS. (Provides network services to apps.)
• 6. Presentation: Data representation, encryption, compression. Examples: SSL/TLS, JPEG, MPEG.
• 5. Session: Establishes, manages and terminates sessions (dialogs) between applications. Examples: RPC, NetBIOS.
• 4. Transport: End-to-end communication, reliability, flow and error control. Protocols: TCP (reliable), UDP (unreliable but fast). Concepts: ports, segmentation.
• 3. Network: Logical addressing and routing across networks. Protocols: IP, ICMP, OSPF. Concepts: IP addressing, routing, packet forwarding.
• 2. Data Link: Node-to-node data transfer on the same physical link; frame formation, MAC addressing, error detection. Protocols/standards: Ethernet (IEEE 802.3), PPP, ARP.
• 1. Physical: Physical medium and hardware (cables, fiber, wireless), bit-level transmission, voltages, connectors, repeaters, hubs.

TCP/IP Model (4 layers)

• Application layer: Combines OSI's Application, Presentation and Session. (HTTP, FTP, SMTP, DNS)
• Transport layer: TCP, UDP — provides end-to-end communication, ports, reliability.
• Internet layer: Equivalent to OSI Network layer. IP, ICMP — logical addressing (IP) and routing.
• Network Access (Link) layer: Combines OSI Data Link + Physical. Ethernet, Wi‑Fi, PPP.

Key concepts

• Encapsulation: At each layer data is wrapped with layer-specific headers (and sometimes trailers). Example: Application data -> TCP segment -> IP packet -> Ethernet frame -> bits on wire.
• Addressing: Physical (MAC) addresses are used on a link; logical (IP) addresses are used for routing across networks. Transport uses ports (socket = IP:port).
• Segmentation and reassembly: Large messages are split into segments/packets at transport/network layers and reassembled at receiver.
• Routing: Determining path from source to destination using routing protocols (OSPF, BGP) at Network/Internet layer.
• Services vs. Protocols: A service is what a layer offers to the layer above; a protocol is the set of rules two peers at the same layer use to communicate.

Why models matter (CBSE context)
They provide a common language for explaining how applications, transport, routing and physical transmission cooperate. When you troubleshoot, you map problems to layers (e.g., "can't browse" -> application or transport; "can't ping" -> network; "no link" -> data link/physical).

Definition: A protocol is a set of rules that governs how devices communicate (how data is formatted, transmitted, received and interpreted). A standard is a published specification, often created by a standards body, that formalizes protocols and ensures interoperability between products and vendors.

Core aspects of a protocol:

• Syntax – structure/format of data (packet formats, headers).
• Semantics – meaning of each field and control information (what actions to take on receipt).
• Timing – speed and sequencing (when to send, timeouts, retries).

Protocol vs Standard:

• Protocol = rules for communication (e.g., how to do a three-way handshake).
• Standard = widely accepted, documented specification usually set by a body (e.g., IEEE 802.11 for Wi‑Fi).
• A protocol can be part of a standard; a standard may define several protocols or profile existing ones.

Layered models: Protocols are normally organized in layers so each layer performs a distinct role. Two common models:

• OSI model (7 layers): Physical, Data Link, Network, Transport, Session, Presentation, Application. Each layer has its own protocols (e.g., Ethernet at Data Link, IP at Network, TCP at Transport).
• TCP/IP model (4 layers): Link, Internet, Transport, Application — the practical model used on the Internet.

Examples of widely used protocols and standards (mapped roughly to layers):

• Application: HTTP/HTTPS (web), SMTP/IMAP/POP3 (email), FTP/SFTP (file transfer), DNS (name resolution).
• Transport: TCP (reliable, connection‑oriented), UDP (unreliable, connection‑less).
• Network: IP (addressing & routing).
• Data Link & Physical: Ethernet (IEEE 802.3), Wi‑Fi (IEEE 802.11), Bluetooth.
• Security: SSL/TLS (secure transport), IPSec (network security).

How protocols work — simple examples:

• TCP three‑way handshake: Client sends SYN → Server replies SYN‑ACK → Client sends ACK. This establishes a reliable connection before data transfer.
• HTTP request/response: Browser (client) sends an HTTP GET request → Server responds with status and content → Client renders page. Over HTTPS the messages are encrypted with TLS.
• ARP (Address Resolution Protocol): Maps an IP address to a MAC address on a local network using request/reply broadcasts.

Why protocols & standards matter:

• Interoperability — devices from different manufacturers can work together.
• Compatibility & portability — software and services run across networks.
• Reliability & robustness — well‑tested behaviors (retransmission, error detection).
• Security — standardized methods to authenticate and encrypt traffic.
• Innovation & market growth — standards create common platforms for new services.

Standardization bodies: ISO, IEEE, IETF (Internet Engineering Task Force), ITU, W3C — they publish and maintain standards and RFCs used worldwide.

Summary: Protocols are the operational rules for communication; standards are formal, agreed specifications that adopt and document those rules so systems interoperate. Understanding protocols and standards is essential to design, troubleshoot and use networks effectively.

What is an IP address?
An IP (Internet Protocol) address uniquely identifies a device on an IP network. In IPv4, an IP address is a 32-bit number usually written in dotted-decimal form as four octets (e.g. 192.168.1.10).

Binary structure
Each IPv4 address = 32 bits = 4 octets of 8 bits. Example: 192.168.1.10 = 11000000.10101000.00000001.00001010.

Network and Host portions
An IP address has two logical parts: the network portion (identifies the network) and the host portion (identifies the device on that network). Which bits belong to each portion is defined by the subnet mask or prefix length.

Subnet mask and CIDR
A subnet mask is a 32-bit number with contiguous 1s starting from the left that marks the network bits (e.g. 255.255.255.0). CIDR notation expresses the mask as a prefix length: /24 means 24 network bits (255.255.255.0).

Network address and broadcast address
- Network address: all host bits = 0 (found by bitwise AND of IP and mask).
- Broadcast address: all host bits = 1 (network OR inverted mask).
First usable host is network+1; last usable host is broadcast-1 (except some special cases).

Classful addressing (basic historical idea)
Originally IPv4 addresses were grouped in classes A, B, C (A: /8, B: /16, C: /24) for large, medium and small networks. Modern networks use classless addressing (CIDR) which allows flexible prefix lengths.

Subnetting (why and how)
Subnetting divides a large network into smaller logical networks (subnets). This reduces broadcast domain size, organizes hosts by function/location, and improves security and routing. Subnetting is done by borrowing bits from the host portion to create additional network bits.

Basic steps to subnet
1. Start with network and its prefix (for example 192.168.1.0/24).
2. Decide how many subnets (or how many hosts per subnet) you need.
3. Determine how many bits to borrow from host part: borrowed_bits = smallest s such that 2^s >= required subnets.
4. New prefix = original_prefix + borrowed_bits. Calculate new subnet mask and ranges.
5. For each subnet compute network address (IP & mask), broadcast (network | ~mask), and usable host range.

Important rules
- Number of addresses in a subnet = 2^(host_bits).
- Usable hosts per subnet (typical) = 2^(host_bits) - 2 (subtract network and broadcast).
- Number of subnets created by borrowing s bits = 2^s.

Bitwise operations used
Network = IP AND mask. Broadcast = Network OR (invert mask).

Summary
IP addressing and subnetting let you assign unique addresses, group devices into networks, and control traffic. Practice converting between binary and dotted-decimal, computing network/broadcast addresses, and splitting networks into subnets using the steps above.

Overview

The Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) are two fundamental network services that make Internet use convenient. DNS translates human-friendly domain names into IP addresses that computers use. DHCP automatically assigns IP configuration (IP address, subnet mask, gateway, DNS servers) to hosts on a network, avoiding manual setup.

Domain Name System (DNS)

Purpose: Convert domain names (eg. www.example.com) into IP addresses (eg. 93.184.216.34) so applications and routers can locate services on the Internet.

Hierarchy and Components:

• Root level — represented by a dot (.) and served by root name servers.
• TLD (Top Level Domain) — examples: .com, .org, .in.
• Authoritative name servers — store DNS records for specific domains.
• Resolver (DNS client) — usually part of your OS/router; it sends queries and caches answers.
• Zones — portions of the DNS namespace managed by an authoritative server.

Common DNS record types:

• A — IPv4 address for a hostname.
• AAAA — IPv6 address.
• CNAME — canonical name (alias) pointing to another name.
• MX — mail exchange server for email routing.
• NS — nameserver record for a zone.
• PTR — reverse DNS (IP to name).

Resolution process (simplified, example: client wants www.example.com):

1. Client asks its local resolver (often OS or router cache).
2. If not cached, the resolver performs a recursive query to a DNS server. The server may query root servers, then TLD servers (for .com), then the authoritative server for example.com.
3. Authoritative server returns the A record (IP address).
4. Resolver caches the answer (for the time specified by TTL) and returns the IP to the client.

Query types: recursive (resolver asks server to return final answer) vs iterative (server returns best referral it knows; client follows referrals).

Caching: DNS responses have a TTL (time to live) value. Caching improves speed but may delay propagation of DNS changes.

Security note: DNS is susceptible to spoofing and cache poisoning. DNSSEC adds digital signatures to DNS records to provide data integrity.

Dynamic Host Configuration Protocol (DHCP)

Purpose: Automatically provide IP configuration to hosts joining a network so users don’t configure addresses manually.

Components:

• DHCP server — holds a pool of IP addresses and configuration parameters.
• DHCP client — requests configuration when it joins a network.
• DHCP relay/agent — forwards DHCP packets between clients and servers across different subnets.

Address allocation methods:

• Manual/Static — administrator assigns a permanent IP to the device (not typical DHCP behavior).
• Automatic — DHCP assigns a fixed IP from its pool permanently to a client.
• Dynamic — DHCP leases an IP for a limited time; addresses can be reused after lease expiry (most common).

DHCP process (DORA) — typical message sequence when a client joins a network:

• Discover — client broadcasts to find DHCP servers.
• Offer — server offers an IP address and configuration.
• Request — client requests the offered address (may pick one if multiple offers).
• Ack — server acknowledges and finalizes the lease; client configures its interface.

Other messages: NAK (negative acknowledgement), RELEASE (client gives up lease), INFORM (client has IP but asks for other options).

Leases and renewal: A DHCP lease has a lease time. The client will try to renew at a fraction of the lease (commonly T1 = 0.5 * lease). If renewal fails, at T2 (commonly 0.875 * lease) it begins rebinding with any server. If lease expires, client must stop using the address.

Common configuration options provided by DHCP: IP address, subnet mask, default gateway, DNS servers, lease time, domain name.

Practical interplay

A typical home setup: your ISP or home router runs a DHCP server that gives your laptop/phone an IP and DNS server addresses. When you type a website, your system uses the provided DNS servers to resolve the domain (DNS) and then uses the IP address to connect.

Key benefits

• DNS: human-friendly naming, distributed management, caching for speed.
• DHCP: centralized, automated IP management, reduces configuration errors.

Limitations & security

• DNS: cached stale records, vulnerability to spoofing (use DNSSEC and secure resolvers).
• DHCP: rogue DHCP servers can supply wrong configuration (use network controls, DHCP snooping).

Overview

Packet switching and circuit switching are two fundamental techniques for sending data over a communication network.

Circuit Switching

• Definition: A dedicated communication path (circuit) is established between sender and receiver for the duration of the session. Resources (bandwidth) along that path are reserved exclusively.
• How it works (steps): call setup (reserve path) → data transfer over the reserved path → teardown (release resources).
• Characteristics: constant bandwidth per call, fixed delay once circuit is set up, blocking may occur if no free circuit available.
• Examples: traditional telephone (PSTN), dedicated leased lines.

Packet Switching

• Definition: Data is broken into packets. Each packet is routed independently through the network; packets from different sources share the same physical links.
• How it works (steps): segmentation → attach header (address, sequence) → routing & queuing at intermediate nodes → reassembly at destination.
• Characteristics: efficient bandwidth sharing, variable delay (queuing), packets may take different routes and arrive out of order, better scalability and robustness.
• Examples: the Internet (IP), LANs, most modern data networks.

Direct Comparison (key points)

• Resource allocation: circuit switching reserves resources; packet switching shares resources dynamically.
• Delay: circuit switching: fixed (after setup) and typically low jitter; packet switching: variable delay and jitter (depends on congestion).
• Setup time: circuit: call setup required before data; packet: no setup—data sent immediately as packets.
• Efficiency: circuit: inefficient when channel idle; packet: efficient for bursty traffic because link is shared.
• Reliability & Robustness: circuit: single reserved path—failure disrupts call; packet: alternate routes possible—more resilient.
• Scalability: packet switching scales better to many users and varied traffic.

Advantages & Disadvantages (brief)

• Circuit switching advantages: predictable performance, low jitter, simple end-to-end behavior.
• Circuit switching disadvantages: poor resource utilization, blocking under high demand, less flexible.
• Packet switching advantages: high utilization, flexible routing, supports bursty traffic and many applications.
• Packet switching disadvantages: variable delays, packet loss under congestion, need for buffering and reordering.

When each is used

• Use circuit switching for applications needing continuous, steady bandwidth with low jitter (traditional voice circuits).
• Use packet switching for data, web, email, most modern voice (VoIP) and multimedia (with QoS mechanisms).

Summary: Circuit switching reserves a continuous path (good for predictable, steady streams), while packet switching divides data into packets that share network resources (good for efficiency and bursty traffic).

What are Network Performance Metrics?

Network performance metrics are measurable quantities that describe how well a network carries data. They help evaluate speed, quality, reliability and user experience. Network engineers and applications use these metrics to design, troubleshoot and optimise networks.

Main metrics (with short definitions)

• Bandwidth: The maximum data rate a link can carry, usually in bits per second (bps). This is a capacity figure (theoretical or advertised).
• Throughput: The actual rate of successful data delivery over the network (bps). Throughput ≤ bandwidth.
• Goodput: The rate of useful application-level data delivered (excludes protocol overhead and retransmissions).
• Latency (Delay): Time taken for a single packet to travel from sender to receiver. It has subcomponents: propagation, transmission, processing and queuing delays.
• Round-Trip Time (RTT): Time for a signal to go from sender to receiver and back.
• Jitter: Variation in packet delay (important for real-time apps like VoIP and gaming).
• Packet loss: Fraction of packets that never arrive (or are discarded), expressed as a rate or percentage.
• Utilization: How much of the available bandwidth is being used (often as a percentage).
• Availability and Reliability: Availability = fraction of time the service is up. Reliability relates to error rates and Mean Time Between Failures (MTBF).

Why they matter

• Throughput and bandwidth determine how fast files download and how smooth video plays.
• Latency and jitter affect interactivity: low latency is essential for online gaming and real-time communication.
• Packet loss and errors reduce quality and cause retransmissions, lowering goodput.

Typical values and intuition

• High bandwidth + low latency = good for large file transfers and interactive apps.
• High bandwidth but high packet loss → poor user experience because retransmissions reduce effective throughput.
• Low jitter is vital for voice/video conferencing even if throughput is moderate.

Network Security Basics covers principles and practices that protect data and resources as they move across networks. The primary goals are the CIA triad: confidentiality (preventing unauthorized data access), integrity (ensuring data is not altered without authorization), and availability (ensuring services and data are accessible when needed). Additional goals include authentication (verifying identities), authorization (granting correct privileges), and non-repudiation (preventing denial of actions).

Common threats and attacks:

• Passive attacks: eavesdropping or traffic analysis (attacker listens but does not alter data).
• Active attacks: modification, replay, impersonation, or Denial of Service (DoS).
• Malware: viruses, worms, trojans that infect hosts and spread through networks.
• Man-in-the-Middle (MitM): attacker intercepts and possibly alters communication between parties.
• Phishing and social engineering: tricking users into revealing credentials or downloading malware.

Key technical controls and concepts:

• Encryption: transforms plaintext into ciphertext so only authorized parties can read it. Two main types: symmetric (same key for encrypt/decrypt) and asymmetric/public-key (different keys for encrypt and decrypt).
• Hashing: one-way functions producing fixed-size digests used for integrity checks (e.g., SHA family).
• Digital signatures: use asymmetric cryptography to provide authentication and non-repudiation.
• Secure protocols: TLS/SSL (HTTPS) for secure web traffic, SSH for secure shell access, IPsec for secure IP-layer communication.
• Firewalls: filter traffic between networks based on rules (packet-filtering, stateful, application-level).
• VPNs: create encrypted tunnels over untrusted networks (e.g., public Wi‑Fi) to protect confidentiality and integrity.
• Intrusion Detection/Prevention Systems (IDS/IPS): monitor network traffic for suspicious patterns and alert/block attacks.
• Access control and authentication: passwords, multi-factor authentication (MFA), role-based access control (RBAC).
• Patch management and endpoint protection: keep systems updated, use antivirus/anti-malware tools.

Best practices for secure networks:

• Use strong, unique passwords and enable multi-factor authentication.
• Prefer HTTPS and up-to-date TLS versions for web traffic.
• Segment networks (separate guest, user, and server networks) and apply least-privilege access.
• Regularly update and patch systems and applications.
• Backup critical data and test restoration procedures.
• Educate users about phishing and safe behavior online.

Overview
Wireless networking is the transmission of data between devices using electromagnetic waves instead of physical cables. It enables mobility, easy deployment, and connectivity in locations where cabling is impractical. Wireless networks follow the same layered principles as wired networks but use radio, infrared, or satellite links for the physical layer.

Major types of wireless networks

• PAN (Personal Area Network) – very short range (a few metres). Examples: Bluetooth, NFC.
• WLAN (Wireless Local Area Network) – covers homes, offices. Example: Wi‑Fi (IEEE 802.11 family).
• WMAN (Wireless Metropolitan Area Network) – covers a city or campus. Example: WiMAX.
• WWAN (Wireless Wide Area Network) – cellular networks covering large geographic areas (2G/3G/4G/5G) and satellite links.

Common wireless technologies

• Wi‑Fi (IEEE 802.11) – used for LAN access. Variants: 802.11b/g/n (2.4 GHz), 802.11a/ac/ax (5 GHz and 6 GHz for newer Wi‑Fi 6E/7). Wi‑Fi uses access points (APs), SSIDs, channels and supports infrastructure and ad‑hoc modes.
• Bluetooth – short‑range (≈1–100 m depending on class), low power, used for peripherals and audio (profiles like A2DP, HFP). Operates in 2.4 GHz ISM band with frequency hopping.
• Infrared (IR) – line‑of‑sight, short range (remote controls, IR data transfer).
• Cellular (2G–5G) – mobile voice/data. 4G LTE provides high data rates; 5G improves throughput, latency and supports massive IoT.
• WiMAX – broadband wireless for metropolitan coverage (less common now due to LTE/5G).
• Zigbee / Thread – low‑power mesh protocols for IoT and home automation (IEEE 802.15.4 family).
• NFC (Near Field Communication) – extremely short range (a few cm) for contactless payments and pairing.
• Satellite – very long range global coverage (geostationary, MEO, LEO systems), used where terrestrial networks are unavailable.

Operating concepts

• Modes: Infrastructure (clients + AP) and Ad‑hoc (peer‑to‑peer). Mesh networks use multiple nodes to forward traffic.
• Channels & Bands: Wireless uses regulated frequency bands (e.g., 2.4 GHz, 5 GHz). Channels are sub‑divisions; overlapping channels cause interference.
• MIMO & Beamforming: Multiple antennas improve throughput and reliability by spatial multiplexing and directing energy.
• MAC layer: Wi‑Fi uses CSMA/CA (carrier sense multiple access with collision avoidance). Bluetooth uses time/frequency hopping to reduce collisions.

Performance factors

• Frequency: Higher frequency → shorter wavelength → generally higher data rate but lower propagation/range.
• Bandwidth: Wider channel bandwidth → higher possible data rates.
• SNR (Signal‑to‑Noise Ratio): Higher SNR → higher reliable throughput.
• Path loss & attenuation: Signals weaken with distance and obstacles (walls, foliage).
• Interference: From other wireless devices, microwave ovens, overlapping Wi‑Fi networks.

Security
Wireless links are more exposed to eavesdropping and unauthorized access. Common mechanisms: SSID hiding (obscurity only), MAC filtering (easily spoofed), and real encryption/authentication: WEP (obsolete and insecure), WPA/WPA2 (WPA2 with AES is standard), WPA3 (stronger). For cellular, SIM authentication and tower‑based encryption are used. VPNs add end‑to‑end protection.

Practical considerations & best practices

• Place APs centrally and elevated to maximize coverage; avoid metal/large obstructions.
• Choose less crowded channels (use Wi‑Fi scanner tools).
• Use WPA2/WPA3 with strong passphrases; update firmware regularly.
• Use guest networks for visitor access to isolate devices.
• For critical links, consider directional antennas or wired backups to improve reliability.

Mapping to syllabus concepts
Wireless networking illustrates physical and data‑link layer differences from wired networks (propagation, spectrum, medium access). It also shows real‑world tradeoffs: mobility vs. security, convenience vs. interference.

Introduction
The Internet is a global system of interconnected computer networks that use a common set of protocols (TCP/IP) to communicate. It provides infrastructure and services that allow devices worldwide to exchange data. The World Wide Web (WWW or Web) is an information service that runs on top of the Internet and uses HTTP/HTTPS to access hyperlinked documents (web pages) identified by URLs.

Key components

• Hosts/Clients: PCs, smartphones, servers that generate and consume data.
• Routers and switches: Forward packets between networks.
• Servers: Web, mail, DNS, FTP servers that provide services.
• ISPs: Internet Service Providers connect users to the global Internet.
• Protocols: TCP/IP, HTTP/HTTPS, FTP, SMTP, POP3, IMAP, DNS, etc.

How the Internet works (brief)
Data is split into packets and routed across many intermediate devices using packet-switching. Each packet contains source/destination IP addresses. The TCP protocol (when used) provides reliable, ordered delivery; IP handles addressing and routing.

Addresses and names
IP address: Numeric address (IPv4/IPv6) assigned to each device.
Domain Name System (DNS): Translates human-readable domain names (example.com) into IP addresses. A URL (Uniform Resource Locator) identifies a web resource and contains the protocol, domain, and resource path (for example, http://www.example.com/index.html).

World Wide Web
The Web uses HTTP (HyperText Transfer Protocol) or HTTPS (secure) to request and transfer web pages. A browser (client) sends an HTTP request to a web server; the server responds with an HTML page which the browser renders. Web pages can include images, scripts, stylesheets and hyperlinks to other pages.

Common Internet services & protocols

• HTTP/HTTPS: Web (port 80/443).
• DNS: Name resolution (port 53).
• SMTP/POP3/IMAP: Email send/receive.
• FTP/SFTP: File transfer.
• VoIP: Voice over IP (real-time communication).

Client–Server model vs Peer-to-Peer
Most Web services use a client–server model: a client (browser) requests resources from a server. In peer-to-peer (P2P), participants act as both clients and servers (example: file-sharing apps).

Security
HTTPS uses SSL/TLS to encrypt HTTP traffic, providing confidentiality and integrity. Firewalls, VPNs, and secure authentication protect networks and users.

Difference: Internet vs WWW (summary)

• Internet = global network of networks (infrastructure, hardware, protocols).
• WWW = collection of interlinked documents and resources accessed via HTTP over the Internet.

Example sequence: Browsing a website
1) Type URL in browser → 2) Browser asks DNS for IP → 3) DNS returns IP → 4) Browser opens TCP connection to web server (TCP 3-way handshake) → 5) Browser sends HTTP GET request → 6) Server responds with HTML → 7) Browser requests additional resources (images, CSS, JS) → 8) Page renders.

Performance basics
Network performance depends on bandwidth (capacity), latency (delay), and packet loss. Techniques like caching, CDNs (Content Delivery Networks), compression, and optimized TCP settings improve user experience.

Educational relevance
Understanding the Internet and WWW helps students learn how online services work, basic web programming, digital citizenship, and safe use of online resources.

Overview

Network Applications and Services are software systems and protocols that run on top of computer networks to provide user-facing functionality (web, email, file transfer, voice/video, etc.). They operate primarily at the Application Layer of the TCP/IP model and rely on lower-layer services (transport, network, link) to move data between hosts.

Key Concepts

• Application vs Service: An application is end-user software (web browser, mail client). A service is a network-provided capability (DNS resolution, DHCP address allocation).
• Client–Server vs Peer-to-Peer (P2P): In client–server, clients request services from central servers (websites, email). In P2P, peers both consume and provide resources (file-sharing, some voice apps).
• Protocols: Define message formats and rules. Common application-layer protocols: HTTP/HTTPS, SMTP/POP3/IMAP, FTP/SFTP, DNS, DHCP, SSH, SIP/RTP for real-time media.
• Ports and Sockets: Applications use port numbers and sockets (IP address + port) to communicate—e.g., HTTP default port 80, HTTPS 443.

Major Network Applications & Services

• Web / HTTP/HTTPS: Hypertext Transfer Protocol for webpages; HTTPS adds TLS/SSL for encryption (critical for banking, e-commerce).
• Email: SMTP for sending, POP3/IMAP for retrieval; webmail uses HTTP(S).
• File Transfer: FTP/SFTP for direct transfers; cloud storage (Google Drive, Dropbox) uses HTTP(S) + APIs.
• Remote Access: SSH (secure shell) and RDP for remote command and desktop access.
• Directory / Name Services: DNS maps domain names to IP addresses; LDAP provides directory services.
• Addressing / Configuration: DHCP automatically assigns IP addresses and configuration to hosts.
• Real-time Communication: VoIP, video conferencing use SIP for signaling and RTP/RTCP for media with QoS considerations.
• Monitoring & Management: SNMP for network management, ICMP for diagnostics (ping, traceroute).
• Cloud & Web Services: SaaS, PaaS, IaaS models; RESTful APIs over HTTP are common for web services.

Performance Factors

• Bandwidth: Maximum data rate of a link (bits per second).
• Latency/Delay: Time taken for a packet to travel (propagation + transmission + queuing + processing).
• Jitter: Variation in packet arrival times—important for audio/video.
• Throughput: Actual useful data rate achieved, often lower than raw bandwidth.
• Quality of Service (QoS): Mechanisms to prioritize traffic (voice over data) using queuing, traffic shaping, DiffServ.

Security & Reliability

• Confidentiality & Integrity: TLS/SSL for encryption; message signing where needed.
• Authentication & Authorization: Passwords, certificates, tokens (OAuth) to control access.
• Redundancy & Fault Tolerance: Load balancers, replication, CDN (Content Delivery Network) to improve availability and performance.

How an Application Request Flows (Example: Web Page Load)

1. User types URL or clicks link → browser checks local cache and DNS resolver.
2. If needed, browser sends DNS lookup to resolve domain → receives IP address.
3. Browser opens TCP connection to server IP:port (three-way handshake) → optional TLS handshake for HTTPS.
4. Browser sends HTTP request; server responds with HTML, assets (CSS, JS, images) which may be fetched in parallel.
5. Browser renders page; additional AJAX/REST calls may continue.

This flow shows interplay of application protocols (HTTP, DNS), transport (TCP/UDP), and network services (DNS, CDN, TLS).

Overview: Network troubleshooting is a systematic process to find and fix problems that prevent devices or services from communicating correctly. It combines logical steps (identify, isolate, fix, verify) with a set of common tools and measurements to detect faults at different OSI layers.

Troubleshooting methodology (step-by-step):

1. Identify — Understand the symptoms: who is affected, when it started, scope (one host, VLAN, whole site), and recent changes.
2. Gather information — Collect logs, run basic commands (ping, ipconfig/ifconfig), ask users, check device LEDs and cables.
3. Isolate — Determine the failing layer (physical, data link, network, transport, application) and whether the fault is local or remote.
4. Diagnose & test — Use targeted tools (traceroute, nslookup, netstat, Wireshark, iperf) to confirm the root cause.
5. Fix — Apply the corrective action (replace cable, correct IP/DNS settings, adjust MTU, restart service, update firewall rules).
6. Verify & document — Re-test, confirm normal operation, and record the issue and resolution for future reference.

OSI-layer based checks (concise):

• Layer 1 (Physical): Check cables, connectors, link lights, switch port LEDs, signal quality, cable tester results.
• Layer 2 (Data Link): Verify MAC addresses, ARP table (arp -a), VLAN membership, switch port configuration and collisions/duplex mismatches.
• Layer 3 (Network): Check IP address, subnet mask, default gateway (ipconfig/ifconfig), routing table (route print / ip route), ping and traceroute.
• Layer 4 (Transport): Verify TCP/UDP ports, connection states (netstat), retransmissions, and firewall/NAT rules.
• Layer 7 (Application): Test DNS (nslookup/dig), HTTP(S) (curl/browser), email, and application logs.

Common tools & how they help:

• ping — Tests basic reachability and round-trip time (RTT). Good first test.
• traceroute / tracert — Shows path and per-hop latency to identify where delays/blackholes occur.
• ipconfig / ifconfig — Displays IP configuration, useful to spot wrong IP/gateway/DHCP problems.
• nslookup / dig — Verifies DNS resolution and records returned by the DNS server.
• netstat — Lists active connections, listening ports and protocol states.
• arp — Shows IP-to-MAC mappings; helps detect ARP conflicts or incorrect entries.
• wireshark / tcpdump — Packet capture and inspection to analyze packet flows, retransmissions, and protocol errors.
• iperf / speedtest — Measures throughput between two endpoints to test bandwidth.
• nmap — Port scanning to check which services/ports are open on a host.
• ethtool / mii-tool — Shows NIC link speed/duplex and helps detect mismatches.

Common problems & quick checks:

• No connectivity: check link LEDs, cabling, ipconfig, default gateway, and ping the gateway.
• Slow internet: ping a public IP and a domain name to separate DNS vs network slowness; run speedtest or iperf to check bandwidth.
• DNS failures: nslookup/dig to query specific DNS servers; try numeric IP to bypass DNS.
• Intermittent drops: capture packets with Wireshark to find retransmissions or ARP storms; test cable for faults.
• IP conflict: check arp/arp -a and event logs; change IP or enable DHCP reservation.

Best practices: Always test from both ends when possible, document steps and results, revert recent changes as a troubleshooting step, and isolate variables (use a known-good cable/device).

Practical/Hands-on Topics in Class 11 Computer Science (Computer Networks) teach students how networks are built, configured, tested and analysed. The practical focus is on basic network setup, addressing, simple services (DHCP, DNS, HTTP), troubleshooting using command-line tools and packet analysis. These labs reinforce theory by giving experience with real devices or simulators (Packet Tracer, GNS3) and tools (Wireshark).

Typical practical activities include:

• Setting up a small LAN: connecting PCs, configuring switches or hubs, assigning IP addresses (static and via DHCP) and verifying connectivity.
• Using command-line networking tools: ipconfig/ifconfig, ping, tracert/traceroute, nslookup/dig, netstat, arp. Interpreting their outputs for troubleshooting.
• Subnetting and CIDR practice: calculating network, broadcast addresses and valid host ranges; applying masks.
• Packet capture and analysis with Wireshark: capturing traffic, filtering by protocol, inspecting TCP handshake, HTTP requests and DNS lookups.
• Setting up simple services: a basic HTTP/FTP server to demonstrate client-server interaction, and observing traffic with Wireshark.
• Using network simulators: creating topologies, configuring routers/switches, simulating routing and NAT, and testing connectivity.

Good lab practice includes documenting topology diagrams, recording IP addressing schemes, following safety and security steps (isolating lab networks from the internet when required), and explaining observations (why ping failed, where packet loss occurred, etc.).