Welcome to Druvexaa

In the context of the Simulator, the RAID Controller sits between the workstation and the disk array like an invisible traffic manager. Every file you save is split, copied, or mathematically protected before it ever touches a platter, and the operating system never sees any of it — it only sees one clean volume: /dev/md0.

How RAID Works (3 Core Ingredients)

Every RAID level, no matter how complex, is really just a mixture of three building blocks.

• 1. Striping: The controller chops a file into small chunks and spreads them across multiple disks so they can be written and read in parallel — pure speed, zero safety on its own.
• 2. Mirroring:
  • Every block is duplicated onto a second disk in real time.
  • If one disk dies, its exact twin keeps serving data instantly.
  • Costs 50% of total capacity to buy that safety.
• 3. Parity: Instead of a full copy, the controller's XOR engine computes a small mathematical "checksum" block. If a disk is lost, parity plus the survivors can mathematically rebuild the missing data.

RAID Flow — Where Data Goes

Detailed RAID Levels

2️⃣ RAID 1 — Mirroring (Safety)

Every block is written twice, to two separate disks. Reads are fast and a full disk failure causes zero data loss — but you only get 50% of your total purchased capacity to use.

3️⃣ RAID 5 — Striping + Distributed Parity

Data stripes across all disks like RAID 0, but one parity block per stripe is added and rotated evenly across disks. Survives any single disk failure with roughly (n−1)/n usable capacity — the classic balance of cost, speed, and safety used in file and web servers.

4️⃣ RAID 6 — Dual Parity (P + Q)

Identical to RAID 5, but with a second, independently computed parity block per stripe. This lets the array survive two simultaneous disk failures — critical for large arrays where rebuilds on huge modern drives can take days.

5️⃣ RAID 10 — Mirrored Stripes (1+0)

Disks are grouped into mirrored pairs, then data is striped across the pairs. It combines RAID 0's write speed with RAID 1's protection and has no parity math to slow it down — the go-to choice for busy databases. Only 50% capacity is usable, and losing both disks in the same mirror pair still means data loss.

Important Reminder

RAID protects against a disk failing — it is not a backup. It does nothing against accidental deletion, ransomware, fire, or theft. A real backup strategy still needs a separate, offline or off-site copy.

Modern Use Cases

• RAID 0: Video/photo editing scratch disks, game drives, caches.
• RAID 1: OS/boot drives, small business servers.
• RAID 5: File servers, NAS boxes, web/mail servers.
• RAID 6: Backup/archive servers, large-capacity surveillance storage.
• RAID 10: Database servers, VM datastores, high-transaction apps.

Conclusion

RAID turns a handful of ordinary disks into one resilient, high-performance volume by mixing striping, mirroring, and parity in different ratios. Choosing the right level is really just choosing which trade-off — speed, capacity, or fault tolerance — matters most for the job at hand.

In the context of the Simulator, the Hub represents the "digital town square" of early networking. When you send data through the Hub, you will see it flood to every device attached to it, regardless of the intended destination.

How a Network Hub Works (Layer 1 Connectivity)

Hubs operate purely at the Physical Layer (Layer 1) of the OSI model. They have no "brain" to understand addresses.

• 1. Multi-Port Repeater: The hub's only job is electrical. It takes a digital signal coming in on one wire and amplifies it to send out on all other wires.
• 2. The "Blind Broadcast":
  • The hub does not check who the data is for.
  • It does not read MAC addresses or IP addresses.
  • Every connected device must inspect the data to see if it belongs to them.
• 3. Shared Bandwidth: If a hub is rated for 100 Mbps, that speed is shared among ALL users. If 10 people try to download at once, they fight for that single pipe.

Detailed Hub Mechanics

2️⃣ Security Vulnerabilities

Since traffic is broadcast to everyone, a hacker plugged into Port 4 can see the "private" email sent from Port 1 to Port 2 using simple sniffing software. There is no privacy on a hub.

3️⃣ Half-Duplex Operation

Devices on a hub cannot send and receive at the same time (Half-Duplex). They must listen, wait for silence, and then speak.

Modern Use Cases

While obsolete for normal networks, Hubs are still useful for:

• Network Analysis: Easiest way to sniff traffic for debugging.
• Signal Repeater: Extending a cable run beyond 100 meters cheaply.

Conclusion

The Hub was the necessary stepping stone of the early internet. It taught us the importance of collision management and paved the way for the intelligent switching we rely on today.

In the simulator, a packet walks up to the firewall and you watch exactly how deeply each generation of firewall looks before it makes a decision. On the left is your workstation, in the middle the firewall appliance, and on the right the internet. Send a packet and see whether it is permitted, denied, or dropped.

How a Firewall Works (Trust-Boundary Enforcement)

