1
00:00:09,050 --> 00:00:11,510
Let's look at IP version six routing protocols.

2
00:00:11,690 --> 00:00:17,390
Now, a lot of the routing protocols you've seen in IP version four have been updated for IP version

3
00:00:17,390 --> 00:00:17,960
six.

4
00:00:18,350 --> 00:00:20,900
IP version six uses a different address structure.

5
00:00:20,990 --> 00:00:26,330
So the IP version for routing protocols cannot be used in IP version six.

6
00:00:26,540 --> 00:00:29,570
The updated versions of the writing protocols need to be used.

7
00:00:29,780 --> 00:00:31,040
Now, some examples.

8
00:00:31,250 --> 00:00:36,140
IP version six routing types includes static routes, and I'll show you a little bit later how to set

9
00:00:36,140 --> 00:00:37,130
up static routes.

10
00:00:37,280 --> 00:00:42,830
I'm also going to show you how to set up Rip in G or Rip Next Generation, which is essentially RIP

11
00:00:42,830 --> 00:00:44,240
in IP version six.

12
00:00:44,540 --> 00:00:48,650
Now, if I were you, I would remember the various routing protocols listed here.

13
00:00:49,010 --> 00:00:50,990
Don't worry too much about the risks.

14
00:00:51,110 --> 00:00:52,980
I've put them here for completeness.

15
00:00:53,000 --> 00:00:56,540
If you really want to get into the depths of the routing protocols, have a look at these.

16
00:00:56,570 --> 00:01:03,200
RFK's OSPF version three is the version of OSPF that supports IP version six.

17
00:01:03,470 --> 00:01:11,320
We also have IS-IS for IPV six as well as multi protocol BGP version for multi protocol.

18
00:01:11,330 --> 00:01:20,030
BGP essentially supports multiple protocols, including IP version four, IP version six and VPN V for

19
00:01:20,330 --> 00:01:22,250
use in MPLS environments.

20
00:01:22,820 --> 00:01:29,990
The thing to remember is multi protocol BGP version four is the BGP version used in IPV six environments.

21
00:01:30,560 --> 00:01:35,480
IGP has also been updated, so we have IP four, IP version six.

22
00:01:35,780 --> 00:01:40,790
It's important that you remember this command in global configuration mode on a router.

23
00:01:40,820 --> 00:01:47,720
You need to top the come on IPV six unicast routing before you can enable any routing protocols on that

24
00:01:47,720 --> 00:01:48,260
router.

25
00:01:49,260 --> 00:01:50,730
So just to demonstrate that.

26
00:01:52,080 --> 00:01:52,950
He has a rather.

27
00:01:53,750 --> 00:02:01,310
So in global config mode, I'm going to type IPv6 router and let's try and enable RIP.

28
00:02:01,610 --> 00:02:06,410
And now an IP version six, you need to specify a string to identify the process.

29
00:02:06,410 --> 00:02:11,810
So let's just say rip n g and notice it says IPv6 routing is not enabled.

30
00:02:11,810 --> 00:02:16,940
So I have to type IPV six unicast routing and now.

31
00:02:17,880 --> 00:02:21,600
I can top the CM on IPv6 or rather rip with a string.

32
00:02:21,960 --> 00:02:28,500
So please don't forget you need to type a command IPV six unicast routing before enabling a routing

33
00:02:28,500 --> 00:02:32,640
protocol that supports IP version six on Cisco routers.

34
00:02:33,530 --> 00:02:37,280
Now Rep Angie is very similar to REP in IP version four.

35
00:02:37,520 --> 00:02:39,650
It's a distance vector routing protocol.

36
00:02:39,920 --> 00:02:41,930
It has a radius of 15 hops.

37
00:02:41,930 --> 00:02:43,760
16 is set to infinity.

38
00:02:43,790 --> 00:02:50,330
It still uses split horizon point and reverse, and it's based very much on REP version two.

39
00:02:50,360 --> 00:02:55,890
In other words, the version of REP used in IP version for environments, there have been updates.

40
00:02:55,910 --> 00:02:59,200
It obviously needs to support the IPV six prefix.

41
00:02:59,210 --> 00:03:01,610
In other words, support IPv6 addresses.

42
00:03:01,730 --> 00:03:07,820
Next, hop addresses or set to the IPV six address because we could run a network entirely using IP

43
00:03:07,820 --> 00:03:09,740
version six with no IP version.

