1
00:00:09,070 --> 00:00:11,880
Let's look at IP version 6 routing protocols.

2
00:00:11,880 --> 00:00:19,000
Now a lot of the routing protocols you've seen in provision for have been updated for IP version 6 version

3
00:00:19,020 --> 00:00:21,040
6 uses a different address structure.

4
00:00:21,240 --> 00:00:26,670
So the key version for writing protocols cannot be used in IP version 6.

5
00:00:26,670 --> 00:00:29,940
The updated versions of the routing protocols need to be used.

6
00:00:29,940 --> 00:00:35,460
Now some examples like Version 6 routing types include static routes and I'll show you a little bit

7
00:00:35,460 --> 00:00:37,460
later how to set up static routes.

8
00:00:37,470 --> 00:00:43,140
I'm also going to show you how to set up rip in G or rip next generation which is essentially REPP in

9
00:00:43,140 --> 00:00:44,620
IP version 6.

10
00:00:44,760 --> 00:00:48,940
If I were you I would remember the various routing protocols listed here.

11
00:00:49,170 --> 00:00:51,080
Don't worry too much about the Archies.

12
00:00:51,250 --> 00:00:53,090
I put them here for completeness.

13
00:00:53,230 --> 00:00:58,350
If you really want to get into the depth of the routing protocols have a look at these or it sees OSPF

14
00:00:58,350 --> 00:01:03,600
version 3 is a version of OSPF that supports IP version 6.

15
00:01:03,600 --> 00:01:13,140
We also have ISIS for IPV 6 as well as multi protocol BGP version for multi protocol BGP essentially

16
00:01:13,140 --> 00:01:22,890
supports multiple protocols including IP version for IP version 6 and VPN before use NPL environments.

17
00:01:22,920 --> 00:01:30,650
The thing to remember is multi protocol BGP version 4 is the BGP version used in IPV six environments.

18
00:01:30,730 --> 00:01:32,810
The GOP is also been updated.

19
00:01:33,060 --> 00:01:36,010
So we have a UI GOP for IP version 6.

20
00:01:36,030 --> 00:01:40,820
It's important that you remember this command in global configuration mode on a router.

21
00:01:40,920 --> 00:01:41,560
It needs it up.

22
00:01:41,570 --> 00:01:48,390
Come on ITV 6 unicast routing before you can enable any routing protocols on that router.

23
00:01:49,500 --> 00:01:59,040
So just to demonstrate that he has a router saying Global config mode I'm going to type IPV six Rodda

24
00:01:59,670 --> 00:02:06,540
and let's try enable rep and now an IP version 6 you need to specify a string to identify the reprocess

25
00:02:06,540 --> 00:02:11,930
Alysha say RIP N-G and notice it says IPV 6 routing is not enabled.

26
00:02:12,110 --> 00:02:21,000
So I have to type IP V-6 unique cache routing and now I can tap the come on ITV 6 for router rep with

27
00:02:21,000 --> 00:02:21,870
a string.

28
00:02:22,170 --> 00:02:29,190
So please don't forget you need to top the common IP V-6 unicast routing before enabling a routing protocol

29
00:02:29,640 --> 00:02:33,540
that supports IP version 6 on Cisco routers.

30
00:02:33,660 --> 00:02:40,020
Now rip Engy is very similar to repped in IP version for it's a distance vector routing protocol.

31
00:02:40,110 --> 00:02:43,970
It has a radius of 15 hops 16 is set to infinity.

32
00:02:44,040 --> 00:02:50,600
It still use a split horizon poison reverse and it's based very much on repletion too.

33
00:02:50,610 --> 00:02:54,710
In other words the version of REPP used an IP version for environments.

34
00:02:54,750 --> 00:02:56,060
There have been updates.

35
00:02:56,100 --> 00:02:59,330
It obviously needs to support the IP V-6 Prefect's.

