Original subtitles

>> It's new, it's shiny, it's IPv6 Configuration, [laughs] and it's fantastic.

I was just going through it, before I start this record I was like "Yeah, better, you know,

brush up a little bit and do, you know, run through some of the commands I'm doing.

And as I'm doing it I'm like, "Oh, oh I should try--

ooh, this would be cool, ooh, I should let's add this."

So, this is going to be fun.

We're going to look at the IPv6 Configuration.

First off, assigning the addresses to you router, you know, just kind of the base,

how do you get started with IPv6 on your router?

We'll look at Routing IPv6, both static routing,

and I want to roll out full IP or OSPF version 3.

And then we'll look at finally how do we cut over from IPv4 to IPv6?

To illustrate IPv6, I decided to go with this simple typology just a--

I mean when you see how this is configured you're going to immediately be like, "Okay,

I can see how this goes to any size organization.

So, I've got a couple of routers, nothing on them at all except the host name.

So, let's get started.

I'm going to bring up the GNS3 console, let's bring up the console for router one

and while we're here might as well grab router two.

Now, just so you get oriented I'm going to do on each one of this--

I just have literally a base config that has a host name, no IP addresses,

everything shut down, I mean these things are out of the box

or out of the emulator, however you want to say it.

So, there's nothing happening here.

First thing I want to do is start assigning the addresses, how do I do that?

Well, unlike IPv4, IPv6 routing is turned off by default, you may have seen--

I don't know if you've seen this at any point in your Cisco journey,

but if I go to the global config mode and type in IP routing

and hit enter, that turns on routing functions.

Essentially your router is not a router until you type that command in.

Now, since the early days Cisco has been shipping routers with that command

in the running config by default, so you don't have to do that, however,

they do not enable IPv6 by default.

So, first off I'll say you need to make sure that your IOS version supports IPv6

and you'll find out real quick if it doesn't because you'll go to type this command,

it's ipv6 unicast-routing, hit the Enter key.

That command turns on the IPv6 features, essentially it's not an IPv6 routers--

router until you type that command in and now it is and that command is not in there by default.

So, now let's go in and assign some addresses, I'm going to look back at my typology here,

router one you can see my main networks.

Now, let me-- before I just type those in let me talk about them,

notice that we have one network here, 2001:55::1, what does that mean?

Well, you remember from the concepts nugget that this represents a whole bunch of zero,

0:0:0 and then you'll see that commonly.

Now, remember each one these represents 16 bits of information, I'm going to change to purple,

just bright is better, so each one of these represents 16 bits of information.

And then-- so you see right here there's up to 32 bits, now the subnet mask is 64 bits.

So, immediately I'm going, "Okay, well, I know in every single IP address whether it's IPv4

or 6, there's always two portions, there's the network and there's the host.

So, when I'm trying to identify the network for this I'll go, "Okay, well I've got 32 bits

and then a whole bunch of zeroes that are kind of vanished behind those double colons.

So my network must be-- if I were to write it, you know, without any shortcuts,

it would look like this, 2001:0055:0000:0000, that would be my networks.

Now, of course with our shortcuts, we've got 2001:55:0:0, right?

That's a shorter way of writing the network statement 'cause I can drop the leading zeroes

out of there, and that represents the first 64 bits.

Now, the last 64 bits, notice I do ::1.

So, if I were to say, "Well, what is the host?"

The host, you know, I'll just write the short version is 0:0:0:1.

So, I mean, you know, how every-- before use IPv4 we have like 192 168.0.1 that's going

to the gateway or something like that.

Well, it's the same thing here except we've got a really big network 2001::55:00, you know,

all of that that's-- that identifies the network and a really big host but it all boils

down to the same concepts, this is a shorthand of writing,

I have the first IP address in that network.

Okay, so down here router two just to describe this, we've got the same thing, 2001:56::1,

so same concepts we've got four octets since it's a slash 64,

represents the network 2001:56:0:0 that represents the network

