Welcome to the World of Networks!
Ever wondered how you can send a message from your phone in the UK and have it pop up on a friend’s screen in Australia a split second later? That is the magic of Networking. In this chapter, we are going to look at how computers "talk" to each other, the rules they must follow, and the physical ways they stay connected.
Don't worry if this seems a bit technical at first—we’ll break it down piece by piece. Think of a network like a conversation: for it to work, everyone needs to speak the same language and follow the same social rules!
1. Network Characteristics, Protocols, and Standards
A network is simply two or more computers connected together to share resources (like files or printers). But for this to work effectively, we need Protocols and Standards.
What is a Protocol?
A protocol is a set of rules that governs how data is transmitted across a network. Without protocols, a computer might send a bunch of 1s and 0s that the receiving computer doesn't understand.
Analogy: Think of a protocol like a "polite conversation." Rule 1: One person speaks at a time. Rule 2: You speak the same language. Rule 3: You say "hello" to start and "goodbye" to finish.
Why are Standards Important?
Standards are agreed-upon models or requirements that allow hardware and software from different manufacturers to work together. Because of standards, you can plug a Samsung phone into an Apple laptop or a Dell monitor, and they still "understand" each other.
Quick Review:
• Protocols = The rules for communication.
• Standards = The "universal" designs that ensure compatibility.
2. LANs and WANs
Not all networks are the same size. We generally categorize them by the area they cover.
LAN (Local Area Network)
A LAN covers a small geographical area, like a single home, a school, or an office building.
• Ownership: Usually owned and managed by the person or organization using it.
• Speed: Very fast data transfer.
• Connection: Usually connected via Ethernet cables or Wi-Fi.
WAN (Wide Area Network)
A WAN covers a large geographical area, such as a city, a country, or even the whole world! The Internet is the ultimate example of a WAN.
• Ownership: Usually uses "leased" telecommunication lines (like big cables under the ocean) owned by companies like BT or Virgin Media.
• Speed: Generally slower than a LAN because the data has to travel much further.
Key Takeaway: If it's inside one building, it's likely a LAN. If it connects different cities or countries, it’s a WAN.
3. Client-Server vs. Peer-to-Peer
This describes the "social structure" of the network—who is in charge?
Client-Server Network
In this setup, there is a powerful central computer called a Server, and many less powerful computers called Clients.
• The Server: Holds the files, manages security, and processes requests.
• The Clients: The computers that "request" services (like opening a file or a webpage).
Example: A school network where your files are stored on a central server so you can log in from any computer.
Peer-to-Peer (P2P) Network
In a Peer-to-Peer network, every computer is equal. There is no central boss. Each computer shares its own files and printers with the others.
• Pros: Easy to set up; if one computer fails, the rest keep working.
• Cons: Security is harder to manage; files can be scattered across different machines.
Analogy: A group of friends sharing notes. Everyone has their own notebook, and you just ask whoever has the info you need.
4. Circuit Switching vs. Packet Switching
When you send data, how does it actually get from point A to point B?
Circuit Switching
This creates a dedicated, physical path between two devices for the entire duration of the connection.
• Real-world example: Old-fashioned landline telephones. When you called someone, a "circuit" was opened just for you. If you didn't speak, the line stayed open and "wasted," and no one else could use that specific path.
• Benefit: No delay (latency) once the connection is made.
Packet Switching
Instead of a dedicated line, the data is broken into small chunks called Packets. These packets are sent independently across the network and reassembled at the end.
Step-by-Step Packet Switching:
1. Data is broken into packets.
2. Each packet is given a header (containing the destination IP address and the packet number).
3. Packets are sent; they may take different routes depending on which path is fastest at that moment.
4. The receiving computer uses the packet numbers to put them back in the right order.
5. If a packet is missing, the receiver asks for it to be sent again.
Did you know? Packet switching is much more efficient than circuit switching because many people can use the same cables at the same time!
5. The TCP/IP Stack and Layering
Networking is complex, so we use layers to break it down. Each layer has a specific job and only talks to the layers directly above or below it.
The 4 Layers of the TCP/IP Stack
You can remember these with the mnemonic: All Tigers Need Lunch.
1. Application Layer: This is where the user interacts with the network (e.g., your web browser or email app). It uses protocols like HTTP or FTP.
2. Transport Layer: This layer sets up the communication between the two hosts. it breaks the data into packets and handles error checking. It uses the TCP protocol.
3. Network (or Internet) Layer: This layer addresses and routes the packets. It adds the source and destination IP addresses. It uses the IP protocol.
4. Link (or Network Access) Layer: This is the physical hardware connection (like your network card or fiber optic cable). It handles the actual bits (1s and 0s) being sent over the wire.
Why use layers?
• It makes it easier to develop new technology. You can change a Wi-Fi card (Link Layer) without having to rewrite your web browser (Application Layer)!
6. DNS (Domain Name System)
Computers communicate using IP Addresses (like \(192.168.1.1\)), but humans are much better at remembering names (like google.com). The DNS acts like the "phonebook" of the internet.
How DNS Works:
1. You type www.ocr.org.uk into your browser.
2. Your computer sends a request to a DNS Server asking: "What is the IP address for this name?"
3. The DNS server looks it up in its database.
4. The DNS server sends the IP address back to your computer.
5. Your computer can now connect directly to the web server using that IP address.
Common Mistake to Avoid: Students often think the DNS server "hosts" the website. It doesn't! It only tells you the number (IP) so you can find the website yourself.
Final Quick Review Box
Check your understanding:
• Can you explain why the TCP/IP stack uses layers?
• What is the main difference between LANs and WANs?
• Why is Packet Switching more efficient than Circuit Switching?
• What does a DNS server actually provide to your computer?
Don't worry if you need to read through the Packet Switching or TCP/IP sections a couple of times—they are the heart of networking and can take a moment to "click"!