36
00:02:59,370 --> 00:03:05,310
In other words support IPV six addresses next Hoppa addresses are set to the IP V-6 address because

37
00:03:05,310 --> 00:03:12,210
we could run a network entirely using IP version 6 with no IP version for now it uses a multicast group

38
00:03:12,330 --> 00:03:20,250
of 5 0 to call uncurling 9 which is the all the routers multi-course group that is the multi-course

39
00:03:20,250 --> 00:03:22,600
address used for rep updates.

40
00:03:22,790 --> 00:03:29,910
In one if you remember Ripp sends updates using broadcasts broadcasts are no longer supported in IP

41
00:03:29,910 --> 00:03:30,720
version 6.

42
00:03:30,720 --> 00:03:37,100
So they cannot be used broadcasts also have some inherent disadvantages which we've covered previously.

43
00:03:37,320 --> 00:03:42,860
Reversion to uses multicast address 2 2 4 0 0 9.

44
00:03:42,870 --> 00:03:48,720
So one of the well-known multi-course addresses and you can see this address is very similar to version

45
00:03:48,720 --> 00:03:53,220
2 and version 2 it's 2 2 4 0 0 9.

46
00:03:53,220 --> 00:04:00,270
In other words that's the multi-course address used in IP version for encrypt N-G in IP version 6 we

47
00:04:00,270 --> 00:04:03,620
use multicast address F-0 to call uncolored 9.

48
00:04:03,780 --> 00:04:10,290
So let's say some consistency in the multicast group number IP version 6 is used for the transport of

49
00:04:10,290 --> 00:04:11,400
Ripp updates.

50
00:04:11,430 --> 00:04:11,690
REP.

51
00:04:11,710 --> 00:04:22,070
N-G since updates on UDP port five to one that's an rope Engy or Next-Generation on these routers saying

52
00:04:22,100 --> 00:04:30,810
Global config mode can top V-6 Virata repped.

53
00:04:31,050 --> 00:04:35,560
And then I need to specify a string to identify this process.

54
00:04:35,640 --> 00:04:42,490
I'm just going to call it in G one and you can see that I'm now in can figure out a mode or they need

55
00:04:42,490 --> 00:04:55,280
to go into my interfaces and top IPV 6 rub the process name and then top enable and I can do that on

56
00:04:55,280 --> 00:04:56,290
each interface.

57
00:04:58,280 --> 00:05:05,460
You don't have to do this on first but that will allow you to change various parameters I can do the

58
00:05:05,460 --> 00:05:13,590
same thing on rockety the top IPV six Rodda.

59
00:05:18,200 --> 00:05:22,080
I would just change this to ngi too because this is on route.

60
00:05:23,360 --> 00:05:24,710
Gone to my interface's

61
00:05:35,400 --> 00:05:39,150
and we've now enabled REPP back in Rodda.

62
00:05:39,230 --> 00:05:41,300
I can top the C'mon show.

63
00:05:41,560 --> 00:05:52,410
IPV 6 rocks to see my writing table and after a while I should see my roots populate in the writing

64
00:05:52,410 --> 00:05:53,360
table.

65
00:05:53,390 --> 00:06:02,720
Sandakan taught ping 2001 Colan one color one color and three color on one which is this IP address

66
00:06:02,840 --> 00:06:06,350
the and you can see the pink succeeds some.

67
00:06:06,380 --> 00:06:10,080
Able to ping from router 1 to router.

68
00:06:10,420 --> 00:06:20,320
I could also do this source and specify the first ethernet interface on router one and you can see the

69
00:06:20,320 --> 00:06:21,610
ping succeeds.

70
00:06:21,850 --> 00:06:25,410
So it's as simple as that to set up a.

71
00:06:25,440 --> 00:06:29,580
I could also advertise a default route from router one to a T

72
00:06:32,440 --> 00:06:34,730
so going on to the serial interface.

73
00:06:34,770 --> 00:06:35,400
I can top that.