and then 00010:0:0:1 represents the host, got that?

Now, looking at this we were a little more descriptive, we said, "Okay,

the serial link is going to have a network of 2001:210:10:1.

Now, again, four octets right there, that's 64 bits have left [phonetic].

So that is our network.

Now, the host is still the ::1, so our host is 0:0:0, you can use that, it's going to be long,

it's bigger addressing if we write it all out that way, but using the shortcuts,

you see how the shortcuts are so handy because there's typically going to be a number of zeroes

in the IP address, at least for your router, and that's one that we care about.

So, you can see that this is on the same network as this, one of them is the first address

and one of them is the second address.

Is that all making sense?

Good, okay, so let's come down here to router one.

And, I'm go into FastEthernet0/0.

So, router one's got FA00 on the left there and 000 on the right.

So, let's power that guy up, I'll do a no shutdown,

get him going 'cause I know he's administratively down, and we'll do now IP--

instead of IP address, right, we're now going to do IPv6 address, and you'll see this so often,

Cisco did such a great job just saying, "You know what,

concepts for the most part are the same in IPv6, we still have, you know, show IP routes

but it's just now it's going to be show IPv6, so it's not like you have

to relearn all the commands that you know.

We're still assigning address but instead of IP address it's IPv6 address, pretty nice,

let me hit the question mark, check this out, a couple of things

that you could do is a link local address, come on, I know it's rusty already,

think back to the concepts, link local is you can actually pick what address that uses

to communicate on its local subnet.

Remember that was the FE80 [phonetic] address that's it's going to generate by itself.

Now, that being said, I'm saying it because it's going to generate it

by itself, we don't have to type it in.

Although being on a router you might just say, "You know what,

I like manually typing it," so you could do that.

Down here, notice this one does not have a subnet mask because it doesn't need one,

link local never talks outside of its own network, it's own little FE80 world,

doesn't pass another router, so there really is no network to it.

However, this one-- that's how you assign a real address and it says, "Okay, well, you know,

this is-- that's what we're going to do, and underneath we can see autoconfiguration.

This is where it can query another router and say, "Hey, what network am I on?"

and it will kind of fill in its own host Id based on its MAC address, so if you want to do

that you can but, come on, but we don't like auto things, we want to do it ourselves.

So I'm going to type in ipv6 address 2001:55::1/64, totally we'll take that,

just like that, look that, 2001:55:1, so it's going to do ti.

Now-- you know, I can't go on, I've got to verify it, I must show IP--

Caps Lock, show ipv6 interface brief.

Yes, they took my favorite command and moved it over, it looks different though.

They knew they couldn't fit this big, old addresses on one line,

so look a this we've got FastEthernet0/0, it is up and up, remember line protocol

and line protocol, line-- why is my mind-- oh, status in line protocol, is that right?

Show ip-- having one of those moments.

Yes, status and protocol, there we go, so the same thing here,

status, first up protocol, second up.

So right there, you see the link local address, now that's pretty cool 'cause look at this,

you can see-- okay, we got some MAC address info but right in the middle, remember that FF:FE,

it kind of squishes it in there to give it enough octets to be a 64

but I just show it's right there we're verifying that, okay, looks good.

And then right here we've got the--

got the address we just assigned so I'm able to verify that, good.

So let's get back in the serial 0/0 no shut down and we'll do ipv6 address, 2001:210:10:1::,

I keep entering the Caps Lock [phonetic], ::1/64.

Come on, I want to verify that.

So, we can see it's got its own little link local address.

Now, check it out, same link local address as above, you see the FE80::

and then-- is that-- whoa, can we do that?

Can we do that?

Yes, we can do that because that address never leaves its local subnets.

So, when it's talking on the serial link, you know, it's not like it's going to get confused

and say, "Oh, well, you know, which link is just coming in on.

You can use the same link local address for all your interfaces if you want

to 'cause it only communicates on that interface, it never goes beyond that world,

but right below, we see that's good.

