WEBVTT 1 00:00:00.040 --> 00:00:02.960 All right, let's dive into this one networking all in 2 00:00:03.000 --> 00:00:06.120 one for dummies. Hum, you really want to get into 3 00:00:06.160 --> 00:00:07.519 the guts of computer networks? 4 00:00:07.519 --> 00:00:10.119 Oh yeah, there's a lot to unpack here. It's incredible 5 00:00:10.160 --> 00:00:12.439 how much we depend on networks without even thinking about 6 00:00:12.480 --> 00:00:13.279 it for sure. 7 00:00:13.839 --> 00:00:16.280 So the book kicks off with this little story about 8 00:00:16.320 --> 00:00:20.039 those old school computers mainframes. You know, some were so 9 00:00:20.239 --> 00:00:22.640 huge they needed liquid nitrogen to stay cool. 10 00:00:22.719 --> 00:00:25.679 Wow, that's wild. I can't imagine a plumber being on 11 00:00:25.719 --> 00:00:27.359 the itteam seriously. 12 00:00:27.600 --> 00:00:30.199 So before we get too far, can you remind us 13 00:00:30.239 --> 00:00:33.520 why networks are so important? I mean, beyond saving us 14 00:00:33.520 --> 00:00:35.439 from carrying floppy disks around. 15 00:00:35.880 --> 00:00:38.479 Well, think of a network as a way to boost efficiency. 16 00:00:38.719 --> 00:00:42.240 We can share resources like printers, internet access, you know, 17 00:00:42.439 --> 00:00:45.280 and of course files, so instead of everyone being isolated, 18 00:00:45.320 --> 00:00:47.719 we can all work together and access information easily. 19 00:00:47.880 --> 00:00:50.759 Okay, makes sense. So the book also talks about different 20 00:00:50.840 --> 00:00:53.359 types of networks, and it seems like most businesses use 21 00:00:53.399 --> 00:00:57.000 those heavy duty dedicated servers, but for smaller setups it's 22 00:00:57.119 --> 00:00:59.200 more common to see peer to peer networks. What's the 23 00:00:59.240 --> 00:00:59.840 difference there? 24 00:01:00.079 --> 00:01:02.439 It all comes down to how the work is spread out. 25 00:01:03.000 --> 00:01:06.480 With a dedicated server. You've got these specialized machines and 26 00:01:06.560 --> 00:01:09.439 their only job is to provide services to other computers. 27 00:01:09.439 --> 00:01:11.599 We call them clients. It's kind of like a five 28 00:01:11.599 --> 00:01:14.400 star hotel where you've got a whole staff dedicated to 29 00:01:14.400 --> 00:01:15.599 taking care of your every need. 30 00:01:15.719 --> 00:01:18.480 Ooh fancy. So what about peer to peer? 31 00:01:18.519 --> 00:01:21.599 Then? Peer to peer is more like a potluck dinner. 32 00:01:21.879 --> 00:01:24.519 Every computer can share stuff with others, which makes it 33 00:01:24.599 --> 00:01:27.359 super easy to set up, pretty simple to manage. Great 34 00:01:27.359 --> 00:01:29.519 for a small group, but probably not the best for 35 00:01:29.560 --> 00:01:30.319 a big company. 36 00:01:30.640 --> 00:01:33.040 I see, I see. So whether it's a fancy hotel 37 00:01:33.159 --> 00:01:35.680 or a potluck, we still need the right hardware to 38 00:01:35.680 --> 00:01:37.879 make it work. And this book, it keeps saying that 39 00:01:37.959 --> 00:01:41.439 switches are like the core of a network. Can you 40 00:01:41.480 --> 00:01:44.239 explain what these things do and why we need them? 41 00:01:44.359 --> 00:01:47.760 Absolutely? Cables those are like the roads connecting everything. Then 42 00:01:47.799 --> 00:01:50.439 you've got patch panels they're like traffic signs, and then 43 00:01:50.760 --> 00:01:53.120 the switches they're like the traffic cops making sure the 44 00:01:53.159 --> 00:01:55.719 data goes to the right place. Without them, you'd have 45 00:01:55.920 --> 00:01:58.680 data crashes everywhere and your network would just stop. 46 00:01:58.920 --> 00:02:01.719 So basically, switch which are the unsung heroes of a 47 00:02:01.760 --> 00:02:02.920 smooth running network. 48 00:02:03.159 --> 00:02:05.079 You got it and the way they do it is 49 00:02:05.120 --> 00:02:08.400 actually pretty cool. Every device on a network it has 50 00:02:08.479 --> 00:02:12.599 this unique id called a massy address. It's like a fingerprint. 51 00:02:12.719 --> 00:02:15.560 And the switches they build a table of these addresses 52 00:02:15.879 --> 00:02:18.039 so they know exactly where to send each piece of data. 53 00:02:18.599 --> 00:02:19.520 No more crashes. 54 00:02:19.639 --> 00:02:22.000 Wow. So that's how data finds its way around. 55 00:02:22.080 --> 00:02:22.319 Now. 56 00:02:22.560 --> 00:02:25.360 The book also talks about Ethernet. That's the main protocol 57 00:02:25.360 --> 00:02:28.560 for networks, right, and it uses this analogy of people 58 00:02:28.639 --> 00:02:31.840 shouting in a crowded room. Kind of chaotic, to be honest, 59 00:02:32.000 --> 00:02:32.400 it is. 60 00:02:32.759 --> 00:02:35.400 Early Ethernet had a lot of problems with those data collisions. 61 00:02:35.439 --> 00:02:38.360 Things would slow to a crawl. But things have evolved 62 00:02:38.360 --> 00:02:41.120 a lot. We've got fast Ethernet and gigabit Ethernet now. 63 00:02:41.360 --> 00:02:43.479 Think of it like going from dial up internet to 64 00:02:43.639 --> 00:02:46.280 super fast broadband. A huge improvement. 65 00:02:46.520 --> 00:02:49.000 Right, So if you're still stuck with that old ten 66 00:02:49.039 --> 00:02:52.319 melip Ethernet, it might be time for an upgrade, for sure. 67 00:02:52.599 --> 00:02:54.520 It'd be like holding onto your old flip phone when 68 00:02:54.560 --> 00:02:57.719 everyone else has the latest smartphone. And to really understand 69 00:02:57.759 --> 00:03:00.319 how much more efficient modern Ethernet is, we need to 70 00:03:00.319 --> 00:03:01.479 talk about hubs and switches. 71 00:03:01.520 --> 00:03:03.599 All right, I'm all yours. What's the deal with hubs? 72 00:03:03.800 --> 00:03:08.319 Imagine a hub like a megaphone in that crowded room, right, 73 00:03:08.400 --> 00:03:11.599 it's just amplifying everyone's voice and everyone hears everything, which 74 00:03:11.680 --> 00:03:15.439 leads to chaos. But a switch, it's like having separate 75 00:03:15.520 --> 00:03:18.199 rooms for each conversation. No more collisions. 76 00:03:18.240 --> 00:03:22.039 Wow. So switches bring order to the chaos. And speaking 77 00:03:22.080 --> 00:03:26.479 of order, let's shift gears to something a bit more serious, cybersecurity. 78 00:03:27.159 --> 00:03:30.280 The book makes it clear that cybersecurity is not an afterthought. 79 00:03:30.319 --> 00:03:33.120 It should be built into your network right from the beginning. 80 00:03:33.199 --> 00:03:34.439 Why is that so important? 81 00:03:34.759 --> 00:03:37.039 Well, you can think of your network like a fortress. 82 00:03:37.800 --> 00:03:40.639 You wouldn't build a fortress with weak walls and unlocked gates, 83 00:03:40.680 --> 00:03:44.159 would you. Cybersecurity is all about building those strong defenses, 84 00:03:44.479 --> 00:03:47.479 but also having a solid plan for recovery just in 85 00:03:47.520 --> 00:03:49.800 case someone does manage to break in, right. 86 00:03:49.759 --> 00:03:51.919 And the book talks about two main parts to a 87 00:03:51.960 --> 00:03:55.759 good cybersecurity strategy, protection and recovery. What does that mean? 88 00:03:55.840 --> 00:03:56.400 In practice? 89 00:03:56.560 --> 00:04:00.280 Protection that's your first line of defense. Strong passwords, you know, 90 00:04:00.360 --> 00:04:03.360 multi factor authentication, think of like having multiple locks on 91 00:04:03.400 --> 00:04:06.400 your door. And then there's data protection, which is all 92 00:04:06.439 --> 00:04:09.039 about making sure that only the right, people can access 93 00:04:09.039 --> 00:04:10.439 sensitive information. 94 00:04:10.120 --> 00:04:12.520 So it's all about keeping the bad guys out exactly. 95 00:04:13.159 --> 00:04:16.519 But even with the best defenses, sometimes things slip through. 96 00:04:16.600 --> 00:04:19.360 That's where recovery comes in. And the most important part 97 00:04:19.360 --> 00:04:22.480 of that is backups. Not just any backups. They need 98 00:04:22.519 --> 00:04:25.360 to be complete, up to date, and you need multiple copies. 99 00:04:25.439 --> 00:04:26.959 Redundancy is key. Yeah. 100 00:04:27.000 --> 00:04:29.720 The book shares a story about someone who restored their 101 00:04:29.759 --> 00:04:32.560 data from a backup, but it turns out the backup 102 00:04:32.639 --> 00:04:36.160 was already infected with malware. So having multiple generations of 103 00:04:36.199 --> 00:04:38.800 backups is crucial just in case you need to go 104 00:04:38.959 --> 00:04:40.800 way back in time to find a clean copy. 105 00:04:41.040 --> 00:04:43.439 Like having checkpoints in a video game. You know, if 106 00:04:43.439 --> 00:04:45.439 you mess up, you don't have to start from scratch, 107 00:04:45.439 --> 00:04:46.720 you can just go back to a safe point. 108 00:04:46.839 --> 00:04:49.839 Makes sense. Okay, so backups are officially on my to 109 00:04:49.839 --> 00:04:52.560 do list. Now let's switch gears again and talk about servers. 110 00:04:52.600 --> 00:04:55.560 They're like the brains of the whole operation, right. The 111 00:04:55.600 --> 00:04:59.199 book says they handle everything from sharing files to running 112 00:04:59.199 --> 00:05:03.040 accounting service says basically the backbone of any network. 113 00:05:03.160 --> 00:05:06.160 That's right. Servers are like the central library and the 114 00:05:06.199 --> 00:05:09.399 main office for your whole network. They store and process 115 00:05:09.439 --> 00:05:12.120 the data that keeps everything running. I see in servers. 116 00:05:12.120 --> 00:05:13.879 They come in different shapes and sizes. Right, there are 117 00:05:13.879 --> 00:05:17.279 tower cases, rack mount servers, and those blade servers that 118 00:05:17.319 --> 00:05:19.480 you see in data centers. What's the difference between those. 119 00:05:20.120 --> 00:05:22.399 It's kind of like choosing the right vehicle for the job. 120 00:05:22.759 --> 00:05:26.040 A tower server is like a pickup truck, versatile, great 121 00:05:26.079 --> 00:05:29.439 for smaller tasks. Rack mount servers are more like semi drugs, 122 00:05:29.480 --> 00:05:31.959 you know, built for heavy lifting, easy to stack in 123 00:05:32.000 --> 00:05:34.439 a data center. And then you've got those blade servers. 124 00:05:34.439 --> 00:05:38.720 Those are like Formula one race cars, incredibly powerful, very compact, 125 00:05:39.000 --> 00:05:41.560 but built for very specific high performance needs. 126 00:05:42.040 --> 00:05:45.199 Ah, I get it. So you pick your server based 127 00:05:45.240 --> 00:05:47.839 on the size and the needs of your network. Now, 128 00:05:47.839 --> 00:05:52.160 this is where things get really interesting. Virtualization. The book 129 00:05:52.199 --> 00:05:55.079 explains how you can have a single physical server running 130 00:05:55.240 --> 00:05:58.800 multiple virtual servers. It's like having an entire data center 131 00:05:58.879 --> 00:06:00.160 squeezed into one box. 132 00:06:00.360 --> 00:06:03.120 Yeah, virtualization is a really powerful concept. Think of it 133 00:06:03.160 --> 00:06:05.920 like building an apartment building. Instead of separate houses, you 134 00:06:05.920 --> 00:06:08.879 can use the same land and infrastructure to create multiple units. 135 00:06:09.279 --> 00:06:11.079 You get much more out of your resources. 136 00:06:11.399 --> 00:06:14.199 That's a great analogy. But the book warns that virtualization 137 00:06:14.600 --> 00:06:18.279 needs a lot of horsepower. We're talking dual processors, tons 138 00:06:18.279 --> 00:06:22.279 of RAM those virtual servers, they're hungry for resources. 139 00:06:22.399 --> 00:06:24.920 Absolutely, It's like building that apartment complex. You need a 140 00:06:24.959 --> 00:06:28.120 really strong foundation to support all those units. And speaking 141 00:06:28.120 --> 00:06:32.360 of powerful resources, let's talk about something that's basically synonymous 142 00:06:32.399 --> 00:06:35.519 with modern networking, cloud computing. 143 00:06:35.759 --> 00:06:38.680 Yes, the book talks about all the benefits of the cloud, 144 00:06:38.920 --> 00:06:42.040 things like cost effectiveness, being able to scale up or 145 00:06:42.040 --> 00:06:46.319 down easily, and of course flexibility. It's like having access 146 00:06:46.360 --> 00:06:49.160 to a supercomputer whenever you need it, but without the 147 00:06:49.279 --> 00:06:50.160 huge price tag. 148 00:06:50.279 --> 00:06:53.040 Cloud computing has really change how we access and manage 149 00:06:53.079 --> 00:06:56.439 computing resources. Instead of owning and maintaining your own equipment, 150 00:06:56.800 --> 00:06:59.879 you can tap into this vast pool of resources provide 151 00:07:00.079 --> 00:07:03.560 by companies like Amazon and Microsoft. It's like renting a 152 00:07:03.600 --> 00:07:06.319 car instead of buying one. You only pay for what 153 00:07:06.360 --> 00:07:08.000 you use and you don't have to worry about all 154 00:07:08.040 --> 00:07:08.560 the maintenance. 155 00:07:08.759 --> 00:07:11.120 And there are different types of cloud computing too, right 156 00:07:11.720 --> 00:07:16.040 the book mentions iis pass and sauce. It's like choosing 157 00:07:16.079 --> 00:07:18.600 different levels of service at a restaurant. Do you want 158 00:07:18.600 --> 00:07:20.959 to cook the whole meal yourself or just have the 159 00:07:20.959 --> 00:07:22.279 finished dish brought to you. 160 00:07:22.560 --> 00:07:25.759 That's a great analogy. I gives you all the ingredients, 161 00:07:25.839 --> 00:07:28.079 you know, the servers, the storage, and you build your 162 00:07:28.079 --> 00:07:31.000 own thing. Pi as gives you a preset kitchen with 163 00:07:31.120 --> 00:07:33.759 all the tools you need to create your application, and 164 00:07:33.879 --> 00:07:37.000 sauce just serves you a delicious, ready to eat meal. 165 00:07:37.319 --> 00:07:39.800 So you choose the level of control you're comfortable with. 166 00:07:40.120 --> 00:07:44.120 Exactly. To make it even clearer, think about old school 167 00:07:44.120 --> 00:07:48.120 accounting software versus a cloud based service like Google Workspace. 168 00:07:48.439 --> 00:07:51.240 It's like the difference between owning a physical encyclopedia and 169 00:07:51.279 --> 00:07:53.240 having access to Wikipedia online. 170 00:07:53.319 --> 00:07:57.079 Ah, I see cloud based services are way more convenient, 171 00:07:57.439 --> 00:08:00.319 But the book does mention some security concerns with the cloud. 172 00:08:00.639 --> 00:08:04.079 Public clouds are super convenient, but they're inherently less secure, right. 173 00:08:04.240 --> 00:08:06.319 That's like trusting a stranger with your house keys. 174 00:08:06.720 --> 00:08:09.480 Security is definitely something to think about in the cloud. 175 00:08:10.040 --> 00:08:13.240 Public clouds are shared environments, which means your data could 176 00:08:13.279 --> 00:08:16.399 be at risk if the provider security isn't good enough. 177 00:08:17.079 --> 00:08:19.879 Think of it like living in an apartment building. You 178 00:08:19.920 --> 00:08:22.439 need to be extra careful about locking your doors because 179 00:08:22.480 --> 00:08:24.240 you're sharing space with other people. 180 00:08:24.759 --> 00:08:29.279 Right, So convenience comes with some added responsibility. Now, let's 181 00:08:29.319 --> 00:08:31.319 get into the nuts and bolts of how the Internet 182 00:08:31.399 --> 00:08:36.480 actually works. The book starts with TCPIP, which is like 183 00:08:36.639 --> 00:08:39.360 the language of the Internet right. Uses a four layer 184 00:08:39.399 --> 00:08:42.080 model to break down how data is sent and received, 185 00:08:42.600 --> 00:08:45.679 kind of similar to the OSI model, but a bit simpler. 186 00:08:45.799 --> 00:08:48.799 TCPIP is really the foundation of the Internet. It started 187 00:08:48.879 --> 00:08:50.919 in the Department of Defense as a way to connect 188 00:08:51.000 --> 00:08:54.559 different networks, and it was designed to be incredibly resilient. 189 00:08:54.799 --> 00:08:57.919 Imagine a network that could survive a nuclear attack. That 190 00:08:57.960 --> 00:08:58.360 was the goal. 191 00:08:58.480 --> 00:09:01.559 Wow, that's some serious stuff, and it's amazing how TCPIP 192 00:09:01.639 --> 00:09:04.519 has grown from just connecting a few networks to powering 193 00:09:04.519 --> 00:09:05.240 the whole Internet. 194 00:09:05.440 --> 00:09:08.720 It really shows how flexible and adaptable it is. And 195 00:09:08.759 --> 00:09:10.879 to understand how it all works, we need to talk 196 00:09:10.919 --> 00:09:14.840 about IP addresses. Those are the numerical addresses that identified 197 00:09:14.919 --> 00:09:17.159 devices on a network. You can think of them like 198 00:09:17.200 --> 00:09:20.080 your home address. They tell data packets exactly where to go. 199 00:09:20.440 --> 00:09:24.200 Right, and the book breaks down the structure of IP addresses. 200 00:09:24.240 --> 00:09:26.840 They're made up of four octets, each one representing a 201 00:09:26.840 --> 00:09:30.559 binary number. There's even an analogy to make converting between 202 00:09:30.559 --> 00:09:33.799 binary and decimal easier. To understand. It's like converting between 203 00:09:33.879 --> 00:09:37.080 different units of measurement, like you know, inches to centimeters. 204 00:09:37.399 --> 00:09:39.679 Yeah, that's a helpful way to visualize it. Just like 205 00:09:39.720 --> 00:09:42.159 twelve inches is equal to one foot. Eight bits are 206 00:09:42.159 --> 00:09:44.519 equal to one byte, and those bytes, those are the 207 00:09:44.519 --> 00:09:46.120 building blocks of IP addresses. 208 00:09:46.159 --> 00:09:49.080 Okay, so IP addresses are like the GPS coordinates for 209 00:09:49.200 --> 00:09:52.200 data packets. A book also mentions different classes of IP 210 00:09:52.360 --> 00:09:56.159 addresses A, B, C, D, and E. Classes A, B 211 00:09:56.399 --> 00:09:58.840 and C are for regular devices, while D and E 212 00:09:58.919 --> 00:10:00.000 are used for special. 213 00:09:59.720 --> 00:10:03.200 Per Think of them like different kinds of roads. Class 214 00:10:03.200 --> 00:10:07.000 A addresses are like highways they can handle tons of traffic. 215 00:10:07.320 --> 00:10:11.120 CLASSA addresses are more like local streets, good for smaller networks. 216 00:10:11.559 --> 00:10:13.200 And then you've got D and E, which are like 217 00:10:13.519 --> 00:10:17.679 restricted access roads used for things like multicasting and research. 218 00:10:18.000 --> 00:10:21.320 I see. So we've got these different classes of IP addresses. 219 00:10:21.600 --> 00:10:23.919 But what happens when you have a really big network 220 00:10:23.960 --> 00:10:26.919 and you need to use those addresses efficiently. That's where 221 00:10:26.960 --> 00:10:29.039 subnetting comes in, right exactly. 222 00:10:29.320 --> 00:10:31.759 Subnetting is like taking a big piece of land and 223 00:10:31.799 --> 00:10:34.399 dividing it up into smaller plots. It lets you break 224 00:10:34.399 --> 00:10:38.080 a network into smaller easier to manage subnetworks, each with 225 00:10:38.159 --> 00:10:39.519 its own range of IP. 226 00:10:39.360 --> 00:10:43.440 Addresses, and the book connects this to vlands virtual local 227 00:10:43.480 --> 00:10:46.480 area networks. They're different concepts, but they often go hand 228 00:10:46.519 --> 00:10:48.399 in hand, right Can you explain that a little more? 229 00:10:48.759 --> 00:10:51.480 Think of vlands like virtual offenses. You can build on 230 00:10:51.519 --> 00:10:54.960 your land. You can group devices logically, even if they're 231 00:10:54.960 --> 00:10:57.840 not physically close to each other. This makes things more 232 00:10:57.840 --> 00:11:01.799 secure by isolating traffic, and it can also improve performance 233 00:11:01.879 --> 00:11:02.960 by reducing congestion. 234 00:11:03.279 --> 00:11:06.639 So it's like creating neighborhoods within your network exactly. 235 00:11:06.799 --> 00:11:09.039 And to connect all those neighborhoods to the outside world, 236 00:11:09.320 --> 00:11:14.039 we use something called network address translation or NAT okay NAT. 237 00:11:14.519 --> 00:11:17.159 The book explains how it allows devices on a private 238 00:11:17.200 --> 00:11:20.279 network to connect to the public Internet. It's like having 239 00:11:20.279 --> 00:11:23.480 a receptionist who handles all the incoming and outgoing calls 240 00:11:23.519 --> 00:11:24.240 for a company. 241 00:11:24.519 --> 00:11:28.559 Good analogy. NAT is like a middleman converting private IP 242 00:11:28.679 --> 00:11:32.480 addresses to public IP addresses and vice versa. This helps 243 00:11:32.519 --> 00:11:35.559 conserve public IP addresses and also adds a layer of 244 00:11:35.600 --> 00:11:38.519 security by hiding internal devices from the outside world. 245 00:11:38.679 --> 00:11:41.919 And the book mentioned something called ephemeral ports, which are 246 00:11:42.080 --> 00:11:44.480 part of how NAT works. It's like giving each call 247 00:11:44.559 --> 00:11:47.879 a unique extension number, so that receptionist knows which internal 248 00:11:47.919 --> 00:11:49.639 device to connect it to exactly. 249 00:11:50.039 --> 00:11:52.240 Ephemeral ports allow the neat router to keep track of 250 00:11:52.320 --> 00:11:56.080 multiple connections from the internal network. Each outgoing connection gets 251 00:11:56.080 --> 00:11:59.559 a unique ephemeral port number, so the incoming responses are 252 00:11:59.600 --> 00:12:00.960 sent back to the right device. 253 00:12:01.360 --> 00:12:03.600 So it's a clever way to manage all those conversations 254 00:12:03.639 --> 00:12:06.320 happening at the same time. Now, last, but not least, 255 00:12:06.360 --> 00:12:09.759 let's talk about DNS, or the Domain Name system. The 256 00:12:09.799 --> 00:12:13.279 book says it's really important because, well, imagine trying to 257 00:12:13.279 --> 00:12:16.039 remember a long string of numbers instead of a website name. 258 00:12:16.159 --> 00:12:19.679 Not very user friendly, and it explains how DNS uses 259 00:12:19.720 --> 00:12:22.600 a hierarchical structure kind of like a phone book for 260 00:12:22.639 --> 00:12:23.120 the Internet. 261 00:12:23.360 --> 00:12:26.600 DNS is what makes the Internet user friendly. It translates 262 00:12:26.919 --> 00:12:30.840 those human readable domain names like Google dot com into 263 00:12:30.879 --> 00:12:34.399 those numerical IP addresses that computers understand. 264 00:12:34.200 --> 00:12:37.440 And the book explains how those DNS queries actually work. 265 00:12:37.759 --> 00:12:40.600 It's like asking a librarian for a book. They might 266 00:12:40.639 --> 00:12:42.720 know exactly where it is, or they might need to 267 00:12:42.720 --> 00:12:45.279 ask other librarians to help them find it exactly. 268 00:12:45.519 --> 00:12:49.519 DNS servers can answer queries in two ways, recursively or iteratively. 269 00:12:50.080 --> 00:12:52.759 Recursive queries are like asking the librarian to find the 270 00:12:52.759 --> 00:12:55.639 book for you. Iterative queries are more like asking for 271 00:12:55.759 --> 00:12:58.120 directions to the section where the book is located. 272 00:12:58.320 --> 00:13:02.120 Got it. So, DNS is like the Internet's directory assistance. 273 00:13:02.200 --> 00:13:04.080 It helps us find what we're looking for without having 274 00:13:04.120 --> 00:13:06.399 to memorize a bunch of numbers exactly. 275 00:13:07.200 --> 00:13:09.600 And with that, we've covered some of the basic building 276 00:13:09.679 --> 00:13:13.519 blocks of computer networks. But there's so much more to explore. 277 00:13:14.080 --> 00:13:16.919 Ready to go deeper, absolutely and ready for the next 278 00:13:17.000 --> 00:13:17.720 layer of knowledge. 279 00:13:17.759 --> 00:13:20.200 All right, So let's get practical. Let's talk about setting 280 00:13:20.279 --> 00:13:24.240 up a home network. This book it's your guide, and 281 00:13:24.320 --> 00:13:26.679 right off the bat, it says planning is key. 282 00:13:27.039 --> 00:13:28.919 Yeah, you can't just plug things in and hope for 283 00:13:28.960 --> 00:13:32.039 the best. The book wants you to really think about, 284 00:13:32.080 --> 00:13:34.679 like what you're using your network for, how many people 285 00:13:34.720 --> 00:13:36.240 are going to be on it, and whether you're going 286 00:13:36.240 --> 00:13:38.000 mostly wired or wireless. 287 00:13:38.200 --> 00:13:41.639 It's kind of like designing a house. You wouldn't just 288 00:13:41.639 --> 00:13:44.679 start building without a blueprint, right thinking about how you'll 289 00:13:44.720 --> 00:13:47.320 actually use your network. It helps you choose the right 290 00:13:47.360 --> 00:13:49.200 equipment and set up the right way. Like if you're 291 00:13:49.240 --> 00:13:52.000 a gamer, you'll eat a router that can handle you know, 292 00:13:52.080 --> 00:13:53.200 speed and low latency. 293 00:13:53.399 --> 00:13:56.360 Makes total sense. So once you have your blueprint, what 294 00:13:56.399 --> 00:13:59.159 are the essential parts of a typical home network? Like, 295 00:13:59.159 --> 00:14:00.360 what do you absolutely need? 296 00:14:00.639 --> 00:14:04.080 Okay? So the heart of your network, that's the router. 297 00:14:04.279 --> 00:14:06.720 It's the gateway between all your devices at home and 298 00:14:06.759 --> 00:14:09.960 the Internet. Think of it like border control for your network. 299 00:14:10.120 --> 00:14:12.519 And these days most routers have a built in firewall 300 00:14:12.559 --> 00:14:13.960 and a DHCP server. 301 00:14:13.919 --> 00:14:17.240 Right yep, exactly. The firewalls like a security guard, blocking 302 00:14:17.240 --> 00:14:18.799 any shady traffic from getting in. 303 00:14:19.480 --> 00:14:23.879 And the DHCP server is like an automated address book. 304 00:14:23.919 --> 00:14:26.639 I guess it gives each device on your network its 305 00:14:26.720 --> 00:14:29.159 own unique IP address. 306 00:14:28.919 --> 00:14:31.879 So no more manually configuring IP addresses. Thank goodness. That 307 00:14:31.960 --> 00:14:35.440 sounds like a headache. What about connecting wireless devices? How 308 00:14:35.440 --> 00:14:36.639 do those get on the network? 309 00:14:36.799 --> 00:14:39.720 For that, you need a wireless access point a WA. 310 00:14:39.879 --> 00:14:42.240 It's basically like setting up a Wi Fi hotspot in 311 00:14:42.279 --> 00:14:45.399 your home. So your phone, laptops, tablets, they can all 312 00:14:45.399 --> 00:14:48.240 connect without wires. And lots of routers these days actually 313 00:14:48.320 --> 00:14:51.120 have WPS built right in, so you get wired and 314 00:14:51.360 --> 00:14:52.519 wireless all in one box. 315 00:14:52.720 --> 00:14:56.080 Nice, very convenient. Now, we talked about switches before, but 316 00:14:56.200 --> 00:14:58.639 this book it really emphasizes how important they are in 317 00:14:58.679 --> 00:15:01.799 a home network too. Those traffic cops making sure data 318 00:15:01.799 --> 00:15:04.799 flows smoothly between all your devices, that's right, Just like 319 00:15:04.840 --> 00:15:08.039 in a bigger network, switches prevent those data collisions and 320 00:15:08.080 --> 00:15:11.879 help everything run faster. The book also talks about managed 321 00:15:11.960 --> 00:15:15.720 versus unmanaged switches. Unmanaged switches are like set it and 322 00:15:15.759 --> 00:15:19.519 forget it, perfect for basic home networks, but managed switches 323 00:15:19.720 --> 00:15:21.399 they give you way more control. 324 00:15:21.840 --> 00:15:24.519 So if you want to really fine tune your network, 325 00:15:24.799 --> 00:15:27.080 a managed switch is the way to go exactly. 326 00:15:27.240 --> 00:15:30.000 You can do things like prioritize certain types of traffic, 327 00:15:30.200 --> 00:15:33.879 like for streaming video or gaming, or you could even 328 00:15:33.919 --> 00:15:36.480 create separate virtual networks for different devices. 329 00:15:36.679 --> 00:15:40.000 And speaking of being organized, the book stresses how important 330 00:15:40.000 --> 00:15:43.320 network diagrams are. It's like having a blueprint for your 331 00:15:43.320 --> 00:15:47.000 digital fortress, right, so you can easily troubleshoot problems and 332 00:15:47.039 --> 00:15:48.200 make changes when you need to. 333 00:15:48.320 --> 00:15:50.360 Oh, network diagrams are super helpful. They give you a 334 00:15:50.440 --> 00:15:52.639 visual map of how everything is connected. It can be 335 00:15:52.720 --> 00:15:54.519 a real life saver when you're trying to figure out 336 00:15:54.559 --> 00:15:55.519 why something's not working. 337 00:15:55.799 --> 00:15:59.399 The book even recommends using tools like Microsoft Visio. Now 338 00:15:59.480 --> 00:16:02.679 let's talk about something that's really important, data storage and 339 00:16:02.720 --> 00:16:06.480 backup strategies. The book is very clear the amount of 340 00:16:06.559 --> 00:16:09.919 data we create, it just keeps growing, and we need 341 00:16:09.960 --> 00:16:12.519 to think long term when we're planning our storage. 342 00:16:12.600 --> 00:16:17.480 Absolutely, we're always creating photos, videos, documents. It piles up fast, 343 00:16:17.799 --> 00:16:20.639 and if your storage solution isn't scalable, you're going to 344 00:16:20.679 --> 00:16:22.120 constantly be running out of space. 345 00:16:22.399 --> 00:16:24.519 And it's not just about how much data we can store, 346 00:16:24.600 --> 00:16:27.039 it's also about how quickly we can access it. The 347 00:16:27.039 --> 00:16:30.519 book talks about the two main types of disk drives HDDs. 348 00:16:30.519 --> 00:16:33.279 Those are the hard disk drives and SSDs, the solid 349 00:16:33.279 --> 00:16:36.600 state drives hds. There are the workhourses lots of storage 350 00:16:36.600 --> 00:16:39.840 for a lower price, but SSDs those are the speed demons, 351 00:16:40.000 --> 00:16:42.720 way faster performance, but they cost more per gigabyte. 352 00:16:42.759 --> 00:16:46.000 It's always a trade off capacity versus speed. HDDs are 353 00:16:46.039 --> 00:16:48.159 like big warehouses. They can hold a ton of stuff, 354 00:16:48.480 --> 00:16:50.039 but it might take a while to find what you're 355 00:16:50.080 --> 00:16:52.799 looking for. SSDs are like express delivery. They can get 356 00:16:52.840 --> 00:16:55.080 your data much faster, but you pay a premium for 357 00:16:55.120 --> 00:16:55.600 that speed. 358 00:16:55.759 --> 00:16:59.120 So choose your storage weapon carefully and then there's RAID, 359 00:16:59.399 --> 00:17:03.600 redundant ray of independent discs. The book explains how RAID 360 00:17:03.639 --> 00:17:06.160 can give you data redundancy. That means you have multiple 361 00:17:06.240 --> 00:17:09.039 copies of your data, but it can also make things faster. 362 00:17:09.319 --> 00:17:12.039 It's like having multiple workers handling those copies. 363 00:17:12.240 --> 00:17:15.319 RAID is great for protecting your data if a drive fails. 364 00:17:15.839 --> 00:17:18.640 Think of it like having a team of couriers, each 365 00:17:18.680 --> 00:17:21.599 one carrying a copy of your data on a different route. 366 00:17:22.000 --> 00:17:24.720 If one of those couriers gets delayed, the others can 367 00:17:24.720 --> 00:17:27.480 still deliver the package. That's kind of how RAID works. 368 00:17:27.640 --> 00:17:31.079 The book explains different RAID levels like RAD one, RAD five, 369 00:17:31.200 --> 00:17:34.119 and RAD ten. RAD one, for example, it mirrors your 370 00:17:34.160 --> 00:17:37.279 data across multiple drives, so if one crashes, you have 371 00:17:37.279 --> 00:17:40.240 a complete copy on the other one. RAD five uses 372 00:17:40.279 --> 00:17:43.559 something called parodied data to protect against drive failures, and 373 00:17:43.599 --> 00:17:46.119 it's more efficient than RAD one in terms of storage space. 374 00:17:46.240 --> 00:17:49.160 Right and RAD ten it combines mirroring and striping. You 375 00:17:49.200 --> 00:17:52.319 get high performance and high redundancy, like having a team 376 00:17:52.359 --> 00:17:54.759 of super fast couriers, each one with a backup in 377 00:17:54.759 --> 00:17:55.759 case something goes wrong. 378 00:17:56.000 --> 00:17:58.359 So RAID is all about peace of mind knowing your 379 00:17:58.440 --> 00:18:03.000 data is safe. Now talk backup strategies. The book really 380 00:18:03.000 --> 00:18:07.680 emphasizes three things. Comprehensive backups, meaning you back up everything important, 381 00:18:08.279 --> 00:18:11.519 multiple copies just in case one gets messed up, and 382 00:18:11.799 --> 00:18:15.319 off site storage to protect against things like fire or theft. 383 00:18:15.799 --> 00:18:17.839 It's like having a fireproof safe at home and a 384 00:18:17.880 --> 00:18:20.079 backup safety deposit box at the bank. 385 00:18:20.359 --> 00:18:24.200 Backups are like your insurance policy against data loss. You 386 00:18:24.200 --> 00:18:26.599 need to back up everything, have multiple copies in keep 387 00:18:26.640 --> 00:18:28.200 at least one copy somewhere else. 388 00:18:28.480 --> 00:18:30.599 And there are different ways to do backups right. The 389 00:18:30.599 --> 00:18:34.240 book talks about full backups, incremental backups, and differential backups. 390 00:18:34.400 --> 00:18:36.720 Yeah, a full backup is like taking a snapshot of 391 00:18:36.720 --> 00:18:40.279 your entire system. Incremental backups they only copy the stuff 392 00:18:40.279 --> 00:18:43.680 that's changed since the last backup, and differential backups they 393 00:18:43.680 --> 00:18:46.720 copy all the changes since the last full backup. Which 394 00:18:46.759 --> 00:18:49.079 method you use it depends on how much data you 395 00:18:49.119 --> 00:18:50.519 have and how often you want to backup. 396 00:18:50.720 --> 00:18:53.920 There's also de duplication. The book explains how that can 397 00:18:53.960 --> 00:18:56.000 save a ton of storage space by getting rid of 398 00:18:56.119 --> 00:18:59.319 duplicate blocks of data, kind of like packing a suitcase 399 00:18:59.400 --> 00:19:02.640 more efficiently by removing all the unnecessary items. 400 00:19:02.839 --> 00:19:06.480 Dduplication is a great way to save space, especially when 401 00:19:06.519 --> 00:19:08.200