74
00:06:35,400 --> 00:06:37,330
C'mon IPV 6.

75
00:06:38,860 --> 00:06:43,880
The process name and then default information originate

76
00:06:46,800 --> 00:06:57,160
you send a default dropped shrouded team on ratus writing table so show IPV six route

77
00:07:00,050 --> 00:07:01,310
notice here.

78
00:07:01,490 --> 00:07:08,970
I'm getting a default route the default route is represented by code uncurl on Ford slash Zira.

79
00:07:09,200 --> 00:07:15,140
Notice the administrative distance of rep in G is still 120 and we still have a hop count.

80
00:07:15,170 --> 00:07:21,410
In this case of to notice she has an example looking at the route from Route 1.

81
00:07:21,680 --> 00:07:24,920
So this rack here is the raft on Phos.

82
00:07:24,920 --> 00:07:34,610
Ethan It's 0 1 1 one notice we are learning it to Vire not to this address but via the link local address

83
00:07:34,850 --> 00:07:36,250
on router 1.

84
00:07:36,620 --> 00:07:44,010
So going on to Route 1 is an example show Ickey V-6 interface Saral 0 0.

85
00:07:44,510 --> 00:07:46,190
Notice the link local addresses.

86
00:07:46,200 --> 00:07:55,190
If 80 C 600 and so forth which is the address here link local addresses are used by writing protocols

87
00:07:55,190 --> 00:07:57,580
to ever type routes to one another.

88
00:07:58,070 --> 00:08:03,410
These addresses are not being used by the routing protocols to advertise the rats other commands I can

89
00:08:03,410 --> 00:08:11,660
type of points that show IP V-6 rep which shows me information about Ripp you can see for instance which

90
00:08:11,690 --> 00:08:13,620
interfaces repens enabled on.

91
00:08:13,850 --> 00:08:19,840
You can see it's administrative distance max number of pause that it supports 16 in this case Edmon

92
00:08:19,850 --> 00:08:21,740
distances 120.

93
00:08:21,740 --> 00:08:28,130
You can see the multicast group which if you remember back to Activision Foy's 2 2 4 0 0 9.

94
00:08:28,430 --> 00:08:38,170
So something similar here if if 0 2 color and color 9 other information very similar to version 4 is

95
00:08:38,190 --> 00:08:40,700
for instance updates are sent every 30 seconds.

96
00:08:40,710 --> 00:08:43,140
So they expire after 180 seconds.

97
00:08:43,140 --> 00:08:44,880
We still have split horizon.

98
00:08:44,910 --> 00:08:49,090
We still have poison reverse and we still have hold on timers.

99
00:08:49,200 --> 00:08:57,970
I can see just the reports in the writing table by tapping the C'mon show IPV six wrocht repr and you

100
00:08:57,970 --> 00:09:01,450
can see my two routes on Route 2.

101
00:09:01,600 --> 00:09:08,950
We are learning a default dropped from router 1 and we are learning about this network which is this

102
00:09:08,950 --> 00:09:16,210
one over here both by the linked local address of serial 0 0 on router 1.

103
00:09:16,210 --> 00:09:27,870
Now lets configure OSPF on these routers so in global config mode I can type IPV 6 Varada OSPF and specify

104
00:09:27,880 --> 00:09:29,940
process id of let's say 1.

105
00:09:29,980 --> 00:09:39,190
Notice what it says OSPF version 3 Crossus one could not pick errata ID even though this is OSPF version

106
00:09:39,190 --> 00:09:39,970
3.

107
00:09:39,970 --> 00:09:42,730
In other words OSPF IP version 6.

108
00:09:42,730 --> 00:09:48,220
It requires a router ID in IP version 4 format.

109
00:09:48,710 --> 00:09:51,710
So I'm going to put that in as quadruple one.

110
00:09:51,910 --> 00:09:55,580
You need to go to the interfaces to put them into the various areas.