So, okay enough descriptions, let's just blaze through router two, right?

And so be our good review router, let's see if I can move it up here to see all the addresses.

Please find a spot, let's do this, there we go.

So let's go into global config, ipv6 unicast routing,

we we turn it on interface FastEthernet 0/0, no shut down IPv6 address looking

over there 2001:56::1, you follow?

Good so far?

Exit, backout, interface 00/-- 0/0,

we'll do ipv6 address 2001:210:10:1::2/64, no shutdown, there we go.

So, go back and do a show ipv6 interface brief and let's-- I mean, so it looks good,

I'm feeling warm and fuzzy about those two, show ipv6 interface serial 0/0.

We can see a little bit more about it, notice it says, "Okay,

I've got my global unicast, address.

Remember we talked about the different address types?

Global Unicast Address, is the one-- it's the global address that it's using this,

it's like a public address we can use out on the internet.

Right above it you see the link local address, this is the automatically generated address.

And, it also says, I've joined this multicast groups.

So multicast groups are kind of like I've tuned in to these radio stations,

I'm listening on my local network for these kinds of--

I think of it as, I mean I'm going to say broadcast

but they just call them unicast nowadays.

So, I'm feeling the need for a ping right about now, yeah?

Let's do a ping, let's say I'm just-- do a show cdp neighbor, sure enough there it is,

show cdp neighbor's detail, check it out, cdp been upgraded,

my friends, to support the IPv6 addresses.

So, it says, "Okay, I've got router one.lab.local which is its host name.

It sees router one at that address.

So, okay, how do I do this?

I can't type in ping because ping is an IPv4 flavor, I have to type in ping ipv6 followed

by the address and that's, you know, I'm on router two, router two so I'm going

to the other side, 2001:210:10:1::1, awesome, okay, so working, yeah, feel good?

Okay, so I know someday I'm going to be typing this and I'm going to be

like these addresses are so long [inaudible] and there's going to be some young kid

who comes home, he's like, "What do you mean?

That's just the way the world works, what are you talking like old IPv4, you know, grab the--

I can totally-- somebody's going to mock me someday on how painful these addresses are

to type in but for now they're painful.

It's-- I like IPv4 typing those is better.

So, router one shows cdp neighbors using router two, let's just go the other direction

to feel good, 2001:210-- oh, I forgot this, ipv6 210:10:1::2.

So, we're doing good, we're getting an end to end communication, but wait, wait there's more,

how do I-- let's-- how do-- let's see if I can ping over here, this 2001:56::1, right?

Up here we've got 2001:55::1.

So, I'm on router one, let's do it, let's do a ping ipv6, 2001:56::1,

what do you think it work-- will work?

Well, no? No it will not, why?

Because it doesn't know how to get there even though it's like, "Hey,

I've only got one router, the router doesn't think that way,

so looking at its routing table, so let's do that.

Let's do a show ipv6 route, and the router is like, "Hey, I know about this stuff,"

and it says, "Okay, I'm connected to this network,

as a matter of fact I've got a local address, a little different

than the ipv4 routing table, right?

I've got a local address of this, see that's the address,

this is the full network I'm connected to, it's my FastEthernet 0/0, no metric,

no administrative distance 'cause it's right there.

I'm plugged into it."

So, the routing table is not able to see-- router one's not able to--

let's squish him up here, [inaudible] it will see router two's network go there.

I don't see that they're on the table.

So, let's do a little a static routing, you say?

I'm gong to do a IPv6 route, you know, instead of an IP route, it's IPv 6, are you--

tell me you're not feeling good, you know, if you're feeling good with IPv4 concepts,

this should be like, "Oh, oh that's cool."

So, it's just the same command with v6 after it, so it's IPv6 route, where do you want to go?

I want to reach 2001:56, actually, :: done, huh, can I do that?

Yeah, because I want to reach that whole network--

look at me I'm waving my finger at the screen, I want to reach this full network right here,

I don't just want to reach the .1 address, right?

