惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
U
Unit 42
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The GitHub Blog
The GitHub Blog
Microsoft Azure Blog
Microsoft Azure Blog
有赞技术团队
有赞技术团队
Stack Overflow Blog
Stack Overflow Blog
爱范儿
爱范儿
博客园 - 司徒正美
Vercel News
Vercel News
I
InfoQ
GbyAI
GbyAI
C
Check Point Blog
B
Blog RSS Feed
Martin Fowler
Martin Fowler
B
Blog
MyScale Blog
MyScale Blog
腾讯CDC
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Hugging Face - Blog
Hugging Face - Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 三生石上(FineUI控件)

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
The OSI Model Explained: A Beginner's Guide to Network La...
Sailee Shingare · 2026-06-27 · via DEV Community

The OSI Model sounds like something only network engineers need to know. But it's actually a simple framework that explains how data moves across the internet.

If you've ever wondered what happens when you click a link, the OSI Model is your answer.

What Is the OSI Model?

OSI stands for Open Systems Interconnection. It's a model that breaks down how computer networks work into 7 layers. Think of it like a stack of steps — data travels down the stack when you send something, and up the stack when you receive it.

Each layer has a specific job. Each layer depends on the layer below it.

Why care? Understanding these layers helps you troubleshoot network problems, understand security, and grasp how the internet actually works.

The 7 Layers (Top to Bottom)

Layer 7: Application

Where users interact. Email, web browsers, file transfers, chat apps — they all live here.

When you visit a website, your browser is operating at Layer 7.

Layer 6: Presentation

Formats the data for display. Encryption, compression, translation. Converts data into something readable.

Example: Your browser decrypts HTTPS data so you can read the webpage.

Layer 5: Session

Manages connections. Starts, maintains, and ends conversations between devices.

Example: When you log into email, this layer keeps your session alive while you're checking messages.

Layer 4: Transport

Reliable delivery. Decides how data gets from point A to point B. Uses protocols like TCP (reliable, slower) and UDP (fast, less reliable).

TCP: Email (important, must arrive)
UDP: Video streaming (fast matters more than perfection)

Layer 3: Network

Routing. Finds the best path for data across the internet. IP addresses live here (192.168.1.1).

This layer asks: "How do I get to that IP address?"

Layer 2: Data Link

Moves data between devices on the same network. MAC addresses live here (physical addresses, not IP).

Example: Your laptop connects to your WiFi router. Layer 2 handles that.

Layer 1: Physical

The actual wires, cables, radio waves. The hardware.

Example: Your Ethernet cable, WiFi signal, fiber optic cable.

How Data Flows

When you send an email:

Going down (your computer):

  1. You write an email (Layer 7)
  2. Browser encrypts it (Layer 6)
  3. Session is maintained (Layer 5)
  4. Email travels via TCP (Layer 4)
  5. Routed to recipient's IP (Layer 3)
  6. Converted to frames for the network (Layer 2)
  7. Sent as electrical signals (Layer 1)

Going up (recipient's computer):
Same layers, reverse order. Data arrives as signals, reconstructed as frames, routed, transported, formatted, presented, and displayed in their email app.

Practical Examples

Why your WiFi is slow:
Could be Layer 1 (weak signal), Layer 2 (WiFi channel congestion), Layer 3 (bad routing), Layer 4 (too many connections), or Layer 7 (app issue).

Why HTTPS is secure:
Encryption happens at Layer 6. Your data is encrypted before it leaves, travels encrypted, and decrypts only at the destination.

Why ping tests troubleshooting:
Ping tests Layer 3 (routing) and Layer 4 (transport). If ping works but email doesn't, the problem is likely Layer 5, 6, or 7.

DNS (Domain Name System):
Sits between Layer 5 and Layer 7. Translates domain names (google.com) to IP addresses (142.250.185.46).

The Takeaway

The OSI Model is a mental framework. It helps you understand that the internet isn't magic — it's layers of systems, each doing a specific job, all working together.

You don't need to memorize all 7. Just remember: upper layers (5-7) handle data meaning. Middle layers (3-4) handle delivery. Lower layers (1-2) handle the physical transport.

Next time something doesn't work online, think OSI. It'll make troubleshooting easier.


Ever had a network problem? Share what layer it turned out to be. I'm curious what surprised you most about how networks actually work.

By Sailee Shingare | M.S. in Computer Science, Northern Illinois University