111
00:09:55,600 --> 00:10:03,450
So I'm going to type IP V-6 OSPF process ID is one specified area.

112
00:10:03,560 --> 00:10:08,770
In this case I'll specify area 1 on the serial interface.

113
00:10:08,780 --> 00:10:10,480
I'll put that into areas.

114
00:10:11,510 --> 00:10:13,460
We need to do the same thing on router 2.

115
00:10:13,790 --> 00:10:26,380
So IPV six router always IPF let's just make this process to give it a Arata ID quadruple to go into

116
00:10:26,380 --> 00:10:29,060
the 40 minute interface.

117
00:10:29,250 --> 00:10:37,140
ITV 6 OSPF to in other words a process ID.

118
00:10:37,320 --> 00:10:44,580
And let's put this into area to go into the Ciril interface and let's put that into area zero.

119
00:10:44,910 --> 00:10:47,180
So hopefully we should form a neighbor relationship.

120
00:10:47,220 --> 00:10:51,560
And as you can see it's taken place the relationship has gone to full.

121
00:10:51,600 --> 00:11:01,300
So hopefully we should get rats from Route 1 so show IPV 6 Berat notice here we have received an OSPF

122
00:11:01,390 --> 00:11:10,000
in two area route from router 1 telling us about this network notices no one at the end here because

123
00:11:10,000 --> 00:11:19,110
that is a network address not a host address so on Route 1 let's create a loopback interface so give

124
00:11:19,110 --> 00:11:24,050
it an IP V-6 the address of let's say 2002.

125
00:11:24,160 --> 00:11:32,140
Culham one slice sixty call put that into OSPF area one mid-back on Route 2.

126
00:11:32,730 --> 00:11:37,360
It's a new look at V.F. rocks.

127
00:11:37,540 --> 00:11:38,920
And here you go.

128
00:11:39,040 --> 00:11:46,300
We have now learnt about the loop back on Route 1 through OSPF and it's displayed in the writing table

129
00:11:46,390 --> 00:11:47,380
of rodded.

130
00:11:48,240 --> 00:11:51,660
I could ping 2002 Karl Cullinan.

131
00:11:52,090 --> 00:11:54,100
Or rather call and call on one.

132
00:11:54,180 --> 00:11:57,190
And as you can see they the ping is successful.

133
00:11:57,270 --> 00:12:00,870
It's as simple as that to set up OSPF version 3.

134
00:12:00,870 --> 00:12:08,040
In other words OSPF the IP version 6 that's important to realize that we are only running IP version

135
00:12:08,040 --> 00:12:09,530
6 on these routers.

136
00:12:09,750 --> 00:12:13,050
For example I type show IP route.

137
00:12:13,140 --> 00:12:20,160
You'll notice there are no routes on route a one on a router to the writing table displays in the same

138
00:12:20,160 --> 00:12:22,040
way that there are no rats.

139
00:12:22,170 --> 00:12:25,200
There are no IP version 4 addresses configured on these routers.

140
00:12:25,500 --> 00:12:27,720
So nothing gets displayed in the writing table.

141
00:12:27,960 --> 00:12:30,870
It is possible to run both protocols at the same time.

142
00:12:31,170 --> 00:12:41,940
So on router to on the serial interface lets configure an IP address of 201 to talk to and now if Alltop

143
00:12:42,010 --> 00:12:47,740
show IP route noticed that route appears in the writing table on Route 1.

144
00:12:47,870 --> 00:12:53,300
There are still no rocks because no provision for addresses have been configured on the serial Zerah

145
00:12:53,300 --> 00:12:53,870
interface.

146
00:12:53,870 --> 00:13:00,040
I could do something like IP address 10:01 to one with a mosque.

147
00:13:00,240 --> 00:13:03,740
And now the writing table will display that grot.

148
00:13:03,980 --> 00:13:10,550
So I could ping 10 one to two which is the IP address of router 2.

