📱

Get Our Mobile App

Take your business learning on the go!

Download on the App StoreGet it on Google Play

The OSI Model makes networking finally make sense 💬

KodeKloud•2:34

Transcription

The OSI models have been explained many, many, many times in the past, but not with this level of clarity. The OSI model has seven layers, and we're going to trace how an HTTP request travels through each one. [music] Think of it like a letter getting wrapped in envelopes, each with different information. From your browser [music] to a web server and back. Let's see what happens at each layer. Let's start with our example. You're browsing example.com. [music]

At layer seven, your browser creates an HTTP request, index.html. >> [music] >> This is the actual data you want to send. Pure application stuff. It's like writing a letter saying, >> [music] >> "Please send me the home page."

Now, layer six steps in. This is where things get secure. It wraps your HTTP request in SSL TLS encryption, like putting your letter in a locked box. Layer five is all about keeping track of your conversation. It adds a session ID, so the server knows it's still talking [music] to you. Handles authentication and manages timeouts.

Now, we get to the networking layers. Layer four wraps everything in TCP for reliable [music] delivery. It adds source port 54321, destination port 443 for HTTPS, and sequence numbers. Layer three adds IP routing info. >> [music] >> Your IP 192.168.1.100 to the server's IP 93.184.216.34. Layer two adds MAC addressing for local network delivery.

Finally, layer one converts everything to electrical signals that travel through your ethernet cable or Wi-Fi radio waves. It travels across the internet through routers that read layer three, switches that read layer two, and finally, reaches the web server.

The web server receives your packet and processes it in reverse order. Layer one converts electrical signals back to data. Layer two removes MAC headers. Layer three removes IP headers. Layer four removes TCP headers. Layer five manages the session. >> [music] >> Layer six decrypts the SSL. And finally, layer seven processes your HTTP request and sends [music] back the web page.

Understanding this layered approach is super important for system [music] design. Load balancers operate at different layers.