And this is the way that we annotate the whole network, we're saying that's the network

and the first 64 bits represents the network

so the router automatically feels it, "Okay, :0:0 there, got it?"

Okay, so now, tell me, admin.

[phonetic], where do I go to get to that network?

And I'm going to say, "Well, actually you can go shrink your window a little bit

and you can go right here to router two.

So, I'm sitting on router one, I need to go right here to get right here,

that's the next half address, so let's do that.

Now, you can put an interface if you want to, I just don't like it.

So, we'll do 2001:210:10:1::2, right?

So, I'm saying, I want a route to this network and I'm going

to use this guy to get me there, good?

Okay, we can also come in here and say, "Oh,

well here is the different administrative distance."

That's actually to create something they call the floating static route,

you'll learn about that when you get to the CCNP world.

You can also say this is just the multicast router, just the unicast router,

we're not going to worry about all that [inaudible].

So now, show ipv6 route, let's take a look, static it looks good,

I'm feeling good about that, so let's do it.

I'm going to go on router one and ping ipv6 2001:56::1.

Yes, I need like a-- I need a like a clapping sound effect or a Bon Jovi, like,

it worked, it's awesome, so we're good.

So, good, now okay-- hang on, where I we on this thing?

I've assigned the addresses, I've verified those addresses,

I see that through there, I've configured static routing.

Now, let's look at dynamic writing.

It's different but I think you'll like it a lot better than the old ipv4 way.

Okay, so I've got the static route in here.

So, let's get rid of that, right?

No, it's gone.

So now my pings will fail again to that address

because it's saying I don't know how to get there anymore.

You've take them right away.

So, I'm going to go to router two, let's set up OSPF, how do we do it?

Okay, going to global config mode, and we're going to use ipv6, remember we would type

in router and then what routing protocol [inaudible], that's IPv4, okay?

Put that in the back of your mind.

So, how do we do it now?

Ipv6 router, go Cisco.

Now, this version of the IOS only supports RIPv6, and actually most people call it RIPng,

next generation, I can't believe RIP made the jump.

And OSPF, but there are flavors of every protocol for ipv6, there is EIGRP for IPv6,

there's BGPISIS, I mean they've all kind of gone through the evolution

and become IPv6 compatible, it's just my IOS version that doesn't do them.

So, I'm going to type in ipv6 router OSPF, and just like the ipv4 I have to type

in a process ID just like-- remember I said it's like task manager that goes through

and we've got the, you know, the process, the PID that--

it's just the number, just got to remember it, that's all there is to it.

So I'm going to type in process ID one, now, unlike the IPv4 version

of OSPF there's nothing really that goes under here, [laughs] that's what's cool.

Remember before this is where we would come in and do network, you know, blah, blah, blah,

wildcard mask 0, you know, 0.0, obviously I'm just throwing some up there.

But check this out, network question mark [phonetic], huh, I don't know what you're trying

to say, the network command is gone, thank you Cisco for getting rid

of it 'cause now they have a better way.

The only thing that we see-- I know some of you are like, "Whoa, what was that?"

OSPF could not pick a router ID, what's that?

Well, in OSPF as soon as you start the process in IPv4it will pick what's called a Router ID.

The Router ID is something that looks like this.

Well, not exactly that but it will be an IP address.

But if you read the documentation you'll say, "No, no, no, it's not an IP address,

it's just the number that looks like an IP address that the router uses kind of like

as its name when it's talking to OSPF router.

So, for instance, if router one said, "I want to have the router ID 192.168.0.1,

then it would just introduce itself, it would say, "Hey, router two, how's it going man?

I want to trade some routes with you.

My name is 192 168 0.1," and router would go, "Oh, great.

Hey, my name is," and whatever you type in.

You can type in whatever you want, you could make--

you could make up and you can say router two has a router ID of 255 255 255 1, if you want.

So, it doesn't matter and that's why they say it's not an IP address,

it's just as an identifier.