149
00:13:11,020 --> 00:13:19,990
Oh I could ping 2001 but on one call and one Kurland to call uncurl on te which is the IP version 6

150
00:13:20,080 --> 00:13:24,520
address of router t I could also for instance trying to telnet to the router

151
00:13:27,760 --> 00:13:30,930
and as you can see its his password required but none set

152
00:13:37,860 --> 00:13:50,930
not can do the same in version 6 so on Ratatouille let's create a Viti y password password Cisco Creadon

153
00:13:50,930 --> 00:13:53,490
enabled password of Cisco.

154
00:13:53,660 --> 00:13:58,010
And now let's try and telnet from Router one to rot to using IP version 6.

155
00:13:58,190 --> 00:14:05,630
And as you can see here we are able to telnet successfully and get an IP version for notice we are able

156
00:14:05,630 --> 00:14:07,380
to telnet successfully.

157
00:14:07,430 --> 00:14:13,220
In other words both protocols can be run at the same time running side by side.

158
00:14:13,220 --> 00:14:20,000
This is known once again as running a jewelled stack both the provision for stack and the IP version

159
00:14:20,000 --> 00:14:23,540
6 stack or running side by side.

160
00:14:23,680 --> 00:14:28,540
You can also clear the OSPF process in a similar fashion to IP version 4.

161
00:14:28,660 --> 00:14:37,910
You just literally tot clear IP V-6 OSPF crossest and that clears the OSPF processes.

162
00:14:37,970 --> 00:14:42,520
You can see the neighbor relationship was torn down and then reestablished.

163
00:14:42,530 --> 00:14:48,630
So a lot of the concepts are very similar between IP version for an IP version 6.

164
00:14:48,690 --> 00:14:54,550
Another example of a command thats very similar in IP version 6 as an IP version 4 is you can do the

165
00:14:54,550 --> 00:15:00,170
same on ITV 6 hostname and not specify a hostname lets say or two.

166
00:15:00,480 --> 00:15:05,740
And then I can specify its address.

167
00:15:05,770 --> 00:15:09,720
So now I've got ping are to do that again.

168
00:15:09,730 --> 00:15:17,080
Notice the ping succeeds let's look at some of the confusion for kabillion six transition mechanisms.

169
00:15:17,080 --> 00:15:19,990
There is fortunately transmission richness.

170
00:15:19,990 --> 00:15:23,480
In other words there is no fixed date to convert.

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

172
00:15:30,460 --> 00:15:33,130
There's no need for all of us to convert at once.

173
00:15:33,160 --> 00:15:35,530
However this is becoming very important.

174
00:15:35,680 --> 00:15:43,240
As I mentioned earlier as I'm recording this a week ago the available IP version for address space was

175
00:15:43,240 --> 00:15:44,200
exhausted.

176
00:15:44,500 --> 00:15:50,230
So it's becoming critical now for businesses to look at ways to transition to IP version 6.

177
00:15:50,230 --> 00:15:53,620
There are multiple transition mechanisms available.

178
00:15:53,650 --> 00:15:59,290
The first one is what's called Running a jewel stack where you run both IP version for an IP version

179
00:15:59,290 --> 00:16:03,460
6 at the same time on a single host.

180
00:16:03,460 --> 00:16:10,300
So this MacBook for example has an IP address as well as an IP version 6 address when the Macbook is

181
00:16:10,300 --> 00:16:12,200
communicating to the server.

182
00:16:12,490 --> 00:16:15,380
It can use my provision for.

183
00:16:15,700 --> 00:16:20,890
But when communicating to this server it can use IP version 6.

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

185
00:16:27,070 --> 00:16:30,670
English to one server and French to another server.

186
00:16:30,880 --> 00:16:38,740
But in this case IPV for the server that only runs IPV for an IP V-6 to the server that only runs IP

187
00:16:38,740 --> 00:16:40,730
version 6.