44
00:03:09,740 --> 00:03:18,770
For now, it uses a multicast group of f02 colon colon nine, which is the all routers multicast group.

45
00:03:19,010 --> 00:03:23,510
That is the multicast address used for updates in rep version one.

46
00:03:23,510 --> 00:03:27,350
If you remember, RIP sends updates using broadcasts.

47
00:03:27,350 --> 00:03:31,910
Broadcasts are no longer supported in IP version six, so they cannot be used.

48
00:03:32,060 --> 00:03:37,010
Broadcasts also have some inherent disadvantages which we've covered previously.

49
00:03:37,040 --> 00:03:42,590
Rep Version two uses multicast address 224009.

50
00:03:42,590 --> 00:03:48,650
So one of the well known multicast addresses and you can see this address is very similar to version

51
00:03:48,650 --> 00:03:49,220
two.

52
00:03:49,520 --> 00:03:53,060
So in version two it's 2 to 4 009.

53
00:03:53,060 --> 00:04:00,080
In other words, that's the multicast address used in IP version four in RIP and G in IP version six,

54
00:04:00,080 --> 00:04:03,530
we use multicast address ff02 colon, colon nine.

55
00:04:03,530 --> 00:04:06,710
So at least there's some consistency in the multicast group.

56
00:04:06,710 --> 00:04:14,600
Number IP version six is used for the transport of RIP updates, RIP and G sends updates on UDP port

57
00:04:14,600 --> 00:04:15,830
521.

58
00:04:17,010 --> 00:04:20,790
Let's enable rip n g or next generation on these riders.

59
00:04:21,540 --> 00:04:27,300
So in global config mode I can type IPV six router.

60
00:04:29,080 --> 00:04:29,650
Grew up.

61
00:04:30,830 --> 00:04:35,150
And then I need to specify a string to identify this process.

62
00:04:35,420 --> 00:04:38,240
So I'm just going to call it Rep Energy one.

63
00:04:39,180 --> 00:04:41,670
And you can see that I'm now in configurator mode.

64
00:04:42,000 --> 00:04:46,080
I then need to go into my interfaces and top IPv6.

65
00:04:47,160 --> 00:04:47,850
Rip.

66
00:04:50,020 --> 00:04:51,430
The process name.

67
00:04:52,430 --> 00:04:56,180
And then top enable and I can do that on each interface.

68
00:04:58,060 --> 00:04:59,230
You don't have to do this.

69
00:04:59,230 --> 00:05:00,250
Come on first.

70
00:05:00,400 --> 00:05:03,070
But that will allow you to change various parameters.

71
00:05:04,910 --> 00:05:07,490
I can do the same thing on router two.

72
00:05:08,370 --> 00:05:11,400
The top IPV six rata.

73
00:05:18,170 --> 00:05:22,070
And we'll just change this to energy, too, because this is on route to.

74
00:05:23,100 --> 00:05:24,790
Let's go on to my interfaces.

75
00:05:35,210 --> 00:05:36,170
And we've now enabled.

76
00:05:38,180 --> 00:05:39,320
Back on router one.

77
00:05:39,320 --> 00:05:42,920
I can type the command show IPV six.

78
00:05:44,390 --> 00:05:46,910
Rut to see my routing table.

79
00:05:48,070 --> 00:05:53,000
And after a while I should see my route populate in the routing table.

80
00:05:53,020 --> 00:05:56,230
So now I can type ping 2001.

81
00:05:56,230 --> 00:05:57,160
Colon one.

82
00:05:57,160 --> 00:05:57,790
Colon one.

83
00:05:57,790 --> 00:05:59,020
Colon three.

84
00:05:59,860 --> 00:06:03,310
Colon one, which is this IP address here.

85
00:06:04,120 --> 00:06:05,860
And you can see the ping succeeds.

86
00:06:05,860 --> 00:06:09,820
So I'm able to ping from router one to router two.

87
00:06:10,270 --> 00:06:18,640
I could also do this source and specify the first Ethernet interface on router one.

88
00:06:19,290 --> 00:06:21,450
And you can see the ping succeeds.

89
00:06:21,600 --> 00:06:24,270
So it's as simple as that to set up rip.

90
00:06:25,300 --> 00:06:29,680
I could also advertise a default route from route one to Route A to.

91
00:06:32,250 --> 00:06:35,610
So going on to the serial interface, I can type the command.