Now, here's-- the way it works in the version 4 or I should say v3,

the older version of OSPF is rather looks at all of its interfaces and it says, "Okay,

which one has the highest IP address?

That will become my router ID, it's just kind of picks one, that's what it does.

But, here's the problem, OSPF looked around and it's like, I can't pick one, why?

Why do you think that is?

'Cause it doesn't have any IPv4 addresses, even though we're doing all these ipv6 config,

I can do a show ip interface brief and it's still like, I've got nothing, nothing--

oh, nothing, nothing, nothing, nothing's there.

I don't have any IPv4 addresses.

So now if you have a truly native router, native not like wild [inaudible] with a spear

like native only IPv6 then it's going to need you type in what the router ID is.

So I'll juts say, "Hey, this is router ID 2.2.2.2, and that's it.

That's it, seriously, do a show run, I'm going to filter it down, I'm just going to say,

show me the section that has router OSPF, well, actually it's--

well, I guess I can type this also find it router ospf comes back it's

like this is all I got.

I got router ospf 1 ipv6 and I got router-id.

So now it's like, well, how does it know which networks to run on?

Remember the old network command we would identify which networks

and then we could send hellos out to those interfaces

and all that, we don't do that anymore.

Now, in the IPv6 version of OSPF I can go in and do interface FastEthernet0/0

and put the interface into the OSPF process.

I think this is a lot easier.

I don't have to explain the wildcard mask and how the network command work.

Now, all I have to do is go in here and do ipv6 ospf, and then I say, well,

I'm going to associate this with process ID 1 and I'm going to put this in area 0.

Now, you remember the area was just in this course.

We're only going to talk about area 0 but the area can designate where you have summary routes

and all that kind of stuff but that's it, no network command, no wildcard mask and matching,

and oh, does this interface gets swooped in there?

Nothing like that.

Now, I just go interface by interface and say, "Okay,

interface FastEthernet0/0, you're running OSPF, done.

Interface serial 0/0, up here-- well, here I'll type it in, ipv6 ospf 1 area 0.

You're running OSPF done, right?

So now, it's the same-- same function as the network command but a lot easier to understand.

Now, I am sending hello messages, hello, hello, hello out of this interface, hello, hello,

I'm going out in this interface too, and I'm advertising these networks.

I'm saying, I'm going to tell people about the 2001:55 network.

I'm going to tell people about this network.

Now, this guy down here, once he's configured for OSPF is going to get those advertisements

and so we're like, oh we already knew about this one 'cause I'm plugged into it

but I did not know about this one behind you so let's do it.

Oh, wait a sec, I'm drawing this all up like I'm on router one but I'm really--

I configured router two for so-- same concept, just flip the arrows, right?

So, I was working on router two, so hello, hello, hello.

So we got to go to router [inaudible].

So, I didn't-- I'll say if I would have had the network commands I would've messed it

up then 'cause I would have typed in router one's network.

But since I did it on the interface, it's the same thing.

Now, let's go back here.

I'm going to do a show ipv6 protocols, just like in the old world we had show ip protocols

which was the version 4 it's just saying, "Hey,

I'm running OSPF on serial 00 and FastEthernet0/0.

Okay, let's go to router one.

Router one, where are you?

There we go, okay.

So, I'm going to go, well, I'm in router one let's do a show ipv6 protocols, I got nothing,

connected and static where we've got no OSPF relationships at all.

So, let's go into a global config ipv6 router ospf, process ID 1, it's fine.

Remember that does not have to match between the two sides.

Now, I'm going to go in here and give it a router ID.

Now, this isn't an optional thing, if the router doesn't have a name,

if it doesn't have a router id, OSPF won't start.

You can't say hello, unless he has a name to introduce itself by.

So now I'm going to go into interface FastEthernet--

let's go there first, FastEthernet0/0 ipv6 ospf and we will say this guy--

and by the way I'm just going in and saying you belong-- essentially, let me just say that,

now what we do feel-- this is how the process works, it's on the router,