188
00:16:40,760 --> 00:16:43,010
A lot of operating system support this.

189
00:16:43,310 --> 00:16:47,470
Is an example in Windows I can ping 170.

190
00:16:47,590 --> 00:16:57,010
I can ping 127 0 0 1 the loopback an IP version for once again I can thing the loop back in IP version

191
00:16:57,010 --> 00:17:05,940
6 this Windows machine supports both protocols and in this case based on the address the specific protocol

192
00:17:05,940 --> 00:17:06,810
is chosen.

193
00:17:07,850 --> 00:17:11,480
So in this example we're looking at an IP version 4 protocols stack.

194
00:17:11,770 --> 00:17:15,980
In this example the application being used only supports IP version 4.

195
00:17:16,280 --> 00:17:23,450
So when data is sent from the application layer down to the physical layer the application will choose

196
00:17:23,570 --> 00:17:26,290
whether it's using TZP UDP Layer 4.

197
00:17:26,630 --> 00:17:32,840
It would then use the provision for protocol stack at least three add layer to that Ethernet type would

198
00:17:32,840 --> 00:17:35,210
be set to zero x 800.

199
00:17:35,210 --> 00:17:40,580
If this is an Ethernet to frame that would then be forwarded across the physical media in this case

200
00:17:40,610 --> 00:17:42,140
Ethernet.

201
00:17:42,140 --> 00:17:48,520
If an application supports both IP version for an IP version 6 the application may choose either DC

202
00:17:48,700 --> 00:17:51,910
to UDP depending on how it's been programmed.

203
00:17:52,070 --> 00:17:54,940
And then the protocol stack 3 would be chosen.

204
00:17:54,950 --> 00:17:59,060
Are we using IP version code or are we using IP version 6.

205
00:17:59,060 --> 00:18:04,580
So the choice of protocol stack would be determined by for instance the destination IP address that

206
00:18:04,580 --> 00:18:10,970
we going to or by using a DNS server that determines which protocol stack is used.

207
00:18:11,060 --> 00:18:17,180
The application programming interface or API of the application needs to be able to handle IP version

208
00:18:17,180 --> 00:18:19,550
6 formatted addresses.

209
00:18:19,570 --> 00:18:26,360
So as I've shown you previously in HGP the IP version 6 address would have to be put in brackets.

210
00:18:26,660 --> 00:18:32,100
So the application would need to be able to handle those address formats for example the infinite type

211
00:18:32,420 --> 00:18:39,470
would then be chosen once again if it's version full of IP the Senate talk would be set to 0 x a hundred.

212
00:18:39,590 --> 00:18:43,690
But if it's IP version 6 the ethernet type would be set to 0 8 6.

213
00:18:43,700 --> 00:18:48,000
DD That would then be forwarded across the physical medium.

214
00:18:48,050 --> 00:18:54,390
So when data is sent from an application let's say Internet Explorer depending on various parameters.

215
00:18:54,470 --> 00:19:01,640
For example the Jaro that you specified the browser the data would be sent across the IP version 6 stack

216
00:19:02,300 --> 00:19:09,730
all across the IP version 4 stack down to the physical medium and other transition mechanism is to use

217
00:19:09,730 --> 00:19:10,630
tunneling.

218
00:19:10,750 --> 00:19:16,210
In this example we have a host on the left hand side that is running IP version 6 on the right hand

219
00:19:16,210 --> 00:19:22,480
side the server is running IP version 6 but the rod is all connected by an IP version 4 only network

220
00:19:23,110 --> 00:19:26,720
so IP version 6 addresses will not be routed by this infrastructure.

221
00:19:26,980 --> 00:19:34,720
So what you can do is you can set up a tunnel between router 1 and router 2 to tunnel IP version 6 over

222
00:19:34,990 --> 00:19:36,400
IP version 4.

223
00:19:36,760 --> 00:19:42,430
There are multiple ways to do this you can either use manual tunneling or dynamic Sixty-Four tunneling