A firewall sits at the boundary between a trusted network (your home or office) and an untrusted one (the internet). Every generation answers the same single question — how deeply does the device look before it decides?

• Depth of inspection trades against throughput: the deeper a firewall reads, the more work it does per packet.
• The taxonomy maps onto the OSI model — that mapping is what separates one firewall type from the next.

The Firewall Family (mapped to OSI)

• 1. Packet Filtering (L3–L4): Stateless. Reads only the IP and transport headers and matches the five-tuple (src/dst IP, src/dst port, protocol). Fast and cheap, but blind above Layer 4.
• 2. Stateful Inspection (L3–L4): Keeps a connection table keyed on the five-tuple plus TCP state. The first packet runs the full rule set; later packets take a fast hash-lookup path. Return traffic is allowed automatically.
• 3. Circuit-Level Gateway (L5): Validates the TCP three-way handshake, then relays bytes blindly between two connections. SOCKS is the classic example; internal addressing stays hidden.
• 4. Proxy / Application Firewall (L7): Terminates the client connection and opens a fresh one to the origin. No packet forwarding — full Layer 7 visibility for URL filtering, MIME checks, and antivirus scanning.
• 5. Next-Generation Firewall (L2–L7): Single-pass parallel inspection. Application identity (allow Teams, block Discord) replaces the port as the policy object; TLS inspection is mandatory.
• 6. Web Application Firewall (L7): An HTTP specialist that guards one website — method, URI, headers, cookies, and body — using rule sets like the OWASP Core Rule Set.

Detailed Firewall Mechanics

2️⃣ Stateful Memory & Its Cost

By tracking sequence numbers, a stateful firewall can drop out-of-window segments — but every tracked connection consumes memory, which makes the connection table itself a denial-of-service target (flood it with half-open sessions and it exhausts state).

3️⃣ Layer 7 & Virtual Patching

Because a proxy is an endpoint on both sides, it can normalise headers and scan payloads. A WAF adds virtual patching: it blocks exploitation of a known vulnerability at the edge while the app team ships a real fix — though an untuned WAF in blocking mode will break legitimate traffic.

Modern Use Cases (Defence in Depth)

No real network relies on a single firewall. Controls are layered so none is load-bearing:

• Scrubbing: absorbs volumetric floods upstream before they reach the stack.
• NGFW: enforces application and identity policy for the whole network.
• WAF: handles application-layer exploitation against published web services.
• Segmentation & zero trust: limit the blast radius after any one control fails.

Conclusion

Firewalls evolved by looking deeper and deeper into traffic — from headers, to connection state, to full application content. Understanding which control belongs at which point in the path is the real skill, and this simulation lets you see each one make its decision in 3D.

In the context of the Simulator, the Gateway represents the single "door" between two IP networks — Network A (192.168.1.0/24) and Network B (10.0.0.0/24). Every packet that needs to leave its home network must pass through this router first.

How a Default Gateway Works (Layer 3 Routing)

Gateways operate at the Network Layer (Layer 3) of the OSI model, using IP addresses and subnet masks to make forwarding decisions.

• 1. Subnet Comparison: Every device applies its subnet mask to both the source and destination IP to check if they share the same network ID.
• 2. Same Network → Direct Delivery:
  • If the network portions match, the switch delivers the frame directly.
  • The router is never involved — it doesn't even see the packet.
• 3. Different Network → Gateway Hop: If the networks differ, the packet is sent to the configured gateway IP, which then routes it toward the destination.

Detailed Gateway Mechanics

2️⃣ One Address, Every Destination

A device doesn't need to know the route to every network on the internet. It only needs the gateway's address — the router handles everything beyond that door, hop by hop.

3️⃣ Two-Way Traffic

The gateway isn't just an exit — replies from outside networks also pass back through it on their way to the original device.

Modern Use Cases

Understanding the gateway is essential for:

• Network Troubleshooting: The first setting to check when "local works, internet doesn't."
• Router Configuration: Setting up home and enterprise networks correctly.

Conclusion

The Default Gateway is the quiet backbone of internet connectivity — a single address that lets any device reach any other network on Earth.

In the context of the Simulator, you travel outward through four scales — a person, a building, a city, and finally the entire planet — watching the same idea (moving data from one device to another) played out at completely different distances and stakes.

The Four Scales — Where Data Goes

Detailed Network Scales

2️⃣ LAN — Local Area Network

A network inside one building or campus — an office, a school, or a home — owned by a single organisation. A central Layer-2 switch learns MAC addresses and forwards traffic only where it needs to go, while a Wi-Fi access point extends the same network wirelessly. Speeds run from 100 Mbps to 10 Gbps.

3️⃣ MAN — Metropolitan Area Network