I create the router OSPF process.

I said, okay I'm not running OSPF, we do that in global config mode

when we type in ipv6 router ospf 1, right?

So, it's like we activate this process of Router OSPF and I say, "Okay,

I'm now going to add FastEthernet0/0 to that process.

So now it's doing OSPF, sending hello messages, advertising itself, its network.

, I'm going to add serial 0/0 to that-- so it's like--

I think of it like if this were a wizard we'd be dragging and dropping interfaces

into the OSPF process bucket and leaving them there.

So, instead of previously we would go under OSPF and configure it with this little goggles

to say, "Hey, this network command now go out and find all of the interfaces that start

with 200., you know, remember the old IPv4-- the old, the current IPv4 flavor of OSPF?

So now we're-- it's like we're putting the interfaces into the bucket instead.

So, I'm going through the-- oh and what I'm saying all these other stuff is like if I want

to change my hello timer, how often I say hello, my dead-interval,

how long until I declare a neighbor dead, the cause of the--

I mean, I can twit this thing all out but to make it work,

I'm just going to say this interface, FastEthernet0/0, is under the process ID 1,

and it is all part of area 0, one big old area.

So, exit back out here and we'll go under interface serial 0/0 ipv6 ospf 1 area 0, right?

I've now dragged those two interfaces into the buck-- oh, look at that, we've got a message,

it says OSPFv3 process one has changed, I see neighbor 2.2.22 and somebody came to me

and said, "My name is 2222 on serial 0/0, I've moved from loading

to full, that means I'm a full neighbor.

Let's do a show ipv6 ospf neighbor and I can see, you know,

the same output is the show ip ospf neighbor as before.

I see now have a full neighbor relationships, let's check our routing table, show ipv6 route

and look, OSPF has now educated my router one about this 56 row, come on we got to ping it.

Ping ipv6 2001:56:-- oh, Caps Lock, ::1, judging we're over and now I can go up to router two

as well and do the show ipv6 route, you know, okay we got to ping it.

You can't just leave something unpung.

What 's the past tense of ping, pung?

2001:55::1.

I've pung it.

[laughs] So, it is now communicating fully between the two-- tell me that's not awesome.

I mean, think about this.

I mean, in one nugget we've now taken all these base concepts, I mean, yeah,

it took us a long time in IPv4 to understand it all, to learn it all but can you--

are you starting to feel like this jump to IPv6 may not be

as monumental as most of them I think?

I mean, yeah, it takes a little while to get used to those new addresses, those big,

old hairy [phonetic] addresses and then the new way the subnet mask looks but for the most part,

I mean, [laughs] we did almost what took us probably have the series

to in IPv4 in one nugget with IPv6.

What that tells me is IPv6 it's brings new concepts, bring some new feature

but the core of networking is still the same.

It's still the same car, right?

We just switch out the engine, we still have seats,

we still have a wheel it all does the same stuff maybe a little faster, maybe a little better.

But IPv6 shouldn't rock our world like I think most people think it will.

It's a big transition, yes, there's a lot of work involved,

yes, but conceptually not too bad.

So, how do we make that jump?

How do we get a smooth non-pressured transition to IPv6?

The-- I would say now Cisco approved and recommended a way

to make a transition is this guy, Dual-stack Routers.

So, here is the idea, I can run-- I mean you can see right here on router one,

let's do a show ipv6 interface brief.

It shows these IPv6 addresses that are on there, right?

So we're running ipv6, show ip interface brief, right?

All completely unassigned, you want to see this method?

Here it is in 30 seconds or less.

We have just created a dual-stack router.

Essentially we've got now if we're to diagram this we've got the router,

we'll say a router one that has an interface

that has let's just say a couple of clients on there.

The interface has two different IP addresses, an IPv6 address and an IPv4 address.

So, the beauty is, now we can have our clients still running--

let's say that guy is running Windows 7, you know, he's got an IPv4 address assigned to that,

