1 00:00:00,000 --> 00:00:00,948 2 00:00:00,948 --> 00:00:04,266 [AUDIO LOGO] 3 00:00:04,266 --> 00:00:08,260 4 00:00:08,260 --> 00:00:10,310 So now, let's take our first look 5 00:00:10,310 --> 00:00:14,630 at an automatic IPv6 over IP tunnel. 6 00:00:14,630 --> 00:00:19,760 Specifically, we're going to look at 6to4 automatic tunnels. 7 00:00:19,760 --> 00:00:23,090 Now, an automatic tunnel simply means 8 00:00:23,090 --> 00:00:24,800 that the tunnel is going to learn 9 00:00:24,800 --> 00:00:30,160 the destination on its own, but that does beg a question. 10 00:00:30,160 --> 00:00:32,360 How is it going to do that? 11 00:00:32,360 --> 00:00:34,210 Well, that's what we have to answer. 12 00:00:34,210 --> 00:00:38,800 How does the tunnel learn the IPv4 destination 13 00:00:38,800 --> 00:00:41,090 that it needs to build the tunnel for? 14 00:00:41,090 --> 00:00:44,410 So that's going to be our primary conversation because 15 00:00:44,410 --> 00:00:49,640 besides that, well, this is essentially a 6in4 tunnel. 16 00:00:49,640 --> 00:00:52,660 So let's go ahead and jump in and talk about some 17 00:00:52,660 --> 00:00:56,230 of the details on how this works specifically 18 00:00:56,230 --> 00:01:00,780 for our 6to4 automatic tunnels. 19 00:01:00,780 --> 00:01:03,710 So as we mentioned, 6to4 tunneling 20 00:01:03,710 --> 00:01:06,570 is an automatic tunneling method. 21 00:01:06,570 --> 00:01:10,670 So let's talk a bit about how this actually functions. 22 00:01:10,670 --> 00:01:14,790 First thing, we did mention this during the introduction. 23 00:01:14,790 --> 00:01:19,230 This is still using 6in4 encapsulation, 24 00:01:19,230 --> 00:01:23,720 which simply means that, again, the IPv6 header is 25 00:01:23,720 --> 00:01:26,840 coming directly behind the IPv4 header. 26 00:01:26,840 --> 00:01:30,140 This does not use GRE headers. 27 00:01:30,140 --> 00:01:35,030 It's also very important to note that this uses the reserved 28 00:01:35,030 --> 00:01:40,370 address space of 2002::/16. 29 00:01:40,370 --> 00:01:43,980 This is by definition, and it's not an option. 30 00:01:43,980 --> 00:01:47,840 So any time we see this 2002 address space, 31 00:01:47,840 --> 00:01:50,030 we should be pretty sure that this 32 00:01:50,030 --> 00:01:54,110 is being used for a 6to4 tunnel, or well, 33 00:01:54,110 --> 00:01:56,310 somebody using it incorrectly. 34 00:01:56,310 --> 00:02:00,990 Then what we do is, each site is then 35 00:02:00,990 --> 00:02:06,970 going to be given an IPv6/48 prefix. 36 00:02:06,970 --> 00:02:14,640 Now, this /48 prefix is going to be based on the IPv4 tunnel 37 00:02:14,640 --> 00:02:16,570 endpoint address. 38 00:02:16,570 --> 00:02:21,760 Keep in mind, of course, IPv4 is 32-bit. 39 00:02:21,760 --> 00:02:26,640 So when we add the 32 bits to the end of the /16, 40 00:02:26,640 --> 00:02:31,500 that's where that /48 comes from that we're going to be giving 41 00:02:31,500 --> 00:02:33,550 to that remote site. 42 00:02:33,550 --> 00:02:39,030 Now, if that other site has the need to subnet further, 43 00:02:39,030 --> 00:02:45,990 keep in mind that we can subnet that /48 maybe to a /64, 44 00:02:45,990 --> 00:02:50,910 something along those lines, just as we would with any other 45 00:02:50,910 --> 00:02:53,070 IPv6 prefix. 46 00:02:53,070 --> 00:02:56,590 But ultimately, how does all of this help? 47 00:02:56,590 --> 00:02:59,400 Well, this is the key factor right here, 48 00:02:59,400 --> 00:03:04,560 when a packet arrives on this tunnel interface. 49 00:03:04,560 --> 00:03:07,620 Now, this isn't really part of our discussion right now, 50 00:03:07,620 --> 00:03:11,610 but how would it know to arrive at this tunnel interface? 51 00:03:11,610 --> 00:03:14,350 Well, that's where the routing comes into play. 52 00:03:14,350 --> 00:03:17,800 We're not focusing on the IPv6 routing right now. 53 00:03:17,800 --> 00:03:20,910 But again, it's going to be from the routing protocols. 54 00:03:20,910 --> 00:03:23,350 The packet arrives at this tunnel. 55 00:03:23,350 --> 00:03:27,990 And then we extract the IPv4 address 56 00:03:27,990 --> 00:03:30,810 of the tunnel destination. 57 00:03:30,810 --> 00:03:36,180 We're pulling that out of this /48 prefix and using that 58 00:03:36,180 --> 00:03:38,410 to then build the tunnel. 59 00:03:38,410 --> 00:03:40,950 So this is the fundamental principle 60 00:03:40,950 --> 00:03:44,200 behind how the 6to4 tunnels work. 61 00:03:44,200 --> 00:03:48,270 So let's take a look at an example of the addressing 62 00:03:48,270 --> 00:03:50,250 and how we would configure this. 63 00:03:50,250 --> 00:03:52,820 64 00:03:52,820 --> 00:03:56,270 So first, let's take a look at an example. 65 00:03:56,270 --> 00:04:00,940 So we're given an IPv4 address of a tunnel endpoint 66 00:04:00,940 --> 00:04:05,240 and what the IPv6 prefix would look like. 67 00:04:05,240 --> 00:04:08,200 So here's how this ultimately works. 68 00:04:08,200 --> 00:04:10,990 First, we have the part of the address that's 69 00:04:10,990 --> 00:04:14,770 a given, which is the 2002. 70 00:04:14,770 --> 00:04:20,589 Then the 210 is going to be converted to this d2 right 71 00:04:20,589 --> 00:04:21,610 here. 72 00:04:21,610 --> 00:04:27,100 The 112 is going to be converted to this 70 right here. 73 00:04:27,100 --> 00:04:33,160 The 35 gets converted to the 23, and the 80 74 00:04:33,160 --> 00:04:35,590 gets converted to the 50. 75 00:04:35,590 --> 00:04:38,230 And of course, by converted, we simply 76 00:04:38,230 --> 00:04:42,290 mean we're converting the decimal into hex. 77 00:04:42,290 --> 00:04:46,150 This is how this becomes a /48, and this is what gets 78 00:04:46,150 --> 00:04:49,220 configured when we set up our devices. 79 00:04:49,220 --> 00:04:53,090 So to go over this, we, again, create an interface tunnel 100, 80 00:04:53,090 --> 00:04:57,390 but notice the IPv6 address for the tunnel. 81 00:04:57,390 --> 00:04:59,420 So this is how we would configure 82 00:04:59,420 --> 00:05:01,250 this particular tunnel. 83 00:05:01,250 --> 00:05:03,980 We would give it the address, and we configure it above. 84 00:05:03,980 --> 00:05:05,930 We would set up our tunnel source, 85 00:05:05,930 --> 00:05:10,850 and we set the tunnel mode to be IPv6 IP, 86 00:05:10,850 --> 00:05:14,810 and then we add this keyword 6to4. 87 00:05:14,810 --> 00:05:19,310 That's what tells it to look for this 2002 address 88 00:05:19,310 --> 00:05:23,180 and extract the IPv4 address from it. 89 00:05:23,180 --> 00:05:25,970 Then, of course, we're going to need a route 90 00:05:25,970 --> 00:05:28,350 to send the traffic down this tunnel. 91 00:05:28,350 --> 00:05:30,500 Now, it could be more specific. 92 00:05:30,500 --> 00:05:33,560 But in most cases, since the 2002 93 00:05:33,560 --> 00:05:36,950 is dedicated for 6to4 tunnels anyway, 94 00:05:36,950 --> 00:05:41,490 we usually just route the entire address space down the tunnel. 95 00:05:41,490 --> 00:05:45,380 So in this case, we're routing it down tunnel 100. 96 00:05:45,380 --> 00:05:50,010 So ultimately, 6to4 tunnels work very well. 97 00:05:50,010 --> 00:05:53,180 However, not everything is without drawbacks, 98 00:05:53,180 --> 00:05:55,280 and this does have some drawbacks. 99 00:05:55,280 --> 00:05:59,180 So let's go ahead and take a look. 100 00:05:59,180 --> 00:06:01,690 So the drawbacks of the 6to4 tunnels, 101 00:06:01,690 --> 00:06:05,770 the first one may already be a little bit obvious and that it 102 00:06:05,770 --> 00:06:11,470 does require the use of that reserved IPv6 address space, 103 00:06:11,470 --> 00:06:15,250 the 2002::/16. 104 00:06:15,250 --> 00:06:18,340 Now, normally speaking, that may not matter. 105 00:06:18,340 --> 00:06:24,550 However, this can definitely create a problem down the road 106 00:06:24,550 --> 00:06:26,800 when you're getting rid of tunnels, 107 00:06:26,800 --> 00:06:31,990 and you're actually going to switch over to native IPv6. 108 00:06:31,990 --> 00:06:35,620 Because if we're on native IPv6, we 109 00:06:35,620 --> 00:06:39,850 should no longer be using that reserved address space. 110 00:06:39,850 --> 00:06:44,300 We should be using normal IPv6 address space. 111 00:06:44,300 --> 00:06:46,780 So that's our first drawback. 112 00:06:46,780 --> 00:06:53,020 Another drawback is what if that IPv4 address of the site 113 00:06:53,020 --> 00:06:54,220 changes. 114 00:06:54,220 --> 00:06:58,030 That means that the IPv6 prefix for that site 115 00:06:58,030 --> 00:07:00,410 would have to change as well, and that 116 00:07:00,410 --> 00:07:03,380 may take some manual intervention to get that tunnel 117 00:07:03,380 --> 00:07:05,400 to function properly again. 118 00:07:05,400 --> 00:07:07,520 And if we're going to provide our customers 119 00:07:07,520 --> 00:07:10,560 with internet access using this solution, 120 00:07:10,560 --> 00:07:13,490 this is going to require a 6to4 relay 121 00:07:13,490 --> 00:07:16,250 router that we have to make available for them 122 00:07:16,250 --> 00:07:19,160 to step this traffic off to the internet. 123 00:07:19,160 --> 00:07:23,630 But these few drawbacks aside, 6to4 automatic tunnels 124 00:07:23,630 --> 00:07:25,730 are actually a really good solution 125 00:07:25,730 --> 00:07:33,430 for automatically configuring tunnels to send IPv6 over IPv4. 126 00:07:33,430 --> 00:07:39,430 So in this video, we took a look at automatic IPv6 tunnels, 127 00:07:39,430 --> 00:07:42,190 specifically 6to4 tunnels. 128 00:07:42,190 --> 00:07:49,090 These, of course, require the use of the 2002::/16 reserved 129 00:07:49,090 --> 00:07:50,620 address space. 130 00:07:50,620 --> 00:07:53,260 Again, if all of this is for tunneling, 131 00:07:53,260 --> 00:07:55,220 that's really not a big deal. 132 00:07:55,220 --> 00:07:58,660 But hopefully, the plan is to migrate away 133 00:07:58,660 --> 00:08:03,580 from tunnels at some point and run native IPv6. 134 00:08:03,580 --> 00:08:05,860 And if that's the case, well, we wouldn't 135 00:08:05,860 --> 00:08:09,530 want to be using these reserved address spaces anymore. 136 00:08:09,530 --> 00:08:12,460 So what would be ideal would be to have 137 00:08:12,460 --> 00:08:16,720 all the advantages of 6to4 tunnels, meaning they're 138 00:08:16,720 --> 00:08:21,400 automatic and being able to use whatever address space 139 00:08:21,400 --> 00:08:24,880 we want and assign that to the customers so 140 00:08:24,880 --> 00:08:27,040 that they could use that long term. 141 00:08:27,040 --> 00:08:30,110 Well, we actually have a solution for that, 142 00:08:30,110 --> 00:08:31,990 and we're going to look at it next. 143 00:08:31,990 --> 00:08:33,380 Till then. 144 00:08:33,380 --> 00:08:35,409 I hope this has been informative for you, 145 00:08:35,409 --> 00:08:38,459 and I'd like to thank you for viewing. 146 00:08:38,459 --> 00:08:42,000