Many LANs across one city, stitched together by an optical fibre ring buried under the roads — think bank branches syncing to headquarters. A ring topology gives every site two paths, so if a digger cuts the fibre on one side, traffic instantly wraps around the other way and self-heals in around 50 ms.

4️⃣ WAN — Wide Area Network

Networks of networks spanning countries and continents — the Internet is the largest WAN ever built. About 99% of intercontinental traffic rides submarine fibre cables along the ocean floor, with satellites covering the rest. Distance now costs real time: light itself needs roughly 100+ milliseconds to make a round trip across the planet.

Side-by-Side Comparison

• PAN: ≈10 m · 1–3 Mbps (Bluetooth) · owned by one person · earbuds, smartwatch, phone hotspot.
• LAN: ≈100 m–1 km · 100 Mbps–10 Gbps · owned by one organisation · office, home, school lab.
• MAN: 5–50 km · 10 Mbps–10 Gbps · owned by an ISP/city · bank branches, cable TV, city Wi-Fi.
• WAN: country → global · 100+ Gbps backbone, higher latency · leased across many providers · the Internet itself.

The Pattern to Remember

As networks grow larger, speed-per-rupee falls, latency rises, and ownership fragments across more parties. A PAN is private and near-instant; a WAN is shared infrastructure limited by the physics of distance. Memory hook: Pocket → Local building → Metro city → World.

Conclusion

PAN, LAN, MAN and WAN aren't different technologies so much as the same networking problem solved at four completely different distances — and understanding where each one's boundary lies is the first step to understanding how the whole Internet fits together.

In the context of the Simulator, TCP is explored across 11 full chapters — from encapsulation and header anatomy, to the 3-way handshake, sequence & acknowledgment numbers, error checking, flow control, congestion control, and the complete end-to-end journey of opening a website.

TCP's 5 Core Promises (Layer 4 Reliability)

TCP sits above the unreliable Network Layer and guarantees five things IP alone cannot.

• 1. Reliable Delivery: Lost data is detected via timers and duplicate ACKs, then automatically resent.
• 2. Ordered Delivery:
  • Every byte carries a Sequence Number.
  • The receiver reassembles data in the exact original order, even if segments arrive scrambled.
• 3. Error Checking: A 16-bit checksum fingerprints every segment; corrupted data is silently discarded and retransmitted.

Detailed TCP Mechanics

2️⃣ Flow Control (Protecting the Receiver)

The receiver advertises a Window Size showing free buffer space. If the window drops to 0, the sender pauses completely — sending only tiny probes — until the receiver's app catches up and reopens the window.

3️⃣ Congestion Control (Protecting the Network)

TCP grows its congestion window exponentially during Slow Start, then linearly during Congestion Avoidance — and halves it sharply on packet loss, producing the famous "sawtooth" graph shared by every TCP flow on the internet.

Modern Use Cases

TCP underlies nearly all reliable internet communication:

• Web Browsing: HTTPS (port 443) runs over TCP for guaranteed page delivery.
• File Transfer & Email: FTP, SMTP, and IMAP all rely on TCP's reliability guarantees.

Conclusion

TCP is the quiet workhorse behind almost every reliable connection on the internet — turning an unpredictable network into a dependable, ordered stream of data, one carefully numbered byte at a time.

In the context of the 3D Simulator you are using, the switch acts as the central traffic director. When you select a "Source" and a "Destination" in the simulator and click "Send Packet," you are visualizing the switch's core job: taking a data frame from one port and accurately delivering it to another.

How a Network Switch Works (The "Matter")

Switches operate primarily at Layer 2 (Data Link Layer) of the OSI model. Their efficiency comes from their ability to "learn" the network topology.

• 1. MAC Addressing: Every network interface card (NIC) has a unique identifier called a Media Access Control (MAC) address. In the Simulator, each device (e.g., PC A, Printer B) has a simulated MAC address.
• 2. The CAM Table (Content Addressable Memory): The "brain" of the switch.
  • Learning: When data enters a port, the switch records the Source MAC and Port Number.
  • Forwarding: Known destinations get Unicast (direct) traffic.
  • Flooding: Unknown destinations cause the data to be sent to all ports (except origin) until the device replies.
• 3. Collision Domains: Unlike a Hub where only one device talks at a time, a Switch makes every port its own collision domain. PC A can talk to PC B while PC C talks to PC D simultaneously.

Detailed Switch Operation Breakdown

2️⃣ Learning Phase (MAC Learning)

Whenever the switch receives a frame, it checks the source MAC and maps it to the incoming port. If the MAC is new, it adds it; otherwise, it refreshes the timer.

3️⃣ Forwarding Phase (Decision Making)

