WEBVTT 1 00:00:00.080 --> 00:00:02.919 Welcome to your deep dive. This time we're diving into 2 00:00:02.960 --> 00:00:06.519 IPv six, the future of the Internet. They say, we're 3 00:00:06.559 --> 00:00:09.279 going to be looking at an advanced IPv six training 4 00:00:09.320 --> 00:00:13.400 course from August twenty seventeen. So we're basically going to 5 00:00:13.480 --> 00:00:16.000 be like your guide through all this awesome technical material. 6 00:00:16.039 --> 00:00:18.760 Will hit the highlights, show you the interesting parts, maybe 7 00:00:18.800 --> 00:00:21.800 some real world examples, even a configuration snippet or two. 8 00:00:22.120 --> 00:00:22.559 Sound good. 9 00:00:22.640 --> 00:00:23.359 Sounds like a plan. 10 00:00:23.839 --> 00:00:27.559 So you might be thinking, why IPv six, Why should 11 00:00:27.600 --> 00:00:30.760 I care? It's not just about longer addresses. It's about 12 00:00:30.760 --> 00:00:34.000 how the Internet works, more efficient, more secure, Ready for 13 00:00:34.039 --> 00:00:36.840 all those devices, billions of them, all connected and talking 14 00:00:36.840 --> 00:00:37.359 to each other. 15 00:00:37.560 --> 00:00:39.920 You got it. Remember all that worry about running out 16 00:00:39.920 --> 00:00:42.920 of IPv four addresses, Well, IPv six takes care of that, 17 00:00:43.079 --> 00:00:45.000 but it also brings a whole new set of challenges 18 00:00:45.039 --> 00:00:45.880 and opportunities. 19 00:00:46.119 --> 00:00:48.719 So let's break this down, starting with the foundation the 20 00:00:48.799 --> 00:00:52.560 packets themselves. This document points out IPv six packets are 21 00:00:52.600 --> 00:00:56.880 structured differently than IPv four packets. And this one blew 22 00:00:56.920 --> 00:01:00.520 my mind. Itv six headers twice the size of IPv 23 00:01:00.640 --> 00:01:03.479 four headers. Now you might be thinking bigger headers. Okay, 24 00:01:03.479 --> 00:01:06.480 so what, But it really impacts how efficiently riders can 25 00:01:06.519 --> 00:01:09.480 process these packets. It even has implications for security. Believe 26 00:01:09.519 --> 00:01:10.359 it or not, it's. 27 00:01:10.239 --> 00:01:13.079 Amazing how a seemingly small change can have such a 28 00:01:13.200 --> 00:01:15.959 huge ripple effect throughout the network. And it's not just 29 00:01:16.000 --> 00:01:20.519 about size. IPv six handles things differently too. Take packet fragmentation. 30 00:01:20.599 --> 00:01:24.480 For example, IPv four routers broke down large packets with 31 00:01:24.560 --> 00:01:27.159 IV six that all shifts over to the host device 32 00:01:27.480 --> 00:01:28.200 much more efficient. 33 00:01:28.359 --> 00:01:31.040 The training document has this visual legend breaks down the 34 00:01:31.079 --> 00:01:33.239 IPv six header format. It's really cool. It's like a 35 00:01:33.280 --> 00:01:36.159 roadmap showing what stayed the same from ITV four, what changed, 36 00:01:36.359 --> 00:01:38.879 and what's brand spanking new in IPv six. You can 37 00:01:38.920 --> 00:01:40.760 really see how these packets have evolved to meet the 38 00:01:40.760 --> 00:01:42.439 demands of a more complex Internet. 39 00:01:42.599 --> 00:01:45.599 We also can't forget about those optional headers in IPv six. 40 00:01:45.760 --> 00:01:49.319 They're like add ons for your packets, providing extra information 41 00:01:49.439 --> 00:01:52.560 or functionality. Some common ones you'll see are the routing 42 00:01:52.560 --> 00:01:56.239 header helps guide packets through the network, and the fragmentation 43 00:01:56.359 --> 00:01:58.760 header that one's used when a packet needs to be 44 00:01:58.760 --> 00:02:02.840 broken down into smaller piece. And get this, these optional 45 00:02:02.879 --> 00:02:06.200 headers are daisy chained, pretty neat way to organize all 46 00:02:06.239 --> 00:02:07.120 that extra information. 47 00:02:07.359 --> 00:02:11.000 Now, this is where things get really interesting. Remember broadcasts 48 00:02:11.000 --> 00:02:14.400 in IPv four shouting in a crowded room hoping someone 49 00:02:14.400 --> 00:02:17.159 will hear you. Well, IPv six gets rid of those 50 00:02:17.240 --> 00:02:18.400 completely good riddans. 51 00:02:18.479 --> 00:02:21.680 I say they were inefficient, created a lot of unnecessary 52 00:02:21.719 --> 00:02:25.360 network traffic. IPv six is more targeted, more elegent, you 53 00:02:25.360 --> 00:02:28.599 can say. It uses something called neighbor discovery, a much 54 00:02:28.639 --> 00:02:30.599 smarter way for devices to find each other. 55 00:02:30.680 --> 00:02:33.599 And you know what powers neighbor discovery, Those little ICMPv 56 00:02:33.680 --> 00:02:36.719 six messages we talked about before. They're not just for diagnostics, 57 00:02:36.759 --> 00:02:41.639 they're crucial for basic network functions. Seriously, don't disable ICMPv six. 58 00:02:41.960 --> 00:02:43.560 Your network will have a meltdown. 59 00:02:43.840 --> 00:02:47.599 It's true. ICMPv six is the unsung hero of IPv 60 00:02:47.719 --> 00:02:52.159 six networking. And the training document has this great diagram 61 00:02:52.400 --> 00:02:55.479 It shows how a web server handles packets of different sizes. 62 00:02:55.919 --> 00:02:58.919 Really brings the concept of path MTU discovery to life, 63 00:02:59.120 --> 00:03:02.639 like a polite converse between devices figuring out the best 64 00:03:02.680 --> 00:03:05.280 way to send data without overwhelming each other. 65 00:03:05.400 --> 00:03:08.199 So let's move on to routing and IPv six. Good 66 00:03:08.240 --> 00:03:11.639 news here, it's actually very similar to IPv four, still 67 00:03:11.719 --> 00:03:14.319 using the concept of longest prefix matching to figure out 68 00:03:14.319 --> 00:03:18.039 where a packet should go, but with IV six everything 69 00:03:18.120 --> 00:03:19.240 is well bigger. 70 00:03:19.280 --> 00:03:21.080 Think give it this way. The Internet just got a 71 00:03:21.080 --> 00:03:24.000 massive expansion with IPv six, so those routing tables are 72 00:03:24.039 --> 00:03:26.800 packed with way more addresses and the prefixes are longer. 73 00:03:27.000 --> 00:03:30.319 Got to accommodate that huge address base. But the underlying 74 00:03:30.400 --> 00:03:32.560 logic for making routing decisions it's the same as an 75 00:03:32.560 --> 00:03:33.240 IPv four. 76 00:03:33.439 --> 00:03:35.800 To help you visualize all this, the training materials have 77 00:03:35.840 --> 00:03:38.120 a sample routing table. We could walk through some examples 78 00:03:38.199 --> 00:03:41.080 show how that longest prefix matching magic works in practice. 79 00:03:41.120 --> 00:03:44.039 It's like solving a puzzle finding the most specific route 80 00:03:44.039 --> 00:03:44.879 for each packet. 81 00:03:45.240 --> 00:03:49.159 Understanding how routing works in IPv six absolutely crucial for 82 00:03:49.199 --> 00:03:51.919 anyone working with networks today, is the foundation of how 83 00:03:52.000 --> 00:03:55.360 data flows across this expanded Internet. It's like knowing the 84 00:03:55.400 --> 00:03:57.560 streets and highways of a city. You need to know 85 00:03:57.639 --> 00:03:59.000 them to navigate effectively. 86 00:03:59.280 --> 00:04:02.199 And of course we can't talk about routing without mentioning 87 00:04:02.439 --> 00:04:09.199 the heavy hitters, those essential routing protocols OSPF three and BGP, 88 00:04:09.960 --> 00:04:12.759 like the traffic cops and air traffic controllers of the Internet, 89 00:04:13.240 --> 00:04:14.800 making sure data flows smoothly. 90 00:04:15.240 --> 00:04:18.360 They've definitely gotten some upgrades to handle the complexities of 91 00:04:18.399 --> 00:04:22.160 IPv six. OSPF three, for example, That one focuses on 92 00:04:22.240 --> 00:04:25.040 managing routing within your own network, making sure all your 93 00:04:25.040 --> 00:04:26.759 devices can talk to each other seamlessly. 94 00:04:26.920 --> 00:04:30.360 And then we have BGP handling connections between different networks 95 00:04:30.439 --> 00:04:32.959 across the entire Internet. It's like a global travel agent 96 00:04:32.959 --> 00:04:35.759 for your data packets, making sure they reach their destination 97 00:04:36.000 --> 00:04:37.560 no matter how far they need to travel. 98 00:04:37.759 --> 00:04:41.120 What's fascinating is seeing the evolution of these protocols. For example, 99 00:04:41.240 --> 00:04:44.160 with OSPF three is designed for IPv six, of course, 100 00:04:44.720 --> 00:04:48.360 but we see some key differences from its IPv four counterpart, 101 00:04:48.680 --> 00:04:52.759 OSPFv two. And get this, in networks that are purely 102 00:04:52.800 --> 00:04:57.160 IPv six, you actually need to configure a router ID manually. 103 00:04:57.480 --> 00:04:59.759 You can't just rely on IPv four addresses anymore. 104 00:05:00.000 --> 00:05:02.879 And the best part is the training document gives actual 105 00:05:02.920 --> 00:05:07.240 configuration examples for both OSPFF three and BGP. We're talking 106 00:05:07.399 --> 00:05:09.959 real world commands you can use to set up these 107 00:05:10.000 --> 00:05:12.360 protocols on your network. This is where the rubber meets. 108 00:05:12.199 --> 00:05:15.360 The road for sure. These configuration examples are super valuable 109 00:05:15.399 --> 00:05:18.120 for anyone managing an itv six network. It's one thing 110 00:05:18.160 --> 00:05:20.360 to get the concepts, it's another to see the actual 111 00:05:20.399 --> 00:05:21.560 commands that make it all happen. 112 00:05:21.600 --> 00:05:23.839 All right, you've got your new IPB six network all 113 00:05:23.839 --> 00:05:26.639 set up. Now, how do you deliver content like websites 114 00:05:26.959 --> 00:05:27.560 to users? 115 00:05:27.720 --> 00:05:30.160 Well, there are several ways to do it. Ideally, you'd 116 00:05:30.199 --> 00:05:33.399 have what we call native dual stack, meaning your entire network, 117 00:05:33.399 --> 00:05:36.560 including your web server, speaks both IPv four and IPv 118 00:05:36.639 --> 00:05:40.519 six fluently, like being bilingual on the Internet. But sometimes 119 00:05:40.560 --> 00:05:42.240 you need to be a little more creative. 120 00:05:42.000 --> 00:05:44.720 And the document talks about some of those creative solutions. 121 00:05:45.199 --> 00:05:49.160 Load balancers with NAP proxies, and even this intriguing thing 122 00:05:49.240 --> 00:05:50.879 called NT sixty. 123 00:05:50.639 --> 00:05:53.040 Four NINETI sixty four is super cool. It's like a 124 00:05:53.079 --> 00:05:55.959 bridge between the IPv four and IPv six worlds, and 125 00:05:56.040 --> 00:05:59.560 let's devices that only speak IPB six access content on 126 00:05:59.639 --> 00:06:02.680 servers that are still using IPv four. It's a key 127 00:06:02.759 --> 00:06:06.160 tool for ensuring a smooth transition as the Internet moves 128 00:06:06.199 --> 00:06:07.240 toward IPv six. 129 00:06:07.399 --> 00:06:10.800 IPv six is especially important for mobile networks. Think about it, 130 00:06:11.079 --> 00:06:14.120 billions of smartphones out there. I'll hungry for data. IPv 131 00:06:14.199 --> 00:06:15.879 four just couldn't handle that kind of demand. 132 00:06:15.920 --> 00:06:18.120 You're absolutely right, rob providers had to jump on the 133 00:06:18.120 --> 00:06:21.319 IPv six train early on. They've got unique challenges though, 134 00:06:21.439 --> 00:06:24.920 implementing NT sixty four, dealing with four sixty four x LAT, 135 00:06:25.439 --> 00:06:28.079 which Apple famously is not a fan of, and making 136 00:06:28.120 --> 00:06:30.920 sure all their network infrastructure from cell towers to core 137 00:06:31.000 --> 00:06:33.439 routers can handle all that IPv six traffic. 138 00:06:33.519 --> 00:06:35.959 Oh and speaking of Apple, they basically told app developers, 139 00:06:36.000 --> 00:06:38.600 get your apps working over IPv six only networks, or 140 00:06:38.639 --> 00:06:41.120 else no more relying on those IPv four crutches. 141 00:06:41.399 --> 00:06:41.879 Tough love. 142 00:06:41.959 --> 00:06:42.120 Right. 143 00:06:42.759 --> 00:06:45.800 The document even has a slide from t Mobile USA 144 00:06:46.399 --> 00:06:49.839 outlines everything noble providers need to consider for IPv six, 145 00:06:50.519 --> 00:06:54.079 from the handsets to the core network. It's a comprehensive 146 00:06:54.160 --> 00:06:57.439 roadmap for building a future proof mobile network. 147 00:06:58.000 --> 00:06:59.720 All right, let's bring it closer to home. Now, let's 148 00:06:59.759 --> 00:07:02.879 talk about your computer. The good news is all the 149 00:07:02.920 --> 00:07:07.920 major operating systems, Windows, Linux, dot OSX they all support 150 00:07:07.959 --> 00:07:11.000 IPD six natively. It's built right in. Good news is 151 00:07:11.040 --> 00:07:14.199 it works automatically. The bad news it works automatic? 152 00:07:14.319 --> 00:07:17.959 Uh huh? The catch right, Sometimes automatic configuration can be 153 00:07:17.959 --> 00:07:20.639 a little two hands off, especially for those of us 154 00:07:20.639 --> 00:07:22.639 who like to have more control over our networks. 155 00:07:22.720 --> 00:07:24.959 So while it's great that IPv six just works out 156 00:07:24.959 --> 00:07:27.120 of the box, sometimes you need more control. 157 00:07:26.959 --> 00:07:30.199 Exactly, and that's where understanding how to manage IPv six 158 00:07:30.279 --> 00:07:32.720 clients comes in. We'll dive into that in the next part. 159 00:07:32.879 --> 00:07:36.879 We'll explore how to configure things like slaoke ecciby, DHCPv 160 00:07:37.000 --> 00:07:40.160 six and how to disable those privacy extensions and Windows 161 00:07:40.680 --> 00:07:42.759 which can sometimes cause a bit of a headache. 162 00:07:42.839 --> 00:07:43.399 Can't wait. 163 00:07:43.759 --> 00:07:45.959 Welcome back to your deep dive into IPv six. 164 00:07:46.160 --> 00:07:48.079 Before we went to break we were talking about IP 165 00:07:48.160 --> 00:07:50.759 address management and all those cool tools available. 166 00:07:50.879 --> 00:07:53.920 It's really mind boggling how many IPv six addresses we're 167 00:07:53.920 --> 00:07:57.160 talking about managing. It's a whole different scale than IPv four. 168 00:07:57.360 --> 00:08:00.360 The document says there are over thirty four trillions. Sixty 169 00:08:00.399 --> 00:08:02.199 four is in a twenty nine like. I can't even 170 00:08:02.279 --> 00:08:03.560 fathom that many addresses. 171 00:08:03.639 --> 00:08:07.519 It's truly astronomical, and that's why IPM tools are so important. 172 00:08:07.639 --> 00:08:10.160 They help us make sense of this massive address space. 173 00:08:10.319 --> 00:08:13.120 So let's break down some specific tools. The training course 174 00:08:13.199 --> 00:08:18.399 highlighted net dot just goip and a GPM. What can 175 00:08:18.399 --> 00:08:19.240 you tell us about. 176 00:08:19.000 --> 00:08:21.720 Net dot net dot is a powerhouse. It can automatically 177 00:08:21.720 --> 00:08:25.240 discover devices on your network using SNMP, manage your DNS 178 00:08:25.240 --> 00:08:28.959 and DHCP configurations, even keep track of m NAG addresses. 179 00:08:29.120 --> 00:08:32.000 And it's got these handy export scripts for popular monitoring 180 00:08:32.080 --> 00:08:34.759 tools like na Gio's smoke being and CACTI. 181 00:08:34.919 --> 00:08:36.440 So it's not just an address track or it's like 182 00:08:36.440 --> 00:08:39.919 a multi toool that integrates with your whole network management ecosystem. 183 00:08:40.360 --> 00:08:41.799 Very cool. What about just gip? 184 00:08:42.080 --> 00:08:44.879 Just diip takes a more visual approach to address management. 185 00:08:45.240 --> 00:08:47.399 It's web based, gives you a clear view of your 186 00:08:47.440 --> 00:08:51.799 address base, shows you free ranges, can manage vlands, even 187 00:08:51.840 --> 00:08:54.879 generate DNS zone files for both forward and reverse lookups. 188 00:08:55.279 --> 00:08:58.879 It's really helpful for planning and allocating subnets, especially in 189 00:08:58.960 --> 00:08:59.559 larger networks. 190 00:08:59.559 --> 00:09:02.240 And it's support or it's multiple languages, a huge plus 191 00:09:02.279 --> 00:09:06.480 for global organizations. Lastly, let's talk about f fab PAM. 192 00:09:06.720 --> 00:09:09.799 Vipam is another web based tool as a really modern interface, 193 00:09:10.000 --> 00:09:13.240 can send email notifications, show you free IP ranges and 194 00:09:13.240 --> 00:09:16.519 client counts per subnet, even important export data to excel. 195 00:09:17.159 --> 00:09:18.039 Very user friendly. 196 00:09:18.080 --> 00:09:20.279 I love that it can pull information from the ripe 197 00:09:20.440 --> 00:09:23.279 database that saves so much manual entry. It seems like 198 00:09:23.399 --> 00:09:25.679 all of these tools bring something unique to the table. 199 00:09:25.840 --> 00:09:28.759 What factors should someone consider when choosing an IPM tool. 200 00:09:29.039 --> 00:09:32.000 That's a great question. It really depends on your specific needs, 201 00:09:32.399 --> 00:09:34.320 like the size of your network, your budget, and the 202 00:09:34.320 --> 00:09:36.919 features that are most important to you. Some tools are 203 00:09:36.919 --> 00:09:40.919 geared toward large enterprises with complex needs, while others are 204 00:09:40.919 --> 00:09:45.039 perfect for smaller organizations with simpler requirements. Some are free 205 00:09:45.120 --> 00:09:49.480 an open source offering flexibility and community support, while others 206 00:09:49.519 --> 00:09:52.799 are commercial products with more advanced features and dedicated support. 207 00:09:53.200 --> 00:09:56.000 So do your research find the tool that fits your 208 00:09:56.080 --> 00:09:58.720 unique situation. Sounds like we could do a whole separate 209 00:09:58.720 --> 00:10:02.000 deep dive episode on ip tools alone, but for now, 210 00:10:02.480 --> 00:10:06.000 let's shift gears talk about how to configure those hosts 211 00:10:06.080 --> 00:10:07.399 to use IPv six. 212 00:10:07.679 --> 00:10:11.759 Sounds good. Like we mentioned before, all the major operating systems, Windows, Linux, 213 00:10:11.759 --> 00:10:13.960 and OSX, they all have native support for. 214 00:10:13.919 --> 00:10:16.679 IPv six, which is fantastic right. It means you don't 215 00:10:16.720 --> 00:10:19.639 have to install any special software to get IPv six 216 00:10:19.679 --> 00:10:20.879 up and running exactly. 217 00:10:21.360 --> 00:10:24.679 But here's the thing that the document really emphasizes. IPv 218 00:10:24.840 --> 00:10:28.519 six often works automatically, and while that sounds super convenient, 219 00:10:28.720 --> 00:10:30.159 it could be a bit of a double edged sword. 220 00:10:30.360 --> 00:10:34.840 Okay, I'm intrigued. Why would automatic configuration be a potential issue. 221 00:10:34.960 --> 00:10:38.320 Well, when things happen automatically in the background, you might 222 00:10:38.320 --> 00:10:40.600 not have as much control as you'd like. For example, 223 00:10:41.279 --> 00:10:44.159 you might not know what specific IPv six address your 224 00:10:44.159 --> 00:10:46.399 computer is using, or you might not be able to 225 00:10:46.440 --> 00:10:51.000 easily configure things like DNS servers or default gateways according 226 00:10:51.039 --> 00:10:52.519 to your specific network setup. 227 00:10:52.679 --> 00:10:55.360 So it's like your computer is making decisions without fully 228 00:10:55.399 --> 00:10:58.279 consulting you, and for network administrators that can be a real. 229 00:10:58.080 --> 00:11:01.000 Headache precisely, and that that's why it's so important to 230 00:11:01.080 --> 00:11:04.960 understand how to manage IPv six clients and have the 231 00:11:05.000 --> 00:11:09.519 ability to override those automatic settings when necessary. The document 232 00:11:09.559 --> 00:11:12.559 goes into detail about how to configure different address assignment 233 00:11:12.600 --> 00:11:17.039 methods like SLAA and DHCPv six. It also covers how 234 00:11:17.080 --> 00:11:20.559 to disable certain features like those privacy extensions and Windows 235 00:11:20.679 --> 00:11:23.000 they can sometimes interfere with network management tools. 236 00:11:23.159 --> 00:11:26.120 Let's break those down one by one. First up, SLAA, 237 00:11:26.200 --> 00:11:27.279 So what's that all about. 238 00:11:27.519 --> 00:11:32.519 SLAAC stands for Stateless Address Autoconfiguration it's a way for 239 00:11:32.559 --> 00:11:35.320 a host to figure out its own IV six address 240 00:11:35.799 --> 00:11:38.480 based on information it receives from a router. Think of 241 00:11:38.480 --> 00:11:40.799 it like the router is saying, hey, here's a prefix 242 00:11:40.840 --> 00:11:42.840 you can use, go ahead and create an address for 243 00:11:42.879 --> 00:11:44.039 yourself within this range. 244 00:11:44.279 --> 00:11:46.639 Ah. So it's like the host is given a street 245 00:11:46.720 --> 00:11:49.519 name and then gets to choose its own house number 246 00:11:49.559 --> 00:11:50.200 on that street. 247 00:11:50.600 --> 00:11:53.639 That's a great analogy. The host combines that prefix from 248 00:11:53.679 --> 00:11:57.639 the router with its own unique identifier, often its NC address, 249 00:11:58.320 --> 00:12:01.399 to generate a globally unique ip v six address. It's 250 00:12:01.399 --> 00:12:04.919 a clever way to simplify address assignment, especially in larger networks. 251 00:12:04.960 --> 00:12:07.399 Pretty neat, But you mentioned that sometimes you might want 252 00:12:07.440 --> 00:12:10.200 to disable SLAC. When would that be the case. 253 00:12:10.679 --> 00:12:13.600 If you need more granular control over the addresses your 254 00:12:13.600 --> 00:12:16.919 hosts are using, you might out for DHGPV six instead. 255 00:12:17.519 --> 00:12:20.519 DHGVV six is the IPv six equivalent of the DHDP 256 00:12:20.639 --> 00:12:23.679 server we use for IPv four. It lets you centrally 257 00:12:23.679 --> 00:12:28.080 manage address assignment and provide additional configuration parameters to clients. 258 00:12:28.240 --> 00:12:31.519 So it's like having a designated address administrator who assigns 259 00:12:31.519 --> 00:12:35.279 addresses and provides all the network settings to each device exactly. 260 00:12:35.360 --> 00:12:37.679 It gives you much more control over your network and 261 00:12:37.759 --> 00:12:40.200 make sure all your devices are configured properly. And the 262 00:12:40.200 --> 00:12:43.159 best part is that training materials include some practical configuration 263 00:12:43.240 --> 00:12:46.919 examples for dhdpv six on Cisco Writers. 264 00:12:46.960 --> 00:12:50.240 Fantastic, always helpful to see those real world commands. What 265 00:12:50.399 --> 00:12:53.039 other cool things can you do with hcpv six. 266 00:12:53.120 --> 00:12:56.720 Well, there's this interesting feature called dhgpv six prefixed delegation. 267 00:12:57.399 --> 00:13:01.000 This allows an ISP to assign a block addresses to 268 00:13:01.039 --> 00:13:04.759 a customer, who can then further subdivide those addresses and 269 00:13:04.799 --> 00:13:06.679 assign them to devices on their own network. 270 00:13:06.840 --> 00:13:09.440 Wow, that's like giving your customer their own mini Internet. 271 00:13:09.679 --> 00:13:11.320 Sounds pretty complex though it. 272 00:13:11.240 --> 00:13:13.799 Can be, but the document actually walks you through it 273 00:13:13.879 --> 00:13:17.080 step by step. It provides configuration examples for both the 274 00:13:17.120 --> 00:13:20.120 ISP side and the customer side, makes it much easier 275 00:13:20.120 --> 00:13:21.240 to understand and implement. 276 00:13:21.440 --> 00:13:25.080 That's incredibly helpful. So we've covered SLAC and DHCPB six. 277 00:13:25.360 --> 00:13:28.360 Now what about those privacy extensions you mentioned earlier? Why 278 00:13:28.360 --> 00:13:29.759 would someone want to disable them? 279 00:13:29.919 --> 00:13:33.440 Privacy extensions are a security feature built into Windows. They 280 00:13:33.480 --> 00:13:36.000 try to make it harder to track a device's IPv 281 00:13:36.080 --> 00:13:38.960 six address over time. By generating a random part of 282 00:13:39.000 --> 00:13:41.000 the IPv six address periodically. 283 00:13:41.080 --> 00:13:44.679 It sounds like a good thing for privacy conscious users, it. 284 00:13:44.679 --> 00:13:49.759 Definitely is, but the catches those randomly generated addresses can 285 00:13:49.799 --> 00:13:53.919 sometimes cause problems with network management tools or applications that 286 00:13:53.960 --> 00:13:57.440 rely on a consistent IPv six address. If you're seeing 287 00:13:57.440 --> 00:14:00.720 strange behavior with certain applications, it's worth che if those 288 00:14:00.759 --> 00:14:02.240 privacy extensions are enabled. 289 00:14:02.279 --> 00:14:05.759 So it's a trade off between privacy and potential compatibility 290 00:14:05.759 --> 00:14:06.639 issues exactly. 291 00:14:06.679 --> 00:14:09.120 And the document shows you how to disable those privacy 292 00:14:09.159 --> 00:14:12.200 extensions using the command prompt in Windows if you need to. 293 00:14:12.480 --> 00:14:15.519 Amazing how many little settings and configurations are tucked away 294 00:14:15.519 --> 00:14:17.320 in Windows. I always learn something new when we do 295 00:14:17.360 --> 00:14:18.039 these deep dives. 296 00:14:18.120 --> 00:14:21.240 Me too. It's a constant journey of discovery. Speaking of discovery, 297 00:14:21.279 --> 00:14:23.120 it's got time for one more topic before we wrap 298 00:14:23.240 --> 00:14:25.559 up Part two. Let's talk security. 299 00:14:25.879 --> 00:14:29.480 Ah, Yes, security, the ever important topic. What does the 300 00:14:29.519 --> 00:14:32.799 document have to say about security in an IPv six world. 301 00:14:33.080 --> 00:14:37.039 Well, it starts by stating something very clearly, there's nothing 302 00:14:37.080 --> 00:14:40.399 inherently secure about IPv six. Just because you're using a 303 00:14:40.399 --> 00:14:43.799 newer protocol doesn't mean you can ignore security best practices. 304 00:14:43.879 --> 00:14:46.399 So just because we have a shiny new house doesn't 305 00:14:46.440 --> 00:14:48.679 mean we can forget to lock the door exactly. 306 00:14:48.879 --> 00:14:53.159 In fact, the expanded address base of IPv six can 307 00:14:53.240 --> 00:14:57.240 actually present some unique security challenges. How so well, with 308 00:14:57.279 --> 00:15:01.080 IPv four, it was at least theoretic possible to scan 309 00:15:01.200 --> 00:15:04.960 the entire address base to look for vulnerable devices. With 310 00:15:05.039 --> 00:15:08.600 IPv six, the address base is so vast that it's 311 00:15:08.639 --> 00:15:11.639 practically impossible to scan it all. This means attackers have 312 00:15:11.679 --> 00:15:14.440 to be more creative, more targeted in their approach. 313 00:15:14.600 --> 00:15:16.679 So instead of casting a wide net, they have to 314 00:15:16.759 --> 00:15:19.240 use more sophisticated techniques to find their targets. 315 00:15:19.279 --> 00:15:22.039 That's right. The document talks about techniques like subnet scanning, 316 00:15:22.639 --> 00:15:26.279 where attackers focus on specific ranges of IPv six addresses 317 00:15:26.639 --> 00:15:29.120 looking for weaknesses. It's like they're searching for a needle 318 00:15:29.159 --> 00:15:32.120 in a slightly smaller haystack, but they're using more advanced 319 00:15:32.120 --> 00:15:33.600 tools and techniques to find it. 320 00:15:33.639 --> 00:15:35.720 Makes sense, So what are some key things to keep 321 00:15:35.720 --> 00:15:38.039 in mind for securing an IPv six network. 322 00:15:38.320 --> 00:15:44.360 The document emphasizes understanding and properly configuring those ICMTV six messages. Remember, 323 00:15:44.720 --> 00:15:48.080 ICMPv six is essential for neighbor discovery and other core 324 00:15:48.120 --> 00:15:51.759 network functions, but it can also be abused by attackers 325 00:15:51.799 --> 00:15:53.600 for things like denial of service. 326 00:15:53.320 --> 00:15:55.960 Attacks, so it's a balancing act. You need to allow 327 00:15:56.080 --> 00:15:59.080 enough ICMPv six traffic for your network to function, but 328 00:15:59.120 --> 00:16:02.000 you also need to filter out any malicious or suspicious 329 00:16:02.480 --> 00:16:04.639 ICMPv six messages. 330 00:16:04.360 --> 00:16:07.480 Exactly, and the document provides some helpful examples of firewall 331 00:16:07.559 --> 00:16:10.759 rules you can use to filter ICMPv six traffic effectively. 332 00:16:11.159 --> 00:16:13.600 It also talks about the importance of filtering IPv six 333 00:16:13.679 --> 00:16:16.159 headers to prevent certain types of attacks. 334 00:16:16.279 --> 00:16:19.240 Are there any other security measures or tools mentioned in 335 00:16:19.279 --> 00:16:19.879 the document? 336 00:16:20.039 --> 00:16:23.000 They touch on using IPsec for encryption, always a good 337 00:16:23.000 --> 00:16:26.279 idea for securing sensitive data and transit, and they discuss 338 00:16:26.360 --> 00:16:29.360 this cool feature called r guard r A guard. 339 00:16:29.360 --> 00:16:30.279 What's that all about? 340 00:16:30.600 --> 00:16:32.799 Riguard is a security feature. You can implement it on 341 00:16:32.840 --> 00:16:35.399 a layer two switch. Think of it as a bouncer 342 00:16:35.440 --> 00:16:38.519 for your network, making sure only authorized routers are allowed 343 00:16:38.559 --> 00:16:39.919 to announce their presence, so. 344 00:16:39.919 --> 00:16:42.840 It helps prevent rogue routers from messing with your network 345 00:16:43.039 --> 00:16:45.639 and potentially intercepting traffic exactly. 346 00:16:45.679 --> 00:16:48.440 It's a very effective way to mitigate certain types of 347 00:16:48.480 --> 00:16:50.639 attacks like man in the middle attacks. 348 00:16:50.759 --> 00:16:53.000 This is all great information. I feel like we could 349 00:16:53.039 --> 00:16:56.440 spend hours diving into the intricacies of IPv six security. 350 00:16:56.519 --> 00:16:59.279 We could, but unfortunately we're out of time for Part two. 351 00:17:00.039 --> 00:17:02.600 Continue our exploration of IPv six in the final part 352 00:17:02.600 --> 00:17:06.799 of this deep dive series. See you then, Welcome back 353 00:17:06.799 --> 00:17:09.079 to the final part of our IPv six deep dive. 354 00:17:09.319 --> 00:17:13.640 We've covered so much ground already, structure of IPv six packets, 355 00:17:13.920 --> 00:17:17.440 the routing protocols that keep everything moving, how to deliver 356 00:17:17.599 --> 00:17:21.480 content in this IPv six world, even those unique security 357 00:17:21.559 --> 00:17:22.960 challenges with IPv six. 358 00:17:23.039 --> 00:17:25.400 It's been quite the journey. In this last part, we're 359 00:17:25.400 --> 00:17:28.079 gonna switch gears a bit focus on some practical tips 360 00:17:28.079 --> 00:17:30.640 and tricks that can help you troubleshoot and optimize your 361 00:17:30.680 --> 00:17:33.680 IPv six deployments. These are the kinds of insights you 362 00:17:33.720 --> 00:17:36.960 often won't find in textbooks, but they are incredibly valuable 363 00:17:36.960 --> 00:17:37.799 in the real world. 364 00:17:37.880 --> 00:17:40.960 Oh I love insider tips like getting a secret decoder 365 00:17:41.039 --> 00:17:43.440 ring for the IPv six universe exactly. 366 00:17:43.680 --> 00:17:46.319 These are lessons learned from years of working with IPv six, 367 00:17:46.759 --> 00:17:49.400 little nuggets of wisdom that can save you hours of frustration. 368 00:17:49.839 --> 00:17:52.240 So spill the beans what's the first tip on our list. 369 00:17:52.319 --> 00:17:56.759 Well, the document really stresses thorough documentation might seem obvious, 370 00:17:57.119 --> 00:18:02.839 but IPv six longer addresses more complex submitting schemes. A 371 00:18:02.920 --> 00:18:05.480 wider array of configuration options. 372 00:18:05.079 --> 00:18:07.400 Easy to get lost without a good map exactly. 373 00:18:07.519 --> 00:18:11.680 A well documented network is your lifeline, especially when you're troubleshooting. 374 00:18:11.920 --> 00:18:16.359 Keep track of your address allocations, subnet masks, routing configurations, 375 00:18:16.400 --> 00:18:19.279 any other relevant information. It'll save you headaches later on. 376 00:18:19.519 --> 00:18:22.400 Perfect use case for those IPM tools we discussed, they 377 00:18:22.400 --> 00:18:24.799 can centralize all that information absolutely. 378 00:18:24.880 --> 00:18:29.119 And speaking of documentation, another tip, use meaningful names for 379 00:18:29.200 --> 00:18:32.440 your network devices and interfaces. Don't just stick with those 380 00:18:32.480 --> 00:18:35.720 generic names assigned by the manufacturer like router ie or 381 00:18:35.839 --> 00:18:36.599 ethernet OA. 382 00:18:36.759 --> 00:18:39.079 Those are about as helpful as calling your pets cat 383 00:18:39.119 --> 00:18:40.160 and dog exactly. 384 00:18:40.319 --> 00:18:43.119 Use names that actually tell you something useful about the 385 00:18:43.160 --> 00:18:46.200 device's roll or its location of the network. So, for example, 386 00:18:46.440 --> 00:18:48.920 you could name a router that connects your isp ISP 387 00:18:49.079 --> 00:18:51.799 router or a switch in your server room. Server room 388 00:18:51.839 --> 00:18:54.480 switch seems like a small thing, but it makes a 389 00:18:54.480 --> 00:18:57.039 big difference when you're trying to understand your network at 390 00:18:57.039 --> 00:18:57.519 a glance. 391 00:18:57.799 --> 00:19:00.400 It's like organizing your tools in the garage. If everything 392 00:19:00.480 --> 00:19:03.119 has a designated spot, much easier to find what you 393 00:19:03.160 --> 00:19:04.400 need exactly. 394 00:19:04.680 --> 00:19:08.319 Another crucial tip, familiarize yourself with the essential IPv six 395 00:19:08.359 --> 00:19:13.200 troubleshooting commands. Commands like ping, choice, route and show IPB 396 00:19:13.319 --> 00:19:17.640 six interface. These are your best friends when diagnosing connectivity issues. 397 00:19:17.759 --> 00:19:19.720 Those are the classics, but I imagine they have some 398 00:19:19.839 --> 00:19:21.799 IPv six specific twists. 399 00:19:21.960 --> 00:19:24.240 Oh they do, and the training materials walk you through 400 00:19:24.279 --> 00:19:27.480 some real world examples of how to use these commands 401 00:19:27.640 --> 00:19:30.160