Let's look at IP version six routing protocols.
Now, a lot of the routing protocols you've seen in IP version four have been updated for IP version
six.
IP version six uses a different address structure.
So the IP version for routing protocols cannot be used in IP version six.
The updated versions of the writing protocols need to be used.
Now, some examples.
IP version six routing types includes static routes, and I'll show you a little bit later how to set
up static routes.
I'm also going to show you how to set up Rip in G or Rip Next Generation, which is essentially RIP
in IP version six.
Now, if I were you, I would remember the various routing protocols listed here.
Don't worry too much about the risks.
I've put them here for completeness.
If you really want to get into the depths of the routing protocols, have a look at these.
RFK's OSPF version three is the version of OSPF that supports IP version six.
We also have IS-IS for IPV six as well as multi protocol BGP version for multi protocol.
BGP essentially supports multiple protocols, including IP version four, IP version six and VPN V for
use in MPLS environments.
The thing to remember is multi protocol BGP version four is the BGP version used in IPV six environments.
IGP has also been updated, so we have IP four, IP version six.
It's important that you remember this command in global configuration mode on a router.
You need to top the come on IPV six unicast routing before you can enable any routing protocols on that
router.
So just to demonstrate that.
He has a rather.
So in global config mode, I'm going to type IPv6 router and let's try and enable RIP.
And now an IP version six, you need to specify a string to identify the process.
So let's just say rip n g and notice it says IPv6 routing is not enabled.
So I have to type IPV six unicast routing and now.
I can top the CM on IPv6 or rather rip with a string.
So please don't forget you need to type a command IPV six unicast routing before enabling a routing
protocol that supports IP version six on Cisco routers.
Now Rep Angie is very similar to REP in IP version four.
It's a distance vector routing protocol.
It has a radius of 15 hops.
16 is set to infinity.
It still uses split horizon point and reverse, and it's based very much on REP version two.
In other words, the version of REP used in IP version for environments, there have been updates.
It obviously needs to support the IPV six prefix.
In other words, support IPv6 addresses.
Next, hop addresses or set to the IPV six address because we could run a network entirely using IP
version six with no IP version.
For now, it uses a multicast group of f02 colon colon nine, which is the all routers multicast group.
That is the multicast address used for updates in rep version one.
If you remember, RIP sends updates using broadcasts.
Broadcasts are no longer supported in IP version six, so they cannot be used.
Broadcasts also have some inherent disadvantages which we've covered previously.
Rep Version two uses multicast address 224009.
So one of the well known multicast addresses and you can see this address is very similar to version
two.
So in version two it's 2 to 4 009.
In other words, that's the multicast address used in IP version four in RIP and G in IP version six,
we use multicast address ff02 colon, colon nine.
So at least there's some consistency in the multicast group.
Number IP version six is used for the transport of RIP updates, RIP and G sends updates on UDP port
521.
Let's enable rip n g or next generation on these riders.
So in global config mode I can type IPV six router.
Grew up.
And then I need to specify a string to identify this process.
So I'm just going to call it Rep Energy one.
And you can see that I'm now in configurator mode.
I then need to go into my interfaces and top IPv6.
Rip.
The process name.
And then top enable and I can do that on each interface.
You don't have to do this.
Come on first.
But that will allow you to change various parameters.
I can do the same thing on router two.
The top IPV six rata.
And we'll just change this to energy, too, because this is on route to.
Let's go on to my interfaces.
And we've now enabled.
Back on router one.
I can type the command show IPV six.
Rut to see my routing table.
And after a while I should see my route populate in the routing table.
So now I can type ping 2001.
Colon one.
Colon three.
Colon one, which is this IP address here.
And you can see the ping succeeds.
So I'm able to ping from router one to router two.
I could also do this source and specify the first Ethernet interface on router one.
And you can see the ping succeeds.
So it's as simple as that to set up rip.
I could also advertise a default route from route one to Route A to.
So going on to the serial interface, I can type the command.
IPV six rip.
The process name.
And then default information originate.
To send a default route.
To route a to en route a tus routing table.
So show IPV six route.
Notice here, I'm getting a default route.
The default route is represented by Colon.
Colon Ford slash zero.
Notice the administrative distance of Rip G is still 120 and we still have a hop count in this case
of two.
Notice he has an example looking at the route from Route one.
So this route here is the route on Fast Ethernet zero one on route of one.
Notice we are learning it via not to this address but via the link local address on Route one.
So going on to Route one is an example show IPV six, interface several zero zero.
Notice the link local address is F, E 80, C, 600 and so forth, which is the address here.
Link Local addresses are used by routing protocols to advertise routes to one another.
These addresses are not being used by the writing protocols to advertise the routes.
Other commands I can type are, for instance, show IPV six rep, which shows me information about RIP.
You can see, for instance, which interface is enabled on.
You can see its administrative distance maximum number of ports that it supports.
16.
In this case, admin distance is 120.
You can see the multicast group which if you remember back to IP version four is 224009.
So something similar here f02.
Colon.
Colon nine.
Other information very similar to version four is, for instance, updates are sent every 30 seconds,
so they expire off 180 seconds.
We still have split horizon.
We still have poison reverse, and we still have hold down timers.
I can see just the rip ruts in the routing table by tapping the command show IPV six root.
And you can see my two routes on router two.
We are learning a default route from router one and we are learning about this network, which is this
one over here both via the link local address of serial zero zero on router one.
Now let's configure OSPF on these routers.
So in global config mode, I can type IPV six router.
OSPF and then specify process ID of, let's say one.
Notice what it says.
OSPF version three Process one could not pick a router ID even though this is OSPF version three.
In other words, OSPF IP version six.
It requires a router ID.
In IP version for format.
So I'm going to put that in as quadruple one.
You need to go to the interfaces to put them into the various areas.
So I'm going to type IPV six.
OSPF.
Process ideas one specify an area.
In this case, I'll specify area one.
On the serial interface.
I'll put that into Area Zero.
We need to do the same thing on router two.
So IPV six router OSPF.
Let's just make this process to.
Give it a rata.
I'd.
The quadruple to go onto the first Ethernet interface.
IPV six.
OSPF too.
In other words, our process ID.
And let's put this into area to go on to the serial interface and let's put that into area zero.
So hopefully we should form a neighbor relationship.
And as you can see there, it's taken place.
The relationship has gone to full.
So hopefully we should get roots from router one.
So show IPV six root.
Notice here we have received an OSPF into area route from router one telling us about this network.
Notice there's no one at the end here because that is a network address, not a host address.
So on router one, let's create a loopback interface.
So give it an IPV six address of let's say 2002 colon.
Colon one slash 64.
Put that into OSPF area.
One.
And then back on route to it's only look at OSPF routes.
And here you go.
We've now learned about the loopback on router one through OSPF and it's displayed in the routing table
of router two.
I could ping 2000 to colon colon one or the colon colon one.
And as you can see there, the ping is successful.
It's as simple as that to set up OSPF version three.
In other words, OSPF for IP version six.
Now it's important to realize that we are only running IP version six on these routers.
For example, if I type show IP route, you'll notice there are no routes on router one and a router
to the routing table displays in the same way that they are no routes.
There are no IP version four addresses configured on these routers, so nothing gets displayed in the
routing table.
It is possible to run both protocols at the same time.
So on router two on the serial interface, let's configure an IP address of 10.1 2.2.
And now if our top show IP rot.
Notice that rot appears in the routing table on router one.
There are still no routes because no IP version for addresses have been configured, but on the serial
zero interface I could do something like IP address ten one two, one.
With a mosque.
And now the writing table will display that rot.
So I could ping ten.
One, two, two.
Which is the IP address of router two.
Or I could ping 2001.
Colin one.
Colin two.
Colin Colon two.
Which is the IP version six address of router RT.
I could also, for instance, try and tell it to the router.
And as you can see, it says password required, but none set.
And I could do the same.
In IP version six.
So on router two, let's create a VI password.
So password cisco create an enable password of Cisco and now let's try and telnet from router one to
write it to using IP version six.
And as you can see here, we are able to telnet successfully and doing it in IP version four.
Notice we are able to telnet successfully.
In other words, both protocols can be run at the same time, running side by side.
This is known once again as running a dual stack.
Both the IP version for Stack and the IP version six stack are running side by side.
You can also clear the SBF process in a similar fashion to IP version four.
You just literally type clear.
IPV six.
OSPF process.
And that clears the OSPF processes.
You can see the neighbor relationship was torn down and then re-established.
So a lot of the concepts of very similar between IP version four and IP version six.
Another example of a command that's very similar in IP version six as in IP version four is you can
do the command IPV six hostname and now specify a host name, let's say or two, and then I can specify
its address.
So now if I ping or to do that again, notice that ping succeeds.
Let's look at some of the IP version for two IP version six transition mechanisms.
There is fortunately transition richness.
In other words, there is no fixed date to convert.
This is not like Y2K, where the whole world was supposedly going to fall apart at the end of 1999.
There's no need for all of us to convert at once.
However, this is becoming very important, as I mentioned earlier.
As I'm recording this a week ago, the available IP version for address space was exhausted.
So it's becoming critical now for businesses to look at ways to transition to IP version six.
There are multiple transmission mechanisms available.
The first one is what's called running a dual stack, where you run both IP version four and IP version
six at the same time on a single host.
So this MacBook, for example, has an IP version four address as well as an IP version six address.
When the MacBook is communicating to the server, it can use IP version four, but when communicating
to this server, it can use IP version six.
So this is the typical analogy where a person can speak two languages and as an analogy would speak
English to one server and French to another server, but in this case IPV four to the server that only
runs IPV four and IPV six to the server that only runs IP version six.
A lot of operating systems support this.
Here's an example.
In Windows, I can pick 172.
I can pick 120 7001.
The loopback in IP version four.
And once again, I can ping the loopback in IP version six.
This Windows machine supports both protocols, and in this case, based on the address, a specific
protocol is chosen.
So in this example, we're looking at an IP version for protocol stack.
In this example, the application being used only supports IP version four.
So when data is sent from the application layer down to the physical layer, the application will choose
whether it's using TCP or UDP at layer four.
It will then use the IP version for protocol stack at layer three.
At Layer two, the Ethernet type would be set to zero x 800.
If this is an Ethernet to frame, that would then be forwarded across the physical medium.
In this case, Ethernet, if an application supports both IP version four and IP version six, the application
may choose either TCP or UDP, depending on how it's been programmed.
And then the protocol stack at layer three would be chosen.
Are we using IP version four or are we using IP version six?
So the choice of protocol stack would be determined by, for instance, the destination IP address that
we're going to or by using a DNS server that determines which protocol stack is used.
The application programming interface or API of the application needs to be able to handle IP version
six formatted addresses.
So as I've shown you previously in HTTP, the IP version six address would have to be put in brackets.
So the application would need to be able to handle those address formats.
For example, the Ethernet type would then be chosen once again, if it's version four of IP, the Ethernet
type would be set to zero x 800.
But if it's IP version six, the Ethernet type would be set to 0x86 DX.
That would then be forwarded across the physical medium.
So when data is sent from an application, let's say Internet Explorer, depending on various parameters,
for example, the URL that you specify in the browser, the data would be sent across the IP version
six stack or across the IP version four stack down to the physical medium.
Another transmission mechanism is to use tunnelling.
In this example, we have a host on the left hand side that is running IP version six.
On the right hand side, the server is running IP version six, but the routers are connected by an
IP version for only network.
So IP version six addresses will not be routed by this infrastructure.
So what you can do is you can set up a tunnel between router one and router two to tunnel IP version
six over IP version.
For there are multiple ways to do this.
You can either use manual tunneling or dynamic 64 tunneling or intra site automatic tunnel addressing
protocol.
Or lastly, you can use Teredo tunneling.
Now let's look at each of those in more depth.
So he has an example of tunneling IP version six packets over an IP version for infrastructure, the
MacBook on the left hand side since IP version six data inside of an IP version six header to its default
gateway, which is, let's say, router one router one will then take the IP version six information
and encapsulated inside IP version four.
A tunnel is set up from the local IP version for address of router one to the remote IP address on router
two.
So please note this is an extra IP header.
In other words, an IP version for header is dependent to the front of the IP version six header encapsulates
the IP version six information.
So routers in the IP version for infrastructure, never see the IP version six header.
They're only see the IP version four header.
Now I've shown more detail of the IP version four header.
I've shown you the source and destination addresses, but this is part of the same header.
When the packet gets to router two, the IP version four headers are stripped off and the packet is
sent on the remote LAN as a pure IP version six packet.
Now when setting up tunneling, it's important to remember that the protocol type is 41.
So the IP version six packet is encapsulated within IP version four.
And when IP version four encapsulates that IP version six packet, a protocol type of 41 is specified
in the IP version four header.
TCP, for example, has a protocol type of six and UDP protocol type of 17.
And in this case, IP version six is set to protocol type 41.
The head is 20 bytes in size when there are no options.
This can cause some problems.
The maximum transmission unit between our two hosts, the MacBook and the server is reduced by 20 bytes
because of this additional header can be difficult to troubleshoot issues with tunneling.
As an example, the routers in this cloud could be blocking Protocol 41 and would need to be changed
to allow that traffic through.
In manual tunneling, you are manually establishing the tunnel between router one and router two and
I'm going to demonstrate how to do that a little bit later.
With dynamic 6 to 4 tunneling, the tunnel is automatically established between the IPV six networks
through the IP version for network pre setting of source and destination IP version four addresses is
not required for these automatic tunnels.
Automatic prefix assignment is where one aggregate global unicast IPV six prefix is assigned to each
6 to 4 site.
And these are based on the specific address 2002 colon.
Colon slash 16 assigned by the honor.