You know, when we sit at a desk and just drag a file from our screen to a coworker's folder, there's this, I don't know, this expectation of magic.
Oh totally. It's like teleportation, right.
You drag, you drop, and poof, the file is just there.
Yeah. It feels completely instantaneous and clean and totally invisible. We just take for granted, you know, we expect the technology to just work without ever really thinking about the crazy mechanics underneath the keyboard exactly.
But then you actually look at the physical reality of a network and that whole teleportation illusion just shatters completely. It really does, because what we're actually looking at is this wild landscape of electrical pulses and hexodecimal codes. It's this highly choreographed system of invisible traffic that is honestly just mind boggling when you dig into it.
I like to call it the absolute definition of structured chaos.
Which is exactly why today's deep dive is going to demystify that chaos. We are taking you on a journey down the invisible hyperfast high way that connects our computers.
And we're using Mike Meyer's Comtia network plus Certification Guide as our map for this one.
Right, the mission here is to figure out how data actually travels. So let's look at a scenario the source sets up. Imagine two co workers, Janelle and Dana. Okay, they work in administration at this fictional company called mhtechad and Janelle has just finished writing a massive new employee handbook in Microsoft Word and she wants Dana to check it for accuracy.
A classic office setup, I mean, Janelle needs to get a really large digital file to another person in the exact same building.
Now, Janelle could just save that document to a flash drive, stand up, and physically walk it over to Dana's desk.
The old school sneakernet.
Mess is sneakernet, right, which technically works, but it kind of defeats the entire purpose of having computers wired together in a modern office.
Right. Yeah, absolutely, it's terribly inefficient.
So instead, without Eve turning around in her chair, she drags the file across her screen and sends it over the network. But and this is the big question, how does that file actually travel from Janelle's desk to Dana's desk without magic?
That is the million dollar question.
Well, by the end of this deep dive. You will never look at a plugged in computer the exact same way.
Again, I promise you won't, because to understand how Janelle's file moves, we can't just stare at the jumble of cables under the desk or the software on her monitor. We first have to look at the architectural blueprint that makes the whole system even possible. The source actually spends a lot of time on this concept of a network model.
Okay, let's unpack this. Yeah, when we hear the word model, we usually think of like a plastic model airplane, right, like a toy. Yeah, it has the wings, the tail, the cockpit, but it intentionally omits the incredibly complex internal combustion engine exactly. Or think of a computer model predicting the weather. It takes this overwhelmingly chaotic reality global wind patterns, ocean temperatures, bemetric pressure, and simplifies it into digestible, predictable parts.
And a network model does the exact same thing for the overwhelming complexity of computer networking. It breaks the entire process down into discrete individual steps.
Which makes it something we can actually wrap our heads.
Around, exactly. And the gold standard we're looking at today is called the OSI seven layer model OSI. Yeah. OSI stands for Open Systems Interconnection, and it was created by the International Organization for Standardization.
Which gives us seven specific layers to get from a physical cable all the way up to the application you are actually clicking on. So, starting from the bottom, layer one is the physical layer, then layer two is data link, Layer three is network, Layer four's transport, layer five is session, layer six is presentation, and layer seven is application.
That's flot to remember it is.
But the source gives us a classic technomonic to remember it from bottom to top.
Please do not throw sausage pizza away.
I love that it sounds silly, but I mean network engineers use that inemonic constantly to keep the hierarchy straight.
The thing that really stood out to me in the text is how the OSI model encourages modular design.
Oh yeah.
Think of it like an automobile assembly line. The person whose job it is to paint the car doesn't care about the person putting the doors.
On, not at all. He just expects the assembly line to hand him a car with doors ready to be painted. Each layer blindly trusts that the other layers are doing their specific job perfectly.
And that modularity is just vital for troubleshooting. Like if a backo outside accidentally cuts the main fiber optic cable to the.
Building, which happens way more often than it should.
Right. If that happens layer one, the physical layer's broken. But the software developers who built Microsoft Word at layer seven, they don't have to rewrite their entire application to fix the problem.
Oh wow, yeah, that makes sense.
Gives way for someone to plug in a new cable providing that structure was completely revolutionary. If we look at the early days of networking, before models like OSI, one manufacturer made absolutely everything.
You mean, like hardware and software.
Everything you bought a complete package, hardware, software, cables. All of it was proprietary, like a walled garden completely. An IBM network worked beautifully, but it only spoke IBM. An Apple network only spoke Apple.
So they couldn't talk to each other.
It made it incredibly difficult, almost impossible really, for computers from different manufacturers to actually talk to each other in the same office. The OSI model became the universal translator. It allowed developer to focus on just building a great network card or just building a great web browser, knowing it would interface perfectly with the rest of the stack.
So let's walk down those stairs and build this blueprint. Let's trace Janelle's file starting at the very bottom layer one, the physical realm, the foundation, because every blueprint has to be built on a tangible foundation. The journey of Janelle's file literally starts in the physical world.
This is the hardware, the cabling, and the central connection box. Most modern office networks use a specific type of cable called unshielded twisted pair or UTP YOUUGP rate. Inside that plastic cable casing are four pairs of tiny copper wires. Twist it together in a very specific way to prevent electromagnetic interference, and those wires are what actually transmit and receive data.
So all those cables from all the different computers in the Mhtech office snake through the drop ceilings, down the walls, and eventually plug into a central.
Box, usually hidden away in some dusty equipment closet somewhere.
Yeah exactly. But here's the wild part. To me Janelle's word document. Once it hits that wire, it's not a document anymore. It's a stream of binary ones and zeros represented by electrical pulses. If you hooked up a diagnostic tool like in a silloscope to that copper wire, you wouldn't see text or formatting.
You wouldn't see the employee handbook right.
You would just see jagged peaks and valleys of voltage. A surge of electricity is a one and the absence of a charge zero.
And because it's pure electricity, Layer one is completely blind. It doesn't know if it's transmitting an urgent financial spreadsheet or like a video of a cat playing the piano.
It just doesn't care exactly.
It just moves the voltage pulses from one computer to the central box.
Historically, that central box was a piece of hardware called a hub, and the hub was, to put it nicely, a very dumb device, very dumb. It was essentially just an electrical reputer.
Yeah, a hub has a fundamental flaw by modern networking standards, When a hub receives an electrical pulse from Janelle's computer, it has zero intelligence. It doesn't know who the message is for.
So what does it do.
It simply makes an exact copy of that pulse and blasts it out of every single port, sending it to every single computer connected to the office network.
Wait, hang on, if a hub just blasts every single electrical pulse to everyone on the network simultaneously, wouldn't that create absolute chaos?
Total chaos?
I mean, how does Dana's computer know which pulse is her employee handbook? And how do the fifty other computers in the office know to ignore it?
That pushes us directly up to the next level of the blueprint. Because the physical layer is essentially screaming the message to everyone in the room, the network strictly requires a filter at the hardware level to sort out all that noise. Okay, And that brings us to layer two, the data link layer, and a crucial piece of hardware called the NIC.
The NIC the network interface card. This is the piece of hardware that actually plugs into the motherboard of your computer, right yep. And it's where that twisted pair network cable connects. The NC basically straddles layer one and layer two, and it's what gives your computer its unique identity on the network.
Inside every single NIC, permanently burned into a read only memory chip at the factory, is a unique identifier called the MC address. MC stands for Media Access Control.
And this is where the formating gets interesting. The source breaks down the anatomy of a MESS address. It's a forty eight bit value.
Sometimes called an EUI forty eight or a messe forty eight.
Right, and because humans are frankly terrible at reading a string of forty eight ones and zeros, it is always written in hexadecimal format That means base sixteen.
Yeah. The math gets a little weird here a little bit.
Instead of just using zero through nine, it uses the numbers zero through nine plus the letters A through F to represent values up to fifteen.
What's fascinating here is how the industry ensures this address is globally unique. No two network interface cards in the entire world share the same MS address. Never The forty eight bits are split in half. The first twenty four bits make up the organizationally unique identifier or OUI. The Institute of Electrical and Electronics Engineers the IEE assigns this specific code to the manufacturer.
So it's like a brand stamp exactly.
So Sister gets a specific block of codes, Intel gets their own block, Apple gets theirs. It's almost like an area code. Then the last twenty four bits are essentially the manufacturer's specific serial numb for that exact piece of silicon.
And you can actually see this physical footprint yourself. If you are listening to this and you're sitting at a Windows computer, you can open up the command prompt type in IP canfig all and look for the line that says physical address.
That is your MC address.
Yeah, if you're on a Mac, you can open a terminal and type if canfig. You'll see a string of characters separated by dashes or colons like zero zero four, zero, zero, zero five six zero, seventy forty nine. That is your device's permanent, burned in fingerprint.
So, coming back to the chaos of the hub blasting data everywhere, the NIC is the solution. Think of the NIC is a highly disciplined bouncer at the door of your computer.
Oh, I like that a bouncer.
Right when the hub blast Janelle's file out as electrical pulses, every single NIC on the network receives those pulses. They all interpret the ones and zeros, but the immediately check the destination MAAC address stamped on the incoming data and if it's not for them, if that destination address doesn't match their own burned in fingerprint, then drops the message entirely.
It acts like it never even happened. Only data's NIC will see its own MAC address on the incoming data, accept it, and pass it up to the computer's memory.
Okay, so the bouncer checks the ID to let the data in. But that means Janelle's massive word document has to be packaged in a very specific way so the bouncer can quickly read it right exactly, because a raw, continuous stream of ones and zeros is pretty much useless without some kind of structure.
Which introduces the concept of a frame. A frame is the protocol data unit or PDU for layer two. It is basically the digital container for the data.
Here's where it gets really interesting. The source suggests visualizing this frame like one of those pneumatic tube canisters at a drive in bank.
Oh yeah, the plastic tubes.
Yeah, you put your paper check inside, close the plastic tube and it gets sucked up the pipe into the building. The text actually jokes about a little guy named nick Nick living inside the network card who works at a table building these canisters.
Little guy doing all the hard.
Work, working overtime. And then which is the frame doesn't care if it's carrying dirt or diamonds. It doesn't care if it's the employee handbook or just a quick email. It just holds the payloads safely.
And that canniser has a very rigid anatomy. In a generic wired network, the frame starts with a header. You can think of this as the shipping label.
Okay.
This header contains the destination m may address where it's going, followed immediately by the source and MAC address. Work came. Then there's a tight field that tells the receiving system what kind of data is hidden inside. After the header comes the payload itself, the actual ones and zeros of the word document, and finally the cannister ends with a trailer called the FCS or frame check sequence.
Well, wait a second. If these pneumatic canisters are a standardized size to move efficiently through the network, how on earth does a massive fifty page employee handbook with graphics and formatting fit inside one?
It doesn't. Oh, and this is where the system has to work over time. A standard frame on a wired network in general only hold a maximum of fifteen hundred bytes of data.
Fifteen hundred bytes. That's tiny.
It's an incredibly small amount of information. Yeah, so when Janelle hits send on a large word document, her computer's operating system has to step in. The software chops that massive document into hundreds, maybe thousands, of tiny fifteen hundred byte chunks. Wow. It hands those sequential chunks to the NIC, and the NIC stuffs each individual piece into its own individual frame, its own noumatic canister, and fires them off down the wire, one by one.
And then Dana's computer has to put it all back together exactly.
Dana's computer has to catch all those thousands of cannisters, open them up, extract the payloads, and seamlessly reassemble all the pieces in the exact right.
Order, which brings up a terrifying thought. We have thousands or even millions of these little fifteen hundred byte canisters flying through the copper cables at light speed. What if an electrical surge from a nearby power cord flips a single one to a zero while it is inside the cable. It happens, but a corrupted word document is completely useless.
Right, which is why quality control is so important. That's exactly what the FCS. The frame check sequence at the end of the canister is for It verifies the integrity of the data using a mathematical algorithm called a cyclic redundancy check or.
CRC CRC okay.
It is fundamentally a form of binary math division wait division.
How does doing long division on a file check for corruption. That sounds like unnecessary maths, slowing down the transfer.
It sounds crazy, but think of it with simple numbers. Imagine Janelle's data equals the number ten. Her network card divides that ten by a specific universally agreed upon key. Let's say the key is three.
Okay, ten divided by three right, ten.
Divided by three leaves the remainder of one. Janelle's NIC takes that remainder, the number one, and stamps it into the XCS trailer at the end of the frame before sending.
It okay, So the remainder travels with the file exactly.
When Dana is receiving NIC gets the canister, it takes the payload and does the exact same division problem using the exact same key of three. If Dan also gets a remainder of one, the math matches perfectly. The file is safe, the file survived the trip intact, and the frame is accepted. But if a bit flipped during travel and that ten became an eleven.
Oh, I see where this is going.
Right, Eleven divided by three leaves the remainder of two. Dana's computer sees the remainders two, realizes it doesn't match the one stamped on the trailer and immediately knows that data was corrupted in transit.
And what does it do with the cryptid canister? Does it try to fix it somehow?
It drops it instantly? Yeah, the frame is considered garbage and thrown away, forcing the upper layers of the network to eventually realize a piece is missing and asks Janelle's computer to resend that specific fifteen hundred byte chunk.
It just throws it away. That is ruthless, but I guess it has to be to ensure perfect data integrity. But hold on, I have another logistical problem here late on me. For Janelle's computer to build this canister in the first place, it needs to write Dana's specific destination NEC address on the header. But how does Janelle's computer know DANA'SMEC address. It's not like there's a physical phone book of forty eight bit hexadecimal numbers sitting on Janelle's desk.
That's a great question. It needs that address to function. So if Janelle's computer doesn't know DANA'SMEC, it uses a very specific mechanism to find out. It sends an investigative message called a broadcast.
Frame broadcast frame.
Instead of targeting a specific forty eight bit device address, it uses the universal MAC address ffffffffffff all F.
Because it's hexadesimal, F is the highest possible value.
You got it. That all F address is the universal broadcast code. When a network card sees a frame address to all FS, the bouncer doesn't drop it. Every single computer on the mhtech ed network is forced to accept that specific frame, open the canister, and read the payload like a company wide memo exactly, and the payload basically acts as a megaphone saying, Hey, whoever has the IP address for Dana's computer, please reply and tell me your physical MAC address.
And then Dana's computer answers yep.
Dana's computer sees the request, realizes it's the intended target, and sends a direct reply back with their burned in MPAC address. Now Janelle's computer caches it in memory and can send the thousands of document frames directly.
But if we combine this with what we learned about hubs earlier, hubbs blindly blast every electrical pulse out of every port, and now we are adding broadcast frames that force every single computer to open and read the message. If Mhtech has fifty or one hundred computers all sending broadcasts and hubs blasting everything everywhere, that sounds like a recipe for a complete network meltdown. The cables would be absolutely saturated with noise.
If we connect this to the bigger picture, you have just identified why the networking industry had to evolve.
Oh good, so they fixed it.
They had to. Relying on hubbs would completely break a large modern network. The sheer volume of traffic, the constant copying of frames would overwhelm the physical bandwidth of the cables. This is exactly why Layer two hardware advanced. The dumb hub was replaced by an intelligent device called a switch.
The switch, which, if you look at it in the equipment closet, looks almost exactly like a hub, doesn't It Just a metal box with a bunch of ports for cables to plug into.
Physically similar, but internally, a switch is a massive leap forward, a switch actually learns. It learns it contains a memory bank. Every time a device sends a frame into the switch, the switch looks at the source MK address on a header. It notes odd, Janelle's MK address is coming in on port two. It writes that down in a dynamic table. Oh wow. When Dana replies, it logs Dana's MAA address is on port five. It dynamically builds a literal map of the office network.
So it's not guessing anymore exactly.
The next time Janelle sends a frame destined for Dana's MTA address, the switch consoles its internal table. It knows Dana's on port five. So instead of blasting the electrical pulses out of every single port like a hub, it sends the voltage only down the specific cable plugged into port.
That is so much more efficient.
It revolutionized network efficiency by turning a noisy room where everyone is shouting over each other into a sophisticated system of private direct telephone lines.
That's incredible.
And if you are listening to this on Wi Fi at a busy coffee shop right now, the wireless router is acting exactly like a modern switch mapping the mac addresses of all the laptops and phones, filtering the traffic so your device only receives this audio data and ignores everyone else's video streams.
Okay, let's take a breath. So what does this all mean? We started with Janelle dragging and dropping a massive word document to data. It feels like simple teleportation magic on the screen, but it's not. No. Underneath that illusion, an incredibly complex ballet is taking place. In fractions of a millisecond, that simple text file is chopped into thousands of fifteen
hundred byte pieces. Each piece is stuffed into a virtual pneumatic canister, stamped with a serial number, stamped with unique forty eight bit hexadecimal codes that were liter really burned into silicon at a factory. The whole package is converted into pure electrical voltage sent across twisted copper wires routed by intelligence, which is building dynamic memory maps mathematically verified by long division to ensure no bits flipped, and finally reassembled by the receiving operating system.
Exhausting just to say it.
It really is all of that just so Dana can read an employee handbook. It really makes you realize how monumental human engineering really is to make all this completely invisible.
It truly is a marvel of modular design, showing how layers of technology can blindly trust each other to perform highly specific tasks. But you know, looking at the mechanics of this blueprint also leaves us with something deeper to consider.
What's that?
Well, this raises an important question. Think about that m address we spend so much time examining. We just learned that every single network interface card in the world, including the one of the smartphone in your pocket, your laptop, your smart watch, has a permanently burned in universally unique forty eight bit serial numbers or identifying exactly who made it and which specific unit it.
Is, right, the manufacturer's OUI and the device's exact serial number.
And our devices are constantly sending out frames stamped with this permanent digital fingerprint just to function on network. They broadcast it to find rouders, they use it as the source address to send data. It is a fundamental inescapable requirement of layer two networking.
Yeah, they have to.
So if our personal devices are silently screaming this permanent unique serial number out into the airwaves just to get a connection. What does that mean for our privacy as we carry these devices through public spaces, coffee shops, airports, and across networks we don't even own.
Wow. From an innocent file transfer in an office to a permanent digital footprint tracking our devices, that teleportation magic definitely has a physical reality. We all need to be a little more aware of something
To mull over the next time you connect to a network.