• 🚀 A. Unicast Forwarding: If destination MAC is known, send only to that port.
• 🚀 B. Flooding: If destination MAC is unknown, flood to all ports.
• 🚀 C. Filtering: If source and destination are on the same port, drop the frame.

4️⃣ 🔁 Aging MAC Table

Entries are removed after 5 minutes (default) if no traffic is seen, avoiding stale entries.

5️⃣ 📦 Switch Avoids Collisions

Communication is full duplex (send + receive same time). No collisions occur.

6️⃣ 🧠 Internal Working

Uses ASICs for wire-speed decisions. Methods include Store-and-Forward (checks errors) and Cut-Through (fastest).

Use Cases

• Small Office (SOHO): File sharing and printer access.
• Enterprise LANs: Using VLANs to separate Finance traffic from Guest Wi-Fi.
• Data Centers: High-performance Top-of-Rack switches handling 10Gbps+ traffic.
• IP Camera Surveillance (PoE): Powering cameras directly through the ethernet cable.

Conclusion

The network switch is the unsung hero of the modern internet. While routers get the credit for connecting us to the World Wide Web, switches do the heavy lifting of moving data around our local environments efficiently.

In your Mesh Topology Simulator, this is visually represented by the "cables" connecting the various nodes. The simulation demonstrates how data travels across these links and how the network reacts when a link is "broken."

Types of Mesh Topology

There are two main types of mesh topologies, both of which serve different needs in network architecture:

How It Works: Routing and Flooding

• Routing: Nodes use logic to find the shortest/fastest path. If a link breaks, the router calculates a new path.
• Flooding: Data is transmitted to all nodes to ensure delivery, though this increases traffic load.

Key Advantages

Disadvantages

• Complexity: Hard to manage due to the web of connections.
• Cost: High cabling and hardware costs.
• Power Consumption: Nodes acting as repeaters drain battery (in wireless/IoT).

Conclusion

Mesh topology remains the gold standard for networks where reliability is non-negotiable. While it comes with higher setup costs and configuration complexity, its ability to self-heal and maintain communication during partial failures makes it indispensable for critical infrastructure.

In your Simulator, the green "packets" traveling along the cables demonstrate the sequential nature of data transmission in this architecture.

Types of Ring Topology

Your simulator specifically handles two variations, which are critical distinctions in networking:

How It Works: Token Passing

The most unique mechanism of a ring network is Token Passing:

• The Token: A short message circulates around the ring constantly.
• Permission: A node can only send data if it possesses the token, preventing collisions entirely.
• Regeneration: Each node acts as a repeater, boosting the signal before passing it to the neighbor.

Key Advantages

Disadvantages

• Single Point of Failure: In a standard ring, one broken cable kills the whole network.
• Scalability: Adding a node usually requires shutting down the network.
• Latency: Data passes through every intermediate node, which is slower than direct connections.

Conclusion

Ring topology offers a disciplined approach to data transmission, eliminating the chaos of packet collisions. While traditional single rings are fragile, the Dual Ring architecture demonstrated in your simulator transforms it into a highly reliable system capable of surviving physical line breaks, a concept still vital in high-speed backbone networks like SONET.

The behavior of the network depends entirely on what that central box is—a detail your simulation explores in depth.

The Core Component: Hub vs. Switch

Your simulation distinguishes between two types of central devices, illustrating the evolution of network technology:

Key Advantages

Disadvantages

• Single Point of Failure: If the central Hub/Switch fails, the entire network goes down immediately.
• Cabling Costs: Every device needs a dedicated cable, which can be expensive compared to Bus or Ring topologies.

Conclusion

Star topology represents the standard for modern networking because it balances performance with ease of management. While it relies heavily on the health of the central device, the intelligence of that device (Switch vs. Hub) is what truly determines the network's efficiency and speed.

In your Simulator, you can observe how data packets travel bi-directionally along the cable, reaching every station simultaneously through a broadcast mechanism.

Core Components

The simulator highlights the critical infrastructure required for a functional bus network:

How Data is Received

The simulation demonstrates the "Listen and Compare" logic used by PCs:

• Broadcast: Data is sent to the whole line. Every PC "sees" the packet.
• Address Check: Each PC examines the packet header. If the destination address doesn't match its own, it discards the packet.
• Acceptance: Only the PC with the matching address accepts and processes the data.

Key Advantages

Disadvantages

• Single Point of Failure: If the backbone cable breaks, the entire network is split and becomes non-functional.
• Traffic Congestion: Heavy traffic or too many nodes can significantly slow down performance due to collisions.

Conclusion

Bus topology provides a foundational look at how shared-medium networks operate. While its physical use has declined in favor of Star topologies, its concepts of broadcasting and collision detection remain core to modern wireless and Ethernet communication protocols.