we haven't made the transition yet, he's 192.168.-- what did I say?

0.50-- negative [inaudible] one or 0?

Yeah, so 0.50.

He's pointing to the default gateway of 0.1, life is good for them,

he never notices that there's problem or anything is changing, we've got the IPv6 address

so this guy is running-- I'll just say, Windows 8 or beyond and it's got an IPv6 address

and it's default gateway points to this right here.

This router, it's like a bilingual router, that's all there is to it

where he speaks IPv4 English and then IPv6 Spanish, you know,

so he can speak the two languages at the same time on the same interface.

This is probably the least changing of your network, like you can do it

because you can have, you know, a WAN like now with with an IPv6 address over here,

IPv4 address over here, maybe this goes to the internet; right?

And your service provider can do the dual-stack thing and you can do-- you can net these guys--

oh, did I put, let's say, you could net [phonetic] these guys out to a public v4 address

and you could-- well, you don't even have it,

right 'cause there's bazillion of addresses out there.

So you can just natively pass those guys through and route them

or you could even use net for IPv6, it's out there.

So, you could net them to an IPv6 public address if you wanted to do that too.

So you can see you could make this change, you could just--

you could say, you know what organization we're going to run IPv6 right now.

I have just turned on IPv6 on a router interface and now you just got to slowly move the clients

over to IPv6 as you will, that is Cisco's best, you know, thumbs up method if you look

at all there white papers of how can we transition, that's the least impactful.

But we have otherwise, we can do tunneling, and what that means is, you know,

let's say the world around us we we're slow and the internet became IPv6

and the whole IPv4 internet is shutdown, right?

We can actually still run IPv4 on our networks, think of this like a VPN right, IPv4 over here

and I can actually tunnel that through the IPv6 internet to where I can run IPv4 on both sides

and still communicate through this tunnel like a VPN.

More likely is the early adapters, you probably won't see much of that,

you'll see people that are like, "Oh men, we're ready, we're going to IPv6

but the internet connection has not caught up yet so it's still IPv4, same concept.

You can create-- that's why I say 6 to 4 or 4 to 6.

I can do a 6 to 4 tunnel to where I'm tunneling IPv6 through an IPv4 internet or it doesn't have

to be the internet, it could be a WAN link, it could be a service router, it could be anything

that just has not converted as of yet, so you can slowly bring up your networks one-by-one

to IPv6 and tunnel them to each other, pretty cool.

The last one is NAT, they modified NAT to where it does protocol translation NAT-PT

to where I can have, let's just say we've got the IPv4 internet as it stands today

and I've decided to be that early adapter and I'm running IPv6 on my internal network,

NAT-PT allows me-- or IPT [phonetic], NAT-PT allows me to take those v6 addresses

and NAT them out to a v4 address.

Let's just say 200.1.1.1 so it hides the entire IPv6 network behind the scenes and just comes

out as a version 4 public address.

So, I know I've said this a couple of times, moving the IPv6 is not going

to be a Y2K experience, it's not going to be one day you wake up and you're like, "Oh man,

November 3rd, I've got to convert," you know, or something, you know,

you've got to run to that date and be that,

IPv4 will be around for a long time, I-- can I say how long?

I don't know, I would-- 20 years, and let me throw another wild prediction

that by the time I get there I totally forget it and nobody will call me on it anyway.

Twenty years IPv4 is gone, right?

IPv6 has taken over as its entire-- does that mean you cannot run IPv4?

No, it does not, you can use those migration strategies for a long time to come.

So, we've seen-- you've got to feel a little better

about IPv6 after seeing this nugget, right?

We've seen how we can go in assign IPv6 addresses to your router,

verify those addresses, turn on routing, both static routing and OSPF, same command,

same concept as before, same cars just a different engine, we put IPv6 in front

of all the commands and now we can start routing the IPv6 addresses

and then finally we saw how we can migrate over, how we can cut over from IPv4 to v6.

Now, I hope this has been informative for you and I would like to thank you for viewing.