92
00:06:35,640 --> 00:06:37,340
IPV six rip.

93
00:06:38,750 --> 00:06:40,280
The process name.

94
00:06:41,360 --> 00:06:43,970
And then default information originate.

95
00:06:46,630 --> 00:06:48,310
To send a default route.

96
00:06:49,000 --> 00:06:53,230
To route a to en route a tus routing table.

97
00:06:55,030 --> 00:06:57,280
So show IPV six route.

98
00:06:59,830 --> 00:07:03,310
Notice here, I'm getting a default route.

99
00:07:03,910 --> 00:07:05,890
The default route is represented by Colon.

100
00:07:05,890 --> 00:07:08,410
Colon Ford slash zero.

101
00:07:09,040 --> 00:07:15,640
Notice the administrative distance of Rip G is still 120 and we still have a hop count in this case

102
00:07:15,640 --> 00:07:16,360
of two.

103
00:07:16,510 --> 00:07:21,130
Notice he has an example looking at the route from Route one.

104
00:07:21,490 --> 00:07:27,070
So this route here is the route on Fast Ethernet zero one on route of one.

105
00:07:27,400 --> 00:07:35,950
Notice we are learning it via not to this address but via the link local address on Route one.

106
00:07:36,400 --> 00:07:43,720
So going on to Route one is an example show IPV six, interface several zero zero.

107
00:07:44,320 --> 00:07:52,150
Notice the link local address is F, E 80, C, 600 and so forth, which is the address here.

108
00:07:52,600 --> 00:07:57,220
Link Local addresses are used by routing protocols to advertise routes to one another.

109
00:07:57,880 --> 00:08:02,290
These addresses are not being used by the writing protocols to advertise the routes.

110
00:08:02,470 --> 00:08:10,030
Other commands I can type are, for instance, show IPV six rep, which shows me information about RIP.

111
00:08:10,420 --> 00:08:13,450
You can see, for instance, which interface is enabled on.

112
00:08:13,660 --> 00:08:18,220
You can see its administrative distance maximum number of ports that it supports.

113
00:08:18,220 --> 00:08:18,870
16.

114
00:08:18,880 --> 00:08:21,250
In this case, admin distance is 120.

115
00:08:21,520 --> 00:08:28,000
You can see the multicast group which if you remember back to IP version four is 224009.

116
00:08:28,240 --> 00:08:31,780
So something similar here f02.

117
00:08:31,810 --> 00:08:32,200
Colon.

118
00:08:32,200 --> 00:08:33,130
Colon nine.

119
00:08:34,250 --> 00:08:40,669
Other information very similar to version four is, for instance, updates are sent every 30 seconds,

120
00:08:40,669 --> 00:08:42,860
so they expire off 180 seconds.

121
00:08:42,890 --> 00:08:44,630
We still have split horizon.

122
00:08:44,660 --> 00:08:48,410
We still have poison reverse, and we still have hold down timers.

123
00:08:49,070 --> 00:08:55,430
I can see just the rip ruts in the routing table by tapping the command show IPV six root.

124
00:08:57,580 --> 00:09:01,360
And you can see my two routes on router two.

125
00:09:01,390 --> 00:09:08,890
We are learning a default route from router one and we are learning about this network, which is this

126
00:09:08,890 --> 00:09:15,670
one over here both via the link local address of serial zero zero on router one.

127
00:09:16,090 --> 00:09:18,790
Now let's configure OSPF on these routers.

128
00:09:18,790 --> 00:09:23,860
So in global config mode, I can type IPV six router.

129
00:09:25,650 --> 00:09:29,460
OSPF and then specify process ID of, let's say one.

130
00:09:29,760 --> 00:09:31,140
Notice what it says.

131
00:09:31,260 --> 00:09:39,840
OSPF version three Process one could not pick a router ID even though this is OSPF version three.

132
00:09:39,840 --> 00:09:42,540
In other words, OSPF IP version six.

133
00:09:42,540 --> 00:09:45,180
It requires a router ID.

134
00:09:45,910 --> 00:09:48,010
In IP version for format.

135
00:09:48,520 --> 00:09:50,770
So I'm going to put that in as quadruple one.

136
00:09:51,750 --> 00:09:55,440
You need to go to the interfaces to put them into the various areas.

137
00:09:55,440 --> 00:09:57,390
So I'm going to type IPV six.

138
00:09:58,390 --> 00:09:59,350
OSPF.

139
00:10:00,280 --> 00:10:03,350
Process ideas one specify an area.

140
00:10:03,370 --> 00:10:06,190
In this case, I'll specify area one.

141
00:10:07,390 --> 00:10:08,650
On the serial interface.

142
00:10:08,650 --> 00:10:10,510
I'll put that into Area Zero.

143
00:10:11,350 --> 00:10:13,270
We need to do the same thing on router two.

144
00:10:13,570 --> 00:10:17,830
So IPV six router OSPF.

145
00:10:18,340 --> 00:10:20,050
Let's just make this process to.

146
00:10:21,450 --> 00:10:22,060
Give it a rata.

147
00:10:22,080 --> 00:10:22,800
I'd.

148
00:10:23,930 --> 00:10:28,580
The quadruple to go onto the first Ethernet interface.

149
00:10:29,180 --> 00:10:30,410
IPV six.

150
00:10:31,530 --> 00:10:33,360
OSPF too.

151
00:10:33,540 --> 00:10:35,250
In other words, our process ID.

152
00:10:37,210 --> 00:10:44,410
And let's put this into area to go on to the serial interface and let's put that into area zero.

153
00:10:44,620 --> 00:10:47,110
So hopefully we should form a neighbor relationship.

154
00:10:47,110 --> 00:10:49,270
And as you can see there, it's taken place.

155
00:10:49,780 --> 00:10:51,380
The relationship has gone to full.

156
00:10:51,400 --> 00:10:54,520
So hopefully we should get roots from router one.

157
00:10:54,520 --> 00:10:57,370
So show IPV six root.

158
00:10:58,240 --> 00:11:07,210
Notice here we have received an OSPF into area route from router one telling us about this network.

159
00:11:07,720 --> 00:11:12,760
Notice there's no one at the end here because that is a network address, not a host address.

160
00:11:13,870 --> 00:11:16,900
So on router one, let's create a loopback interface.

161
00:11:17,410 --> 00:11:24,100
So give it an IPV six address of let's say 2002 colon.

162
00:11:24,100 --> 00:11:25,630
Colon one slash 64.

163
00:11:26,650 --> 00:11:28,440
Put that into OSPF area.

164
00:11:28,570 --> 00:11:29,290
One.

165
00:11:30,440 --> 00:11:34,460
And then back on route to it's only look at OSPF routes.

166
00:11:37,340 --> 00:11:38,420
And here you go.

167
00:11:38,870 --> 00:11:46,280
We've now learned about the loopback on router one through OSPF and it's displayed in the routing table

168
00:11:46,280 --> 00:11:47,330
of router two.

169
00:11:48,110 --> 00:11:53,570
I could ping 2000 to colon colon one or the colon colon one.

170
00:11:53,990 --> 00:11:56,840
And as you can see there, the ping is successful.

171
00:11:57,200 --> 00:12:00,700
It's as simple as that to set up OSPF version three.

172
00:12:00,710 --> 00:12:03,830
In other words, OSPF for IP version six.

173
00:12:05,060 --> 00:12:09,200
Now it's important to realize that we are only running IP version six on these routers.

174
00:12:09,590 --> 00:12:16,520
For example, if I type show IP route, you'll notice there are no routes on router one and a router

175
00:12:16,520 --> 00:12:21,910
to the routing table displays in the same way that they are no routes.

176
00:12:21,920 --> 00:12:26,690
There are no IP version four addresses configured on these routers, so nothing gets displayed in the

177
00:12:26,690 --> 00:12:27,590
routing table.

178
00:12:27,740 --> 00:12:30,680
It is possible to run both protocols at the same time.

179
00:12:30,950 --> 00:12:38,690
So on router two on the serial interface, let's configure an IP address of 10.1 2.2.

180
00:12:41,110 --> 00:12:43,090
And now if our top show IP rot.

181
00:12:43,840 --> 00:12:47,680
Notice that rot appears in the routing table on router one.

182
00:12:47,680 --> 00:12:53,020
There are still no routes because no IP version for addresses have been configured, but on the serial

183
00:12:53,020 --> 00:12:57,550
zero interface I could do something like IP address ten one two, one.

184
00:12:58,360 --> 00:12:59,350
With a mosque.

185
00:13:00,050 --> 00:13:03,140
And now the writing table will display that rot.

