WEBVTT 1 00:00:00.120 --> 00:00:03.359 So every time you double tap a photo on your 2 00:00:03.359 --> 00:00:07.519 phone to like it, you're actually unknowingly triggering this really 3 00:00:07.559 --> 00:00:10.320 strict Cold War era military protocol. 4 00:00:10.519 --> 00:00:12.199 Yeah, it's wild to think about. 5 00:00:12.160 --> 00:00:15.240 Right, Like that tiny action chops your tap into these 6 00:00:15.279 --> 00:00:19.920 microscopic data packets, scrutinizes them through intelligent intersections, and then 7 00:00:20.039 --> 00:00:23.199 you shoots them via lasers through hair thin tubes of 8 00:00:23.239 --> 00:00:26.399 glass across the ocean, and all of that in just 9 00:00:26.519 --> 00:00:28.440 a matter of milliseconds. 10 00:00:27.879 --> 00:00:32.479 Which is frankly a brilliantly constructed illusion of simplicity because 11 00:00:32.520 --> 00:00:35.920 the moment you look beneath that frictionless glass screen while 12 00:00:36.000 --> 00:00:39.640 you find this world of uncompromising traffic laws and literal 13 00:00:39.719 --> 00:00:40.960 light speed logistics. 14 00:00:41.119 --> 00:00:44.560 I mean, we interact with this invisible architecture constantly streaming, 15 00:00:44.600 --> 00:00:47.560 working whatever. Yeah, but we almost never see the sprawling 16 00:00:47.600 --> 00:00:51.560 physical infrastructure making it happen. It just feels like magic, exactly. 17 00:00:51.719 --> 00:00:54.320 But every single piece of data has to navigate a 18 00:00:54.399 --> 00:00:57.039 highly organized gauntlet to get from point A to point B. 19 00:00:57.359 --> 00:01:01.039 And today we are going to demystify that exact gauntlet. 20 00:01:01.159 --> 00:01:02.359 Welcome to today's deep dive. 21 00:01:02.479 --> 00:01:03.079 Glad to be here. 22 00:01:03.200 --> 00:01:05.879 Our mission today is to take you on the exact 23 00:01:05.959 --> 00:01:08.760 journey your data takes from the physical cables in your 24 00:01:08.799 --> 00:01:11.879 wall all the way up to the invisible rules governing 25 00:01:11.959 --> 00:01:12.680 the global web. 26 00:01:12.959 --> 00:01:16.000 And to map this out, we are diving into excerpts 27 00:01:16.000 --> 00:01:20.359 from Todd Lamley's CCNA Certifications Study Guide, Volume. 28 00:01:20.079 --> 00:01:23.359 Two, Yeah, which is basically the definitive blueprint for understanding 29 00:01:23.400 --> 00:01:24.840 the nuts and bolts of networking. 30 00:01:25.159 --> 00:01:27.959 What makes this material so compelling is that it focuses 31 00:01:28.000 --> 00:01:31.319 heavily on the why. You know. It reveals the sheer 32 00:01:31.480 --> 00:01:35.280 human ingenuity required to solve massive logistical problems. 33 00:01:35.319 --> 00:01:38.680 Because networking did not start out organized, did it. 34 00:01:38.719 --> 00:01:41.079 Not at all? The rules and devices we used today 35 00:01:41.159 --> 00:01:44.680 they evolved out of absolute necessity to prevent digital traffic 36 00:01:44.719 --> 00:01:46.480 from just collapsing under its own weight. 37 00:01:46.640 --> 00:01:48.799 So let's start right there at the physical intersections, you know, 38 00:01:48.840 --> 00:01:51.599 the devices that act as the traffic cops for our data. 39 00:01:51.680 --> 00:01:55.000 Right. The transition from hubs to switches to routers. It's 40 00:01:55.040 --> 00:01:58.840 really a story of moving from total chaos to highly 41 00:01:58.959 --> 00:01:59.920 targeted communication. 42 00:02:00.359 --> 00:02:02.120 Yeah. Because in the early days, if you wired a 43 00:02:02.159 --> 00:02:05.799 small office together, you plug everything into a hub. And 44 00:02:06.480 --> 00:02:09.199 I mean a hub is about the dumbest piece of 45 00:02:09.240 --> 00:02:10.520 hardware imaginable. 46 00:02:10.680 --> 00:02:14.000 It really is. It operates with zero intelligence, right, It just. 47 00:02:13.960 --> 00:02:16.879 Takes an electrical signal coming in on one wire and 48 00:02:17.000 --> 00:02:19.400 blindly copies it to every other connected wire. 49 00:02:19.560 --> 00:02:22.120 Yeah. So if a hub receives a message meant for 50 00:02:22.199 --> 00:02:25.479 one specific computer, it just blasts that message out to 51 00:02:25.560 --> 00:02:27.439 fifty other computers anyway. 52 00:02:27.080 --> 00:02:29.120 Which causes a massive problem. 53 00:02:28.800 --> 00:02:32.039 Exactly, an electrical problem. If two devices connected to that 54 00:02:32.120 --> 00:02:34.560 hub try to talk at the exact same fraction of 55 00:02:34.599 --> 00:02:38.439 a second, they're electrical signals physically crash into each other 56 00:02:38.520 --> 00:02:41.479 on the wire. Oh wow, Yeah, the data becomes corrupted, 57 00:02:41.759 --> 00:02:45.800 the transmission fails, and both computers have to pause for 58 00:02:45.800 --> 00:02:47.759 a random amount of time before trying again. 59 00:02:47.960 --> 00:02:50.680 And that is what the industry calls a single collision domain. 60 00:02:50.840 --> 00:02:52.080 Right, yes, exactly. 61 00:02:52.159 --> 00:02:56.000 I always picture a hub like a guy at a 62 00:02:56.039 --> 00:02:58.879 crowded party. If he wants to tell a secret to 63 00:02:58.919 --> 00:03:00.800 one person, he doesn't walk over and whisper. 64 00:03:01.680 --> 00:03:02.800 He grabs a megaphone. 65 00:03:02.919 --> 00:03:06.000 Yes, he grabs a megaphone and shouts it to the 66 00:03:06.159 --> 00:03:09.879 entire room. Everyone has to stop their conversation, listen to 67 00:03:09.879 --> 00:03:12.840 the megaphone and figure out if the message is for them. 68 00:03:13.159 --> 00:03:16.479 And if two people shout at once, no one understands anything. Right. 69 00:03:16.639 --> 00:03:18.919 You can imagine how quickly a network grinds to a 70 00:03:18.960 --> 00:03:22.240 halt if fifty computers are constantly shouting over each other. 71 00:03:22.439 --> 00:03:27.039 So to fix that literal shouting match, network engineers introduced switches, 72 00:03:27.159 --> 00:03:30.439 which are much smarter, way smarter. A switch actually pays 73 00:03:30.439 --> 00:03:34.680 attention to who is talking to whom. It uses specialized 74 00:03:34.719 --> 00:03:39.719 hardware called application specific integrated circuits or ASEX, which process 75 00:03:39.840 --> 00:03:43.960 data at blistering speeds. Wait, yeah, ASEX. The moment a 76 00:03:44.039 --> 00:03:47.560 computer plugs into a switch, the switch memorizes its physical 77 00:03:47.599 --> 00:03:50.439 hardware address, its MBSC address, and logs it into a 78 00:03:50.439 --> 00:03:51.759 dedicated filter table. 79 00:03:51.879 --> 00:03:55.319 Okay, so it turns the chaotic megaphone room into like 80 00:03:55.360 --> 00:03:56.599 a polite cocktail party. 81 00:03:56.719 --> 00:03:59.759 Exactly, people are having private one on one conversations. 82 00:04:00.039 --> 00:04:02.360 So when computer A sends a file to computer B, 83 00:04:02.840 --> 00:04:05.560 the switch checks its filter table and forwards that electrical 84 00:04:05.599 --> 00:04:08.199 signal exclusively to the single port where computer B is 85 00:04:08.199 --> 00:04:10.240 plugged in. Nobody else hears it. 86 00:04:10.479 --> 00:04:14.360 Right, it successfully breaks up the collision domains. Everyone can 87 00:04:14.400 --> 00:04:20.040 talk simultaneously without their signals interfering. But switches introduce a 88 00:04:20.079 --> 00:04:23.759 new vulnerability. Oh really yeah, because they are designed to 89 00:04:23.920 --> 00:04:27.079 forward a very specific type of traffic called a. 90 00:04:27.040 --> 00:04:29.240 Broadcast, Right I remember reading about that. 91 00:04:29.279 --> 00:04:33.040 Sometimes a computer legitimately needs to ask the entire local 92 00:04:33.079 --> 00:04:36.759 network a question like who has this specific IP address? 93 00:04:37.519 --> 00:04:41.319 The switch will dutifully take that broadcast question and copy 94 00:04:41.360 --> 00:04:42.560 it to every single. 95 00:04:42.279 --> 00:04:45.519 Port, which sounds fine until your network grows. Yeah, because 96 00:04:45.519 --> 00:04:48.279 if you have thousands of devices occasionally shouting questions to 97 00:04:48.319 --> 00:04:51.959 the entire room, you create a broadcast storm exactly. 98 00:04:52.360 --> 00:04:55.879 The network gets so bogged down processing everyone's general questions 99 00:04:55.879 --> 00:04:58.160 that actual data just stops moving. 100 00:04:58.000 --> 00:04:59.480 And that brings us to the bouncer at the door, 101 00:04:59.519 --> 00:04:59.920 the router. 102 00:05:00.319 --> 00:05:03.560 The router is key. Routers operate on a completely different 103 00:05:03.639 --> 00:05:06.920 level of logic. Instead of looking at physical mix addresses, 104 00:05:07.319 --> 00:05:09.800 they read logical IP addresses, and their. 105 00:05:09.600 --> 00:05:13.199 Default behavior is to relentlessly block local broadcasts. Right. 106 00:05:13.560 --> 00:05:16.519 Yes, If a packet hits a router and it is 107 00:05:16.560 --> 00:05:20.040 addressed to everyone on this local network, the router drops 108 00:05:20.040 --> 00:05:21.360 it immediately, so. 109 00:05:21.279 --> 00:05:24.120 The writer stands at the exit of the party. It 110 00:05:24.160 --> 00:05:28.399 breaks up those broadcast domains so that local chatter doesn't 111 00:05:28.439 --> 00:05:29.759 deafen the entire Internet. 112 00:05:29.879 --> 00:05:32.639 Precisely, if you want to talk to a device in 113 00:05:32.680 --> 00:05:35.720 the room next door, meaning a completely different network. You 114 00:05:35.800 --> 00:05:37.319 have to go through the bouncer, So. 115 00:05:37.240 --> 00:05:41.079 You contain collisions with switches and you contain broadcasts with routers. 116 00:05:41.639 --> 00:05:45.319 Makes sense, right, And once those foundational intersections are in place, 117 00:05:45.480 --> 00:05:47.000 the challenge shifts to scale. 118 00:05:47.360 --> 00:05:51.759 Moving from a single room to a massive corporate campus 119 00:05:51.800 --> 00:05:52.600 or a data center. 120 00:05:52.720 --> 00:05:55.480 Yeah, that requires a structured architectural model to keep all 121 00:05:55.480 --> 00:05:58.680 those switches and routers organized. The classic approach is the 122 00:05:58.720 --> 00:05:59.839 three tier model. 123 00:05:59.639 --> 00:06:05.079 Which is this beautifully logical hierarchy broken into three layers, access, distribution, 124 00:06:05.279 --> 00:06:05.680 and core. 125 00:06:06.000 --> 00:06:10.079 Correct. The access layer is where you, the user, actually interact. 126 00:06:09.759 --> 00:06:12.839 With the network, like where my desktop computer plugs directly 127 00:06:12.839 --> 00:06:13.240 into an. 128 00:06:13.199 --> 00:06:16.759 Access switch exactly. Its only job is to get you 129 00:06:16.839 --> 00:06:21.959 connected and enforce basic port security. Above that sits the 130 00:06:22.000 --> 00:06:25.079 distribution layer, which is essentially the brains of the entire 131 00:06:25.120 --> 00:06:26.000 campus network. 132 00:06:26.279 --> 00:06:28.160 This is where the heavy duty routing happens, right. 133 00:06:28.279 --> 00:06:31.480 Yeah. It connects all the various access switches together, apply 134 00:06:31.560 --> 00:06:36.319 security policies, enforces access lists, and ultimately directs your traffic 135 00:06:36.360 --> 00:06:37.959 toward the top of the pyramid. 136 00:06:37.639 --> 00:06:39.680 Which is the core layer. And the core layer is 137 00:06:39.720 --> 00:06:42.800 all about pure, unadulterated. 138 00:06:42.000 --> 00:06:45.519 Speed, nothing but speed. The source material stresses that you 139 00:06:45.560 --> 00:06:48.639 should never ever put a firewall or an access list 140 00:06:48.639 --> 00:06:49.319 in the core layer. 141 00:06:49.360 --> 00:06:51.920 It's like a massive data highway. You do not put 142 00:06:51.959 --> 00:06:53.759 a toll booth in the middle of the autobox. 143 00:06:53.839 --> 00:06:57.079 Great analogy. Its only job is to switch massive volumes 144 00:06:57.120 --> 00:06:59.439 of data as fast as physically possible. 145 00:07:00.120 --> 00:07:02.279 You know, I was looking at the section on network designs, 146 00:07:02.399 --> 00:07:05.879 and it also details a collapsed core setup, yeah, which 147 00:07:05.920 --> 00:07:10.319 intentionally combines the core distribution layers into one device. I mean, 148 00:07:10.759 --> 00:07:13.639 if the core is supposed to be this sacred, blazing 149 00:07:13.720 --> 00:07:17.800 fast highway with no rules, why would anyone deliberately bottleneck 150 00:07:17.839 --> 00:07:20.160 it by bogging it down with distribution duties. 151 00:07:20.360 --> 00:07:24.000 Well, it's a perfect example of engineering meeting economic reality. 152 00:07:24.720 --> 00:07:29.480 Building a true three to two network requires purchasing highly specialized, 153 00:07:29.680 --> 00:07:33.519 tremendously expensive hardware, So it's the money thing. Completely. A 154 00:07:33.600 --> 00:07:36.879 dedicated core switch that does nothing but move data at 155 00:07:36.959 --> 00:07:40.240 wire speed costs of fortune. For a small to mid 156 00:07:40.319 --> 00:07:44.600 size business. Their daily data volume rarely justifies that kind 157 00:07:44.600 --> 00:07:45.519 of capital. 158 00:07:45.160 --> 00:07:48.279 Expenditure, so they compromise to save the budget. They collapse 159 00:07:48.360 --> 00:07:51.399 the brains in the highway into a single physical box. Right. 160 00:07:51.600 --> 00:07:55.000 They lose that theoretical maximum top speed. But for a 161 00:07:55.040 --> 00:07:58.240 fifty person company, it is still more than fast enough 162 00:07:58.240 --> 00:08:00.839 to get the job done. Practicality off and wins out. 163 00:08:00.920 --> 00:08:03.639 But as we move from corporate offices into modern cloud 164 00:08:03.720 --> 00:08:07.000 data centers, the three tier model starts to show cracks, 165 00:08:07.040 --> 00:08:07.519 doesn't it. 166 00:08:07.519 --> 00:08:10.639 It does. In a traditional office, traffic flows north south. 167 00:08:10.879 --> 00:08:13.240 You sit at your desk, request a file from a server, 168 00:08:13.319 --> 00:08:15.839 and the file comes back down. But in a massive 169 00:08:15.879 --> 00:08:19.000 data center powering something like a streaming service, the servers 170 00:08:19.040 --> 00:08:22.199 are constantly talking directly to each other, sinking databases and 171 00:08:22.240 --> 00:08:24.560 sharing workloads. That's east west. 172 00:08:24.279 --> 00:08:27.560 Traffic and pushing east west traffic up and down. A 173 00:08:27.600 --> 00:08:30.959 three tier pyramid creates a massive bottleneck. 174 00:08:31.160 --> 00:08:34.600 Exactly. That is why modern data centers use a spine 175 00:08:34.679 --> 00:08:35.559 leaf architecture. 176 00:08:35.919 --> 00:08:38.919 In this setup, every leaf switch, which sits at the 177 00:08:39.000 --> 00:08:42.039 very top of a server rack, connects directly to every 178 00:08:42.080 --> 00:08:43.519 single spine switch in the room. 179 00:08:43.799 --> 00:08:46.919 It creates a highly predictable environment where any server can 180 00:08:47.000 --> 00:08:50.080 talk to any other server in exactly one hop. The 181 00:08:50.159 --> 00:08:52.039 latency is virtually non existent. 182 00:08:52.200 --> 00:08:56.399 But that instant unhindered access introduces a terrifying security risk. 183 00:08:56.440 --> 00:09:00.679 Right, oh, absolutely, If every server can reach every other server, instantly. 184 00:09:01.000 --> 00:09:05.320 A malicious virus can infect the entire data center in milliseconds, which. 185 00:09:05.159 --> 00:09:08.360 Is why the architecture evolved to include next generation firewalls 186 00:09:08.799 --> 00:09:11.320 or ngfw's like Cisco's Firepower. 187 00:09:11.440 --> 00:09:14.039 Yes, these are light years beyond the old firewalls that 188 00:09:14.159 --> 00:09:16.120 just checked a port number and an IP address. 189 00:09:16.240 --> 00:09:18.679 Right. A traditional firewall is like a security guard just 190 00:09:18.799 --> 00:09:20.840 checking if your name is on the guest list. A 191 00:09:20.879 --> 00:09:24.399 next generation firewall actually opens the envelope, reads the letter, 192 00:09:24.759 --> 00:09:26.440 and decides if the contents are a threat. 193 00:09:26.679 --> 00:09:28.799 That's a great way to put it. It performs deep 194 00:09:28.799 --> 00:09:33.399 packet inspection, utilizing intrusion prevention systems to hunt down malicious 195 00:09:33.399 --> 00:09:35.559 code hidden inside normal looking traffic. 196 00:09:35.799 --> 00:09:38.080 It uses Application visibility and control. 197 00:09:37.799 --> 00:09:42.159 Right yes, AVC. It understands the context of what you're doing. 198 00:09:42.399 --> 00:09:44.840 It knows the difference between you logging into a cloud 199 00:09:44.879 --> 00:09:48.399 storage site to read a document versus trying to covertly 200 00:09:48.480 --> 00:09:50.679 upload proprietary company data, and. 201 00:09:50.639 --> 00:09:53.320 It can block the upload while allowing the read access. 202 00:09:53.519 --> 00:09:57.480 That's incredible. So we have these highly intelligent intersections, massive 203 00:09:57.600 --> 00:10:01.519 architectural grids, and incredibly paranoid security guards. 204 00:10:01.320 --> 00:10:04.159 But none of this functions without the physical roads. 205 00:10:04.320 --> 00:10:07.559 Right. I was looking at the section on unshielded twisted 206 00:10:07.600 --> 00:10:10.720 pair or UTP cabling. This is the standard copper Cat 207 00:10:10.799 --> 00:10:12.879 six cable you probably have plugging into the back of 208 00:10:12.879 --> 00:10:13.759 your WiFi. 209 00:10:13.519 --> 00:10:16.320 Radder, the standard workhourse of networking. 210 00:10:15.960 --> 00:10:18.480 And it honestly blew my mind that the eight tiny 211 00:10:18.480 --> 00:10:22.320 copper wires inside are twisted together not for durability, but 212 00:10:22.440 --> 00:10:25.879 to utilize literal physics to cancel out electromagnetism. 213 00:10:25.960 --> 00:10:29.840 It is an incredibly elegant analog solution to a digital problem. 214 00:10:30.159 --> 00:10:31.279 How does that actually work? 215 00:10:31.480 --> 00:10:35.519 Well? When electrical signals travel down parallel copper wires, they 216 00:10:35.559 --> 00:10:40.399 generate tiny electromagnetic fields. If those wires sit flat next 217 00:10:40.440 --> 00:10:43.279 to each other, the fields bleed over and corrupt the 218 00:10:43.320 --> 00:10:45.720 data on the adjacent wires. We call that. 219 00:10:45.759 --> 00:10:48.000 Cross stock ah crosstalk. 220 00:10:48.200 --> 00:10:51.639 Yeah, But by tightly twisting the pairs together, the opposing 221 00:10:51.679 --> 00:10:55.919 electromagnetic fields perfectly cancel each other out. The tighter the twist, 222 00:10:56.080 --> 00:10:57.639 the less cross stock you get. 223 00:10:57.480 --> 00:11:00.879 Which is exactly why a modern Cat sick cable can 224 00:11:00.919 --> 00:11:04.759 push gigabit speeds while an older, loosely twisted Cat five 225 00:11:04.840 --> 00:11:05.840 cable cannot. 226 00:11:06.080 --> 00:11:08.440 Exactly the physicality of it is amazing. 227 00:11:08.639 --> 00:11:11.039 The text also explains the difference between a straight through 228 00:11:11.039 --> 00:11:13.679 cable and a crossover cable. Right straight through cable is 229 00:11:13.720 --> 00:11:16.120 exactly what it sounds like. Pin one on one end 230 00:11:16.120 --> 00:11:18.159 connects to pin one on the other end. You use 231 00:11:18.200 --> 00:11:20.559 it to connect different types of devices, like a computer 232 00:11:20.759 --> 00:11:21.679 to a switch. 233 00:11:21.440 --> 00:11:23.919 Because the computer transmits on pin one and the switch 234 00:11:23.960 --> 00:11:25.519 expects to receive on pin one. 235 00:11:25.639 --> 00:11:28.679 Right. But if you connect two identical devices like two switches, 236 00:11:28.960 --> 00:11:31.440 using a straight through cable, it is like walking up 237 00:11:31.480 --> 00:11:33.080 to a mirror and trying to shake hands with your 238 00:11:33.080 --> 00:11:33.679 own reflection. 239 00:11:34.039 --> 00:11:36.919 That mirror analogy is spot on. If you put your 240 00:11:37.000 --> 00:11:39.720 right hand out, your reflection puts its right hand out, 241 00:11:39.879 --> 00:11:42.360 and your hands just awkwardly bump into each other. 242 00:11:42.519 --> 00:11:45.440 Yeah. So, if switch A transmits on pin one and 243 00:11:45.480 --> 00:11:48.799 switch B also transmits on pin one, the electrical signals 244 00:11:48.840 --> 00:11:50.399 physically collide on the wire. 245 00:11:50.600 --> 00:11:53.879 To fix it, you use a crossover cable, which physically 246 00:11:53.919 --> 00:11:56.879 crosses the transmit pins on one end over to the 247 00:11:56.919 --> 00:11:58.000 receive pins on the other. 248 00:11:58.279 --> 00:12:00.600 You are crossing your arms to shake hands of the mirror, 249 00:12:00.759 --> 00:12:03.080 ensuring the dat lands perfectly where it is expected. 250 00:12:03.120 --> 00:12:07.360 Precisely. But copper is just one medium. The true backbone 251 00:12:07.360 --> 00:12:10.320 of the global Internet is fiber optic cabling, which is 252 00:12:10.440 --> 00:12:12.480 just mine bending because. 253 00:12:12.200 --> 00:12:15.279 We are shooting actual lasers down tubes of glass. Yeah. 254 00:12:15.559 --> 00:12:18.919 By using pulses of light instead of electricity, fiber optics 255 00:12:18.919 --> 00:12:23.039 are completely immune to electromagnetic interference. There is zero cross stock, 256 00:12:23.279 --> 00:12:23.559 and the. 257 00:12:23.519 --> 00:12:27.759 Material highlights two distinct types, single mode and multimode. Single 258 00:12:27.759 --> 00:12:31.240 mode fiber has a microscopic glass core, typically around nine 259 00:12:31.279 --> 00:12:32.279 microns thick. 260 00:12:32.120 --> 00:12:35.080 Which is significantly thinner than a single strand of human hair. 261 00:12:35.200 --> 00:12:35.879 That's just wild. 262 00:12:36.279 --> 00:12:39.799 It uses a highly focused, expensive laser to shoot a 263 00:12:39.840 --> 00:12:43.799 concentrated beam of light straight down that tiny core. Because 264 00:12:43.840 --> 00:12:46.960 the light does not disperse or bounce around, it maintains 265 00:12:46.960 --> 00:12:49.600 its integrity over massive distances, so. 266 00:12:49.600 --> 00:12:53.200 Delecom companies use single mode fiber to cross oceans and 267 00:12:53.200 --> 00:12:54.679 connect cities exactly. 268 00:12:54.879 --> 00:12:59.240 Multimode fiber, conversely, has a much wider core, usually fifty microns, 269 00:13:00.080 --> 00:13:03.120 uses a cheaper led light source that physically bounces off 270 00:13:03.159 --> 00:13:05.240 the interior walls of the glass as it travels. 271 00:13:05.639 --> 00:13:08.120 And because the light is rickicheting off the walls, it 272 00:13:08.200 --> 00:13:11.080 naturally spreads out and gets fuzzy over long distances. 273 00:13:11.240 --> 00:13:14.360 Right, So multimode is heavily restricted to short runs like 274 00:13:14.399 --> 00:13:17.879 connecting different server racks within the same physical building. Single 275 00:13:17.879 --> 00:13:20.000 mode handles the cross country heavy lifting. 276 00:13:20.159 --> 00:13:23.759 Got it. There's one more crucial physical technology to cover 277 00:13:24.240 --> 00:13:26.320 power over Ethernet or POE. 278 00:13:26.559 --> 00:13:29.879 Ah yes, standards like aightoh two point three AF and 279 00:13:29.960 --> 00:13:31.200 a two point three APP. 280 00:13:31.360 --> 00:13:33.799 These allow a network switch to send both high speed 281 00:13:33.879 --> 00:13:37.360 data and low voltage electrical power down the exact same 282 00:13:37.360 --> 00:13:38.639 copper UTP cable. 283 00:13:38.720 --> 00:13:41.679 It's incredibly useful. Think about the logistics of outfitting a 284 00:13:41.720 --> 00:13:45.320 massive one hundred thousand square foot warehouse with security cameras. 285 00:13:45.639 --> 00:13:49.360 Right, If every camera requires a dedicated power outlet, you 286 00:13:49.399 --> 00:13:52.159 have to hire licensed electricians to run heavy condo it 287 00:13:52.240 --> 00:13:55.679 up into the rafters for every single device, which costs 288 00:13:55.679 --> 00:13:57.000 an absolute fortune. 289 00:13:57.039 --> 00:13:59.960 But with POE, you just run one cheap CAT six 290 00:14:00.120 --> 00:14:02.120 cable from the network switch to the camera. 291 00:14:02.360 --> 00:14:04.679 The switch pumps the DC power to turn the camera 292 00:14:04.720 --> 00:14:08.120 on and receives the four K video feedback over the 293 00:14:08.159 --> 00:14:11.799 exact same wire. It's a masterpiece of efficiency, it really is. 294 00:14:11.879 --> 00:14:15.200 So we have built the physical roads, established the intersections, 295 00:14:15.240 --> 00:14:16.960 and powered the devices. 296 00:14:16.480 --> 00:14:19.240 But none of this infrastructure means anything if the devices 297 00:14:19.279 --> 00:14:21.480 do not speak a common language. 298 00:14:21.200 --> 00:14:25.399 Which brings us to the protocols, specifically TCPIP and the 299 00:14:25.480 --> 00:14:26.960 DoD model, and the. 300 00:14:26.960 --> 00:14:29.559 History here is deeply tied to the Cold War. In 301 00:14:29.600 --> 00:14:33.720 the nineteen seventies, the Department of Defense funded the Arpennet project. 302 00:14:34.000 --> 00:14:37.519 They needed a communications network that could survive a catastrophic event. 303 00:14:37.639 --> 00:14:40.600 The underlying logic had to be so robust that if 304 00:14:40.600 --> 00:14:43.759 half the country's infrastructure was wiped out in a nuclear strike, 305 00:14:44.279 --> 00:14:47.360 the surviving computers could automatically route data around the crater 306 00:14:47.759 --> 00:14:49.679 to find a new path to the destination. 307 00:14:50.000 --> 00:14:53.080 So they engineered a four layer architecture known as the 308 00:14:53.159 --> 00:14:58.279 DoD model process application host to host or transport Internet 309 00:14:58.320 --> 00:14:59.480 and network access. 310 00:15:00.000 --> 00:15:03.000 The true brilliance of this model is its open systems 311 00:15:03.000 --> 00:15:03.879 approach right. 312 00:15:03.759 --> 00:15:07.440 Exactly Unlike proprietary tech, where every piece of hardware has 313 00:15:07.440 --> 00:15:11.399 come from the same vendor, TCPIP is completely agnostic at 314 00:15:11.440 --> 00:15:12.480 the bottom layer, so. 315 00:15:12.440 --> 00:15:14.879 The physical network access layer just does not care what 316 00:15:14.919 --> 00:15:15.559 the medium is. 317 00:15:15.720 --> 00:15:19.000 Right, the upper layers process the digital data exactly the 318 00:15:19.039 --> 00:15:21.759 same way, whether that bottom layer is a copper telephone wire, 319 00:15:22.120 --> 00:15:25.919 a transatlantic fiber optic glass tube, or a modern Wi 320 00:15:25.919 --> 00:15:28.320 Fi radio wave bouncing around your living room. 321 00:15:28.159 --> 00:15:31.600 And understanding that nineteen seventies layered architecture is actually the 322 00:15:31.679 --> 00:15:34.679 secret to troubleshooting your own home Wi Fi today, it 323 00:15:34.759 --> 00:15:35.279 really is. 324 00:15:35.679 --> 00:15:38.120 When your laptop suddenly cannot load a web page, you 325 00:15:38.200 --> 00:15:42.960 troubleshoot systematically, layer by layer. First, the physical network access layer, 326 00:15:43.159 --> 00:15:45.000 is the Wi Fi radio actually connected? 327 00:15:45.159 --> 00:15:47.519 Next the Internet layer, did the router assign you a 328 00:15:47.559 --> 00:15:48.639 valid IP address? 329 00:15:48.679 --> 00:15:51.559 Then up to the application layer, is the browser failing 330 00:15:51.600 --> 00:15:53.960 to resolve the website name? It gives you a mental 331 00:15:54.000 --> 00:15:56.399 map to isolate the exact point of failure. 332 00:15:56.759 --> 00:15:59.279 Let's zoom in on that top layer, the application layer. 333 00:15:59.720 --> 00:16:03.480 These are the unsung background protocols making our digital lives function. 334 00:16:04.120 --> 00:16:06.519 Let's start with DNS, the Domain Name system. 335 00:16:06.720 --> 00:16:10.399 Because computers do not understand English words, they only understand numbers, 336 00:16:10.519 --> 00:16:12.200 specifically IP addresses. 337 00:16:12.240 --> 00:16:14.879 But no one wants to type a random string of 338 00:16:14.960 --> 00:16:18.200 numbers into their browser to check the news. So DNS 339 00:16:18.320 --> 00:16:20.559 is basically the Internet's phone book exactly. 340 00:16:20.799 --> 00:16:24.480 It translates human readable URLs, what the networking world calls 341 00:16:24.559 --> 00:16:28.759 fully qualified domain names into the exact IP addresses the 342 00:16:28.799 --> 00:16:30.080 machines need to connect. 343 00:16:30.399 --> 00:16:33.519 But before your phone can even access that DNS phone book, 344 00:16:33.559 --> 00:16:36.840 it needs its own IP address. That's the job of DHCP, 345 00:16:37.080 --> 00:16:39.000 the dynamic host configuration protocol. 346 00:16:39.120 --> 00:16:41.399 Right when you walk into a coffee shop and your 347 00:16:41.399 --> 00:16:44.240 phone connects to the Wi Fi, it has no identity 348 00:16:44.240 --> 00:16:46.919 on that network. It cannot send a targeted message to 349 00:16:46.960 --> 00:16:49.279 the router to ask for an address because it does 350 00:16:49.279 --> 00:16:50.960 not have a return address yet, so it. 351 00:16:50.919 --> 00:16:53.600 Literally has to shout into the digital void. The phone 352 00:16:53.600 --> 00:16:57.039 sends out a massive broadcast message to the entire local network, 353 00:16:57.039 --> 00:16:59.879 basically disagreement. Is there a DHCP server out there that 354 00:16:59.919 --> 00:17:01.279 can give me an IP address? 355 00:17:01.559 --> 00:17:03.480 And this kicks off what is known as the door 356 00:17:03.519 --> 00:17:09.359 our process Discover, Offer, request, acknowledge. Your phone's shout is 357 00:17:09.400 --> 00:17:10.599 the discover message, and. 358 00:17:10.559 --> 00:17:12.960 The router hears it and replies with an offer of 359 00:17:13.000 --> 00:17:14.880 an available IP address. 360 00:17:15.079 --> 00:17:19.000 Your phone then formally requests to lock in that specific address, 361 00:17:19.240 --> 00:17:22.960 and the router acknowledges the lease. This four step negotiation 362 00:17:23.160 --> 00:17:24.519 happens in a fraction of a second. 363 00:17:24.799 --> 00:17:28.000 But if that DHCP server is frozen or dead, the 364 00:17:28.039 --> 00:17:31.519 phone panics. It realizes no one is answering the shout, 365 00:17:31.720 --> 00:17:35.599 so it automatically assigns itself an APAPA address automatic private 366 00:17:35.599 --> 00:17:36.359 IP addressing. 367 00:17:36.440 --> 00:17:38.839 It just pulls a random address in the one sixty 368 00:17:38.920 --> 00:17:40.559 nine point two five four range. 369 00:17:40.640 --> 00:17:42.599 Yeah, if you are ever trying to fix a broken 370 00:17:42.640 --> 00:17:45.000 Internet connection and you look at your computer settings and 371 00:17:45.000 --> 00:17:47.200 see an IP address starting with one sixty nine point 372 00:17:47.200 --> 00:17:49.759 twenty five four, it is a massive red flag. 373 00:17:49.920 --> 00:17:52.559 It instantly tells you the device is completely isolated and 374 00:17:52.559 --> 00:17:56.240 cannot reach the router. It is an invaluable diagnostic clue, and. 375 00:17:56.200 --> 00:17:59.440 The application layer also dictates how we remotely manage these devices. 376 00:17:59.519 --> 00:18:03.559 Yes, for decades, engineers use telnet, which is incredibly lightweight 377 00:18:03.559 --> 00:18:07.440 but fundamentally flawed because it sends every keystroke in clear text. 378 00:18:07.400 --> 00:18:10.200 So if an engineer types of password, anyone listening on 379 00:18:10.240 --> 00:18:12.720 the local network can intercept and read it exactly. 380 00:18:13.240 --> 00:18:17.319 Today, that has been entirely replaced by SSH secure shell, 381 00:18:17.720 --> 00:18:20.119 which encrypts the entire remote session. 382 00:18:20.240 --> 00:18:22.359 Now, the protocol that really caught me off guard in 383 00:18:22.400 --> 00:18:25.759 this section is MTP, the Network Time Protocol. 384 00:18:25.960 --> 00:18:28.359 Oh. Yeah, NTP is crucial. 385 00:18:28.440 --> 00:18:30.599 It reaches out to atomic clocks on the Internet to 386 00:18:30.599 --> 00:18:34.519 perfectly synchronize your device's internal clock. But honestly, in a 387 00:18:34.519 --> 00:18:38.000 world of deep packet inspecting firewalls and fiber optic lasers, 388 00:18:38.519 --> 00:18:40.960 why is simply knowing what time it is considered a 389 00:18:41.000 --> 00:18:42.079 mission critical function. 390 00:18:42.359 --> 00:18:44.839 It only seems trivial until you look at how digital 391 00:18:44.839 --> 00:18:48.759 security and databases function really just the time. Yeah, almost 392 00:18:48.759 --> 00:18:53.440 every encrypted transaction and database entry relies entirely on exact timestamps. 393 00:18:53.839 --> 00:18:56.359 If a financial service clock drifts out of sync by 394 00:18:56.400 --> 00:18:58.039 just a few seconds compared to the rest of the 395 00:18:58.039 --> 00:19:01.000 banking network, it might log a cash withdrawal is happening 396 00:19:01.039 --> 00:19:03.599 before the direct deposit that actually funded the account. 397 00:19:03.640 --> 00:19:06.039 Oh wow, the database logic just collapses. 398 00:19:06.279 --> 00:19:11.079 Furthermore, modern website security certificates are time bound. If your 399 00:19:11.079 --> 00:19:14.960 computer's internal clock gets reset and thinks the years twenty eighteen, 400 00:19:15.400 --> 00:19:18.480 your browser will reject every secure website you try to 401 00:19:18.559 --> 00:19:22.119