224
00:19:43,060 --> 00:19:46,730
or intra site or a metric ton of addressing protocol will last.

225
00:19:46,750 --> 00:19:48,990
You can use to Rito tunneling.

226
00:19:49,170 --> 00:19:51,820
Let's look at each of those in more depth.

227
00:19:52,230 --> 00:19:58,070
So as an example of tunneling IP version 6 packets over not be vision for infrastructure.

228
00:19:58,300 --> 00:20:05,650
The Mac book on the left hand side since IP version 6 data inside of an IP version 6 header to its default

229
00:20:05,650 --> 00:20:14,650
gateway which is let's say router one router one will then take the IP version 6 information and encapsulated

230
00:20:14,650 --> 00:20:23,440
inside IP version for a tunnel is set up from the local provision for address of router one to the remote

231
00:20:23,830 --> 00:20:26,130
IP address on rabbity.

232
00:20:26,230 --> 00:20:29,730
So please note this is an extra IP header.

233
00:20:29,740 --> 00:20:36,340
In other words an IP version for header is prepended to the front of the IP version 6 header encapsulates

234
00:20:36,340 --> 00:20:38,620
the IP version 6 information.

235
00:20:38,650 --> 00:20:41,120
So Rod is in the provision for infrastructure.

236
00:20:41,290 --> 00:20:44,330
Never see the IP version 6 header.

237
00:20:44,570 --> 00:20:50,220
They only see the IP version for header not sure in more detail the provision for header.

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

239
00:20:55,000 --> 00:21:02,290
When the packet gets routed to the IP version 4 head is a stripped off and a packet is sent on the remote

240
00:21:02,290 --> 00:21:06,880
LAN as a pure IP version 6 packet.

241
00:21:06,910 --> 00:21:12,460
Now when setting up tunneling it's important remember that the protocol type is 41 so the IP version

242
00:21:12,460 --> 00:21:15,950
6 package is encapsulated within IP version 4.

243
00:21:16,180 --> 00:21:22,720
And when Activision for encapsulates that IP version 6 packet a protocol type of 41 is specified in

244
00:21:22,720 --> 00:21:30,160
IP version 4 header TCAP for example has a protocol type of 6 and UDP protocol type of 17.

245
00:21:30,430 --> 00:21:35,050
And in this case IP version 6 is set to protocol 41.

246
00:21:35,140 --> 00:21:37,420
The head is 20 bytes in size.

247
00:21:37,540 --> 00:21:40,680
When there are no options this can cause some problems.

248
00:21:40,690 --> 00:21:49,170
The maximum transmission unit between our two hosts the MacBook and the server is reduced by 20 bytes.

249
00:21:49,360 --> 00:21:54,910
Because of this additional header can be difficult to troubleshoot issues with tunneling.

250
00:21:55,150 --> 00:22:01,420
As an example the rod is in the cloud could be blocking protocol 41 and would need to be changed to

251
00:22:01,420 --> 00:22:04,520
allow that traffic through in manual tunneling.

252
00:22:04,530 --> 00:22:10,720
You are mentally establishing the tunnel between Route 1 and router 2 and I'm going to demonstrate how

253
00:22:10,720 --> 00:22:12,650
to do that a little bit later.

254
00:22:13,000 --> 00:22:20,260
With dynamic 64 tunneling the tunnel is automatically established between the IP B-6 networks through

255
00:22:20,260 --> 00:22:27,130
the IP version for network Preece setting of source and destination IP version 4 addresses is not required

256
00:22:27,130 --> 00:22:34,240
for these automatic tunnel's automatic prefix assignment is way one aggregated global unicast IPV 6

257
00:22:34,240 --> 00:22:42,220
prefix is assigned to each Sixty-Four site and these are based on the specific address 2002.

258
00:22:42,370 --> 00:22:46,160
Colon colon slash 16 assigned by the on.