186
00:13:03,770 --> 00:13:05,090
So I could ping ten.

187
00:13:05,090 --> 00:13:07,130
One, two, two.

188
00:13:08,160 --> 00:13:10,290
Which is the IP address of router two.

189
00:13:10,830 --> 00:13:13,740
Or I could ping 2001.

190
00:13:13,740 --> 00:13:14,370
Colin one.

191
00:13:14,370 --> 00:13:15,180
Colin one.

192
00:13:15,360 --> 00:13:16,620
Colin two.

193
00:13:16,710 --> 00:13:18,030
Colin Colon two.

194
00:13:18,060 --> 00:13:21,270
Which is the IP version six address of router RT.

195
00:13:21,840 --> 00:13:24,600
I could also, for instance, try and tell it to the router.

196
00:13:27,660 --> 00:13:31,080
And as you can see, it says password required, but none set.

197
00:13:37,750 --> 00:13:39,040
And I could do the same.

198
00:13:41,030 --> 00:13:42,620
In IP version six.

199
00:13:42,890 --> 00:13:47,000
So on router two, let's create a VI password.

200
00:13:47,870 --> 00:13:55,760
So password cisco create an enable password of Cisco and now let's try and telnet from router one to

201
00:13:55,760 --> 00:13:57,530
write it to using IP version six.

202
00:13:58,010 --> 00:14:04,280
And as you can see here, we are able to telnet successfully and doing it in IP version four.

203
00:14:04,670 --> 00:14:07,040
Notice we are able to telnet successfully.

204
00:14:07,160 --> 00:14:12,740
In other words, both protocols can be run at the same time, running side by side.

205
00:14:13,070 --> 00:14:16,400
This is known once again as running a dual stack.

206
00:14:16,880 --> 00:14:22,460
Both the IP version for Stack and the IP version six stack are running side by side.

207
00:14:23,500 --> 00:14:28,450
You can also clear the SBF process in a similar fashion to IP version four.

208
00:14:28,480 --> 00:14:30,350
You just literally type clear.

209
00:14:30,430 --> 00:14:31,810
IPV six.

210
00:14:31,900 --> 00:14:33,820
OSPF process.

211
00:14:35,080 --> 00:14:37,360
And that clears the OSPF processes.

212
00:14:37,780 --> 00:14:41,740
You can see the neighbor relationship was torn down and then re-established.

213
00:14:42,370 --> 00:14:47,710
So a lot of the concepts of very similar between IP version four and IP version six.

214
00:14:48,590 --> 00:14:54,260
Another example of a command that's very similar in IP version six as in IP version four is you can

215
00:14:54,260 --> 00:15:01,400
do the command IPV six hostname and now specify a host name, let's say or two, and then I can specify

216
00:15:01,400 --> 00:15:02,210
its address.

217
00:15:05,590 --> 00:15:11,230
So now if I ping or to do that again, notice that ping succeeds.

218
00:15:12,720 --> 00:15:16,710
Let's look at some of the IP version for two IP version six transition mechanisms.

219
00:15:16,920 --> 00:15:19,770
There is fortunately transition richness.

220
00:15:19,800 --> 00:15:22,980
In other words, there is no fixed date to convert.

221
00:15:23,310 --> 00:15:30,090
This is not like Y2K, where the whole world was supposedly going to fall apart at the end of 1999.

222
00:15:30,330 --> 00:15:32,640
There's no need for all of us to convert at once.

223
00:15:32,970 --> 00:15:37,020
However, this is becoming very important, as I mentioned earlier.

224
00:15:37,470 --> 00:15:44,040
As I'm recording this a week ago, the available IP version for address space was exhausted.

225
00:15:44,310 --> 00:15:49,710
So it's becoming critical now for businesses to look at ways to transition to IP version six.

226
00:15:50,010 --> 00:15:52,650
There are multiple transmission mechanisms available.

227
00:15:53,490 --> 00:15:59,250
The first one is what's called running a dual stack, where you run both IP version four and IP version

228
00:15:59,250 --> 00:16:03,180
six at the same time on a single host.

229
00:16:03,210 --> 00:16:08,670
So this MacBook, for example, has an IP version four address as well as an IP version six address.

230
00:16:08,970 --> 00:16:16,710
When the MacBook is communicating to the server, it can use IP version four, but when communicating

231
00:16:16,710 --> 00:16:20,130
to this server, it can use IP version six.

232
00:16:20,700 --> 00:16:27,000
So this is the typical analogy where a person can speak two languages and as an analogy would speak

233
00:16:27,000 --> 00:16:34,020
English to one server and French to another server, but in this case IPV four to the server that only

234
00:16:34,020 --> 00:16:39,630
runs IPV four and IPV six to the server that only runs IP version six.

235
00:16:40,700 --> 00:16:42,740
A lot of operating systems support this.

236
00:16:43,160 --> 00:16:43,850
Here's an example.

237
00:16:43,850 --> 00:16:46,190
In Windows, I can pick 172.

238
00:16:47,460 --> 00:16:49,980
I can pick 120 7001.

239
00:16:50,830 --> 00:16:52,660
The loopback in IP version four.

240
00:16:53,020 --> 00:16:57,610
And once again, I can ping the loopback in IP version six.

241
00:16:59,000 --> 00:17:05,420
This Windows machine supports both protocols, and in this case, based on the address, a specific

242
00:17:05,420 --> 00:17:06,710
protocol is chosen.

243
00:17:07,660 --> 00:17:11,200
So in this example, we're looking at an IP version for protocol stack.

244
00:17:11,560 --> 00:17:15,790
In this example, the application being used only supports IP version four.

245
00:17:16,000 --> 00:17:23,410
So when data is sent from the application layer down to the physical layer, the application will choose

246
00:17:23,410 --> 00:17:26,170
whether it's using TCP or UDP at layer four.

247
00:17:26,410 --> 00:17:30,010
It will then use the IP version for protocol stack at layer three.

248
00:17:30,280 --> 00:17:35,140
At Layer two, the Ethernet type would be set to zero x 800.

249
00:17:35,140 --> 00:17:39,970
If this is an Ethernet to frame, that would then be forwarded across the physical medium.

250
00:17:39,970 --> 00:17:47,410
In this case, Ethernet, if an application supports both IP version four and IP version six, the application

251
00:17:47,410 --> 00:17:51,790
may choose either TCP or UDP, depending on how it's been programmed.

252
00:17:51,790 --> 00:17:54,820
And then the protocol stack at layer three would be chosen.

253
00:17:54,820 --> 00:17:58,600
Are we using IP version four or are we using IP version six?

254
00:17:58,840 --> 00:18:04,510
So the choice of protocol stack would be determined by, for instance, the destination IP address that

255
00:18:04,510 --> 00:18:10,540
we're going to or by using a DNS server that determines which protocol stack is used.

256
00:18:10,870 --> 00:18:17,140
The application programming interface or API of the application needs to be able to handle IP version

257
00:18:17,140 --> 00:18:19,180
six formatted addresses.

258
00:18:19,330 --> 00:18:25,930
So as I've shown you previously in HTTP, the IP version six address would have to be put in brackets.

259
00:18:26,470 --> 00:18:29,830
So the application would need to be able to handle those address formats.

260
00:18:29,830 --> 00:18:37,030
For example, the Ethernet type would then be chosen once again, if it's version four of IP, the Ethernet

261
00:18:37,030 --> 00:18:39,160
type would be set to zero x 800.

262
00:18:39,400 --> 00:18:44,310
But if it's IP version six, the Ethernet type would be set to 0x86 DX.

263
00:18:44,650 --> 00:18:47,740
That would then be forwarded across the physical medium.

264
00:18:47,740 --> 00:18:54,310
So when data is sent from an application, let's say Internet Explorer, depending on various parameters,

265
00:18:54,310 --> 00:19:00,880
for example, the URL that you specify in the browser, the data would be sent across the IP version

266
00:19:00,880 --> 00:19:06,490
six stack or across the IP version four stack down to the physical medium.

267
00:19:07,440 --> 00:19:10,470
Another transmission mechanism is to use tunnelling.

268
00:19:10,500 --> 00:19:15,180
In this example, we have a host on the left hand side that is running IP version six.

269
00:19:15,390 --> 00:19:20,430
On the right hand side, the server is running IP version six, but the routers are connected by an

270
00:19:20,430 --> 00:19:22,620
IP version for only network.

271
00:19:22,950 --> 00:19:26,580
So IP version six addresses will not be routed by this infrastructure.

272
00:19:26,760 --> 00:19:33,600
So what you can do is you can set up a tunnel between router one and router two to tunnel IP version

273
00:19:33,600 --> 00:19:35,550
six over IP version.

274
00:19:35,550 --> 00:19:38,070
For there are multiple ways to do this.

275
00:19:38,070 --> 00:19:44,940
You can either use manual tunneling or dynamic 64 tunneling or intra site automatic tunnel addressing

276
00:19:44,940 --> 00:19:45,690
protocol.

277
00:19:46,080 --> 00:19:48,600
Or lastly, you can use Teredo tunneling.

278
00:19:49,020 --> 00:19:51,540
Now let's look at each of those in more depth.

279
00:19:52,080 --> 00:19:58,350
So he has an example of tunneling IP version six packets over an IP version for infrastructure, the

280
00:19:58,350 --> 00:20:05,580
MacBook on the left hand side since IP version six data inside of an IP version six header to its default

281
00:20:05,580 --> 00:20:13,440
gateway, which is, let's say, router one router one will then take the IP version six information

282
00:20:13,440 --> 00:20:16,470
and encapsulated inside IP version four.

283
00:20:16,980 --> 00:20:24,960
A tunnel is set up from the local IP version for address of router one to the remote IP address on router

284
00:20:24,960 --> 00:20:25,530
two.

285
00:20:25,980 --> 00:20:29,460
So please note this is an extra IP header.

286
00:20:29,490 --> 00:20:36,270
In other words, an IP version for header is dependent to the front of the IP version six header encapsulates

287
00:20:36,270 --> 00:20:38,010
the IP version six information.

288
00:20:38,430 --> 00:20:44,130
So routers in the IP version for infrastructure, never see the IP version six header.

289
00:20:44,310 --> 00:20:47,280
They're only see the IP version four header.

290
00:20:47,730 --> 00:20:50,100
Now I've shown more detail of the IP version four header.

291
00:20:50,220 --> 00:20:54,600
I've shown you the source and destination addresses, but this is part of the same header.

292
00:20:54,780 --> 00:21:01,260
When the packet gets to router two, the IP version four headers are stripped off and the packet is

293
00:21:01,260 --> 00:21:05,760
sent on the remote LAN as a pure IP version six packet.

294
00:21:06,740 --> 00:21:11,210
Now when setting up tunneling, it's important to remember that the protocol type is 41.

295
00:21:11,360 --> 00:21:15,920
So the IP version six packet is encapsulated within IP version four.

296
00:21:15,920 --> 00:21:22,490
And when IP version four encapsulates that IP version six packet, a protocol type of 41 is specified

297
00:21:22,490 --> 00:21:23,990
in the IP version four header.

298
00:21:24,470 --> 00:21:29,990
TCP, for example, has a protocol type of six and UDP protocol type of 17.

299
00:21:30,230 --> 00:21:34,550
And in this case, IP version six is set to protocol type 41.

300
00:21:35,030 --> 00:21:38,810
The head is 20 bytes in size when there are no options.

301
00:21:39,170 --> 00:21:40,580
This can cause some problems.

302
00:21:40,580 --> 00:21:49,070
The maximum transmission unit between our two hosts, the MacBook and the server is reduced by 20 bytes

303
00:21:49,070 --> 00:21:54,860
because of this additional header can be difficult to troubleshoot issues with tunneling.

304
00:21:54,890 --> 00:22:01,220
As an example, the routers in this cloud could be blocking Protocol 41 and would need to be changed

305
00:22:01,220 --> 00:22:02,660
to allow that traffic through.

306
00:22:03,020 --> 00:22:09,740
In manual tunneling, you are manually establishing the tunnel between router one and router two and

307
00:22:09,740 --> 00:22:12,440
I'm going to demonstrate how to do that a little bit later.

308
00:22:12,770 --> 00:22:19,790
With dynamic 6 to 4 tunneling, the tunnel is automatically established between the IPV six networks

309
00:22:19,790 --> 00:22:26,180
through the IP version for network pre setting of source and destination IP version four addresses is

310
00:22:26,180 --> 00:22:28,790
not required for these automatic tunnels.

311
00:22:29,060 --> 00:22:36,170
Automatic prefix assignment is where one aggregate global unicast IPV six prefix is assigned to each

312
00:22:36,170 --> 00:22:37,430
6 to 4 site.

313
00:22:37,790 --> 00:22:42,740
And these are based on the specific address 2002 colon.

314
00:22:42,740 --> 00:22:46,220
Colon slash 16 assigned by the honor.