Are you sure you want to cancel your subscription?

If you cancel, your subscription will remain active through the paid term. You will be able to reactivate the subscription until that date.

Sorry to see you go

Your subscription will remain active until . If you change your mind, you may rectivate your subscription anytime before that date.

Are you sure you want to reactivate?
Welcome Back!

Your subscription has been reactivated and you will continue to be charged on .

Reactivate Subscription

Thank you for choosing to reactivate your subscription. In order to lock in your previous subscription rate, you owe: .

Your Subscription term is from - .

Questions? Call Sales.

Payment Due:

Auto-Renew Subscription

To auto-renew your subscription you need to select or enter your payment method in "Your Account" under Manage Payments.

Click continue to set up your payments.

CBT Nuggets License Agreement

Unless otherwise stated all references to “training videos” or to “videos” includes both individual videos within a series, entire series, series packages, and streaming subscription access to CBT Nuggets content. All references to CBT or CBT Nuggets shall mean CBT Nuggets LLC, a Delaware limited liability company located at 44 Country Club Road, Ste. 150, Eugene, Oregon.

A CBT Nuggets license is defined as a single user license. Accounts may purchase multiple users, and each user is assigned a single license.

  • GRANT OF LICENSE. CBT Nuggets grants you a non-transferable, non-exclusive license to use the training videos contained in this package or streaming subscription access to CBT content (the “Products”), solely for internal use by your business or for your own personal use. You may not copy, reproduce, reverse engineer, translate, port, modify or make derivative works of the Products without the express consent of CBT. You may not rent, disclose, publish, sell, assign, lease, sublicense, market, or transfer the Products or use them in any manner not expressly authorized by this Agreement without the express consent of CBT. You shall not derive or attempt to derive the source code, source files or structure of all or any portion of the Products by reverse engineering, disassembly, decompilation or any other means. You do not receive any, and CBT Nuggets retains all, ownership rights in the Products. The Products are copyrighted and may not be copied, distributed or reproduced in any form, in whole or in part even if modified or merged with other Products. You shall not alter or remove any copyright notice or proprietary legend contained in or on the Products.
  • TERMINATION OF LICENSE. Once any applicable subscription period has concluded, the license granted by this Agreement shall immediately terminate and you shall have no further right to access, review or use in any manner any CBT Nuggets content. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you are in violation of this Agreement. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you have exceeded reasonable usage. In these events no refund will be made of any amounts previously paid to CBT.
  • DISCLAIMER OF WARRANTY AND LIABILITY. The products are provided to you on an “as is” and “with all faults” basis. You assume the entire risk of loss in using the products. The products are complex and may contain some nonconformities, defects or errors. CBT Nuggets does not warrant that the products will meet your needs, “expectations or intended use,” that operations of the products will be error-free or uninterrupted, or that all nonconformities can or will be corrected. CBT Nuggets makes and user receives no warranty, whether express or implied, and all warranties of merchantability, title, and fitness for any particular purpose are expressly excluded. In no event shall CBT Nuggets be liable to you or any third party for any damages, claim or loss incurred (including, without limitation, compensatory, incidental, indirect, special, consequential or exemplary damages, lost profits, lost sales or business, expenditures, investments, or commitments in connection with any business, loss of any goodwill, or damages resulting from lost data or inability to use data) irrespective of whether CBT Nuggets has been informed of, knew of, or should have known of the likelihood of such damages. This limitation applies to all causes of action in the aggregate including without limitation breach of contract, breach of warranty, negligence, strict liability, misrepresentation, and other torts. In no event shall CBT Nuggets’ liability to you or any third party exceed $100.00.
  • REMEDIES. In the event of any breach of the terms of the Agreement CBT reserves the right to seek and recover damages for such breach, including but not limited to damages for copyright infringement and for unauthorized use of CBT content. CBT also reserves the right to seek and obtain injunctive relief in addition to all other remedies at law or in equity.
  • MISCELLANEOUS. This is the exclusive Agreement between CBT Nuggets and you regarding its subject matter. You may not assign any part of this Agreement without CBT Nuggets’ prior written consent. This Agreement shall be governed by the laws of the State of Oregon and venue of any legal proceeding shall be in Lane County, Oregon. In any proceeding to enforce or interpret this Agreement, the prevailing party shall be entitled to recover from the losing party reasonable attorney fees, costs and expenses incurred by the prevailing party before and at any trial, arbitration, bankruptcy or other proceeding and in any appeal or review. You shall pay any sales tax, use tax, excise, duty or any other form of tax relating to the Products or transactions. If any provision of this Agreement is declared invalid or unenforceable, the remaining provisions of this Agreement shall remain in effect. Any notice to CBT under this Agreement shall be delivered by U.S. certified mail, return receipt requested, or by overnight courier to CBT Nuggets at the following address: 44 Club Rd Suite 150, Eugene, OR 97401 or such other address as CBT may designate.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the License Agreement at any time, with or without notice.

Billing Agreement

  • By entering into a Billing Agreement with CBT Nuggets, you authorize CBT Nuggets to use automatic billing and to charge your credit card on a recurring basis.
  • You agree to pay subscription charges on a monthly basis, under the following terms and conditions:
    • CBT Nuggets will periodically charge your credit card each monthly billing cycle as your subscription charges become due;
    • All payments are non-refundable and charges made to the credit card under this agreement will constitute in effect a "sales receipt" and confirmation that services were rendered and received;
    • To terminate the recurring billing process and/or arrange for an alternative method of payment, you must notify CBT Nuggets at least 24 hours prior to the end of the monthly billing cycle;
    • You will not dispute CBT Nugget’s recurring billing charges with your credit card issuer so long as the amount in question was for periods prior to the receipt and acknowledgement of a written request to cancel your account or cancel individual licenses on your account.
  • You guarantee and warrant that you are the legal cardholder for the credit card associated with the account, and that you are legally authorized to enter into this recurring billing agreement.
  • You agree to indemnify, defend and hold CBT Nuggets harmless, against any liability pursuant to this authorization.
  • You agree that CBT Nuggets is not obligated to verify or confirm the amount for the purpose of processing these types of payments. You acknowledge and agree that Recurring Payments may be variable and scheduled to occur at certain times.
  • If your payment requires a currency conversion by us, the amount of the currency conversion fee will be determined at the time of your payment. You acknowledge that the exchange rate determined at the time of each payment transaction will differ and you agree to the future execution of payments being based on fluctuating exchange rates.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the Billing Agreement at any time, with or without notice.

Cisco CCNA ICND2 640-816

IPv6: Configuring, Routing, and Interoperating

This video is only available to subscribers.
Start your 7-day free trial today.

A free trial includes:

  • Unlimited 24/7 access to our entire IT training video library.
  • Ability to train on the go with our mobile website and iOS/Android apps.
  • Note-taking, bookmarking, speed control, and closed captioning features.
Video Titles Duration
1. Review: Rebuilding the Small Office Network, Part 1
2. Review: Rebuilding the Small Office Network, Part 2
3. Review: Rebuilding the Small Office Network, Part 3
4. Switch VLANs: Understanding VLANs
5. Switch VLANs: Understanding Trunks and VTP
6. Switch VLANs: Configuring VLANs and VTP, Part 1
7. Switch VLANs: Configuring VLANs and VTP, Part 2
8. Switch STP: Understanding the Spanning-Tree Protocol
9. Switch STP: Configuring Basic STP
10. Switch STP: Enhancements to STP
11. General Switching: Troubleshooting and Security Best Practices
12. Subnetting: Understanding VLSM
13. Routing Protocols: Distance Vector vs. Link State
14. Routing Protocols: OSPF Concepts
15. Routing Protocols: OSPF Configuration and Troubleshooting
16. Routing Protocols: EIGRP Concepts and Configuration
17. Access-Lists: The Rules of the ACL
18. Access-Lists: Configuring ACLs
19. Access-Lists: Configuring ACLs, Part 2
20. NAT: Understanding the Three Styles of NAT
21. NAT: Command-line NAT Configuration
22. WAN Connections: Concepts of VPN Technology
23. WAN Connections: Implementing PPP Authentication
24. WAN Connections: Understanding Frame Relay
25. WAN Connections: Configuring Frame Relay
26. IPv6: Understanding Basic Concepts and Addressing
27. IPv6: Configuring, Routing, and Interoperating
28. Certification: Some Last Words for Test Takers
29. Advanced TCP/IP: Working with Binary
30. Advanced TCP/IP: IP Subnetting, Part 1
31. Advanced TCP/IP: IP Subnetting, Part 2
32. Advanced TCP/IP: IP Subnetting, Part 3

Review: Rebuilding the Small Office Network, Part 1

Review: Rebuilding the Small Office Network, Part 2

Review: Rebuilding the Small Office Network, Part 3

Switch VLANs: Understanding VLANs

Switch VLANs: Understanding Trunks and VTP

Switch VLANs: Configuring VLANs and VTP, Part 1

Switch VLANs: Configuring VLANs and VTP, Part 2

Switch STP: Understanding the Spanning-Tree Protocol

Switch STP: Configuring Basic STP

Switch STP: Enhancements to STP

General Switching: Troubleshooting and Security Best Practices

Subnetting: Understanding VLSM

Routing Protocols: Distance Vector vs. Link State

Routing Protocols: OSPF Concepts

Routing Protocols: OSPF Configuration and Troubleshooting

Routing Protocols: EIGRP Concepts and Configuration

Access-Lists: The Rules of the ACL

Access-Lists: Configuring ACLs

Access-Lists: Configuring ACLs, Part 2

NAT: Understanding the Three Styles of NAT

NAT: Command-line NAT Configuration

WAN Connections: Concepts of VPN Technology

WAN Connections: Implementing PPP Authentication

WAN Connections: Understanding Frame Relay

WAN Connections: Configuring Frame Relay

IPv6: Understanding Basic Concepts and Addressing

IPv6: Configuring, Routing, and Interoperating

00:00:00 - ..
00:00:04 - let's set it up on the router. We're going to start off by
00:00:08 - assigning and IP version six address to our routers enabling
00:00:12 - the protocol itself and then going in and saying this will
00:00:14 - be the IP address or IPV6 address that we will use. We will then
00:00:19 - look at how the routing protocols have evolved to support IP
00:00:22 - version six and we will go do the base configuration of
00:00:27 - RIPng.
00:00:29 - Can you believe it RIP made its way into the IP version
00:00:32 - world, it survived. It is now called the RIP next generation,
00:00:37 - but it still works the same, it 's good old RIP,
00:00:39 - and then we're going to finally wrap things up by talking about
00:00:42 - the IP version four to IP version six migration strategies.
00:00:46 - So there is going to be a certain cut on the internet where everybody
00:00:48 - has to switch over, we will look at that.
00:00:51 - I am going to use of very simple topology to demonstrate configuring
00:00:56 - IP version six addresses, just because this is the first
00:00:59 - time we're seeing it and I would like to keep the focus not so much on
00:01:01 - a large network as I am on the commands to set up by IP version six.
00:01:05 - Now before we get into the config, let's talk about what
00:01:09 - is on this diagram right here. I've got two routers,
00:01:13 - router one and router two; these happen to be the same two routers I used to demonstrate
00:01:17 - frame relay, so there is a frame relay cloud sitting in the
00:01:20 - middle of this, which I just have represented as a WAN link here.
00:01:23 - Now on the LAN of router one, you can see this is the LAN
00:01:27 - side, I have decided to use a unique local addressing scheme,
00:01:31 - that's the private addresses in IP version six, that all start
00:01:35 - with 1FE0. So 1FE0 is mandated, essentially
00:01:41 - that is what says this address is private. Just like when we
00:01:46 - put address private networks IP version four, we say
00:01:49 - it has to start with ten or 1.2.16
00:01:52 - kind of thing. Here we have to start with IFE0. Now
00:01:57 - I have VIN designated the subnet as one one one one over
00:02:01 - here. You can see that based on my sub-net mask; remember each one
00:02:05 - of these are octets is 16 bits of information. If I were
00:02:10 - saying and this represented
00:02:15 - the sub-net, I would do a /16 because each one
00:02:19 - of these represents eight bits of information. So the same thing
00:02:23 - over here, just a bigger address, this represents myself IFE0111
00:02:26 - So that means every client that
00:02:31 - is on this network would have to have an address that starts
00:02:34 - with 1FE0:1111: then it would
00:02:38 - be something else that would designate the client itself.
00:02:43 - Now let me just clear this off here, you can see that I have designated
00:02:47 - ::1 as the address; this is going
00:02:51 - to be the IP address of this interface on router one. Now on
00:02:55 - the WAN link I have used one of the global scopes 2001:210:10:1::1
00:03:01 - and the same thing over here 210:10:1::2
00:03:06 - with this 64 byte
00:03:10 - sub-net mask. Remember each one of these are
00:03:16 - but my mind just blanked out, 16 bytes, 16 bytes a piece,
00:03:20 - so add all those up and that gives us the 64 the
00:03:23 - ::1 represents the host portion, ::2 over here. So that's
00:03:28 - on addressing the WAN link. Now over on the right side same thing
00:03:31 - as the left side IFE0 private addressing, sub-net 2222
00:03:35 - so that they give you an idea of how sub-netting looks
00:03:39 - in IP version six. Now let's set it up and then start on
00:03:43 - router one and on all of the routers that we used today, we have
00:03:47 - to turn on the TCP/IP version six protocol from global
00:03:50 - config mode. Now in the old days when we, in the old days back
00:03:56 - ten years ago, when we used routers that commonly had IP
00:04:00 - access IP and so on, TCIP wasn't initially enabled
00:04:04 - on the router until you typed in IP routing.
00:04:07 - We used to have to type that command on all the routers, but now on the
00:04:11 - newer routers that command is typed in by default for us, so we
00:04:14 - don't have to type anymore. But for IP version six, we have to
00:04:17 - do the same thing we used to do for version four, IPV6 and
00:04:22 - then we type in unicast-routing, because we have multi-cast
00:04:27 - and any cast and all those different types. This is going
00:04:30 - to be doing unit cast routing, that's like a power switch on
00:04:33 - router one, I've turned it on; now I can get under my interfaces
00:04:38 - go into interface fast/0
00:04:42 - and we can see that IFE0:1111::1/32
00:04:47 - is our address, so I'll type in IP
00:04:51 - just like we're assigning an IP address, but IPV6
00:04:56 - address. See these similarities, check that, look at that we've got
00:05:01 - link local address, if we want to assign, that's for communicating on local
00:05:05 - sub-net or what is the real address we would like to assign.
00:05:08 - Let me scoot this down so I can remember. I am going to have trouble remembering
00:05:12 - these addresses when we make this move, it;s going to be
00:05:16 - IFE0:111::
00:05:19 - notice it even says you
00:05:23 - can use the double :: in this; ::1/32
00:05:28 - enter. I have now assigned a monumental moment, shed a tear,
00:05:34 - I have now assigned an IP version six; we've made the move, starting to move
00:05:38 - IP version six addressing
00:05:40 - to my router. Now I am going to exit out of here and let's go under the serial
00:05:43 - interface, this is still set up for frame relay, so it's actually
00:05:46 - interface 00/0.102;
00:05:52 - that's not it, oh sorry, it's 01/0.102.
00:05:57 - I am going to assign the, I screwed up a little
00:06:02 - bit here so I can still see the address
00:06:04 - IPV6 address
00:06:08 - 2001:210:10:1::1/64
00:06:15 - to that interface.
00:06:18 - Look at that I assigned the second IP version six address. Isn't this
00:06:23 - kind of cool, we are stepping into the future. Now I can verify
00:06:27 - show IPV6 interface and I can even go in here and say I want
00:06:33 - to do the brief, you know my show IP interface brief, show IPV6
00:06:36 - interface brief. Looks a little different, you can see there's
00:06:40 - my fast season at 0/0, it gives the link local address
00:06:44 - of that and the assigned IP address that I put in their right
00:06:48 - FE80, sorry I got that backwards, this
00:06:54 - is the link local address. You may remember FE80 designate
00:06:57 - link local; this is the mac address 214.ICFF with
00:07:03 - FF in the middle. If you want you can jump back
00:07:07 - and go to the concepts again, where I explained that link local
00:07:10 - address, this is the second half of the mac address. So you can
00:07:13 - see that assigned and then this is the one I manually assigned
00:07:16 - to the interface. Up here on the serial interface, there is the
00:07:19 - link local address for the serial interface and there's the
00:07:24 - one I manually assigned to the serial interface. So we can see
00:07:27 - we've got IP version six happening now. Now let's jump down to router
00:07:33 - two; do the same thing IPV6 unicast-routing turn it on,
00:07:41 - get into my interface fast ethernet 0/2, router two is
00:07:46 - ethernet 0/0.
00:07:49 - IPV6 address and that was
00:07:56 - IFE0:222::1/32
00:08:01 - as it's sub-net mask under interface serial
00:08:06 - 0/0.201 was the sub interface
00:08:10 - that was it and I'm going to assign, I am going to do
00:08:16 - let's to this, shrink this down like that, there we go IPV6
00:08:23 - address for that is going to be 2001:210:10:1::2/64
00:08:28 - We now have IPV6 configured
00:08:35 - and working on our WAN link between those two routers.
00:08:39 - To test it, we can ping, ping is still around IPV6.
00:08:45 - We just need to go to privilege mode. We're going to get used
00:08:47 - to typing V6 on things, ping, question mark and it says you
00:08:52 - can using IPV6 and then it says type in the address that you'd like
00:08:56 - to ping. I'm on my on router two right now, so I would like to ping
00:09:00 - 2001:210:10:1, it's not as fun to
00:09:06 - type these though, I'll tell you that.
00:09:08 - ::1 and hit enter; check it out we've got pings on IP version
00:09:15 - six going through our frame relay cloud and I was able to ping
00:09:19 - router one. Let's do the same thing, I'll do ping IPV6
00:09:23 - see if I can get to IFE0:1111::1
00:09:29 - and I'm not giving there. The reason why as you very well
00:09:33 - know by this point is because router two doesn't know about
00:09:36 - that network because it's not directly connected and we need
00:09:39 - a routing protocol.
00:09:42 - Now in IP version six we can do use static routes, global
00:09:46 - config mode IPV6 route instead of IP route, now to enter those
00:09:50 - but nearly every routing protocol that exists has also
00:09:54 - been updated to support IPV6. RIP next generation is what we are going to
00:09:59 - configure in here, but they also have OSPF version three, that's
00:10:03 - the next version, IS european version IS for IP version six. Those
00:10:07 - of been modified and BGP which is the routing protocol of
00:10:11 - the internet has now become multi-protocol BGP which supports
00:10:15 - not only IPV four addressing, but IPV6 addressing as
00:10:20 - well. So with that let me show you how to configure RIP next generation
00:10:26 - for our network so we can get some routing tables going on.
00:10:30 - I am going to bring us back up, I have got router two right here in and
00:10:34 - if I wanted to start the RIP process, I need to go into global config
00:10:38 - mode and instead of broader RIP, I type in IPV6 router
00:10:43 - hoops
00:10:45 - RIP, followed by a tag. Now this is just a string identifying the process,
00:10:51 - it's anything that you want, you can put a name, you could put
00:10:54 - number and you can put the anything there, it just identifies the RIP process.
00:10:59 - I'll just put one as my tag, but I'll need to remember that tag because
00:11:04 - we will need it when we start turning on the networks, oh
00:11:08 - and I haven't told you yet,
00:11:10 - that's all you have to do under the router process. The network
00:11:14 - statement is gone.
00:11:17 - This is great because the network statements has always
00:11:21 - been the most difficult thing for me to teach. I am completely
00:11:24 - selfish on this because it boggles everybody's
00:11:27 - mind when they are thinking, okay you use the network command to turn
00:11:31 - on RIP for the interfaces, well what do you mean. So you
00:11:34 - type network and it has to identify the interfaces that way. That's weird,
00:11:38 - it takes people a little while to catch on to the network
00:11:41 - statement that turns on RIP; now they've done what's logical.
00:11:46 - If you want to turn on a RIP for interface all you have to
00:11:49 - do is go under the interface on router two interface ethernet
00:11:53 - 0/0, that's the connecting to the LAN over here and you turn
00:11:57 - on that interface for RIP. I would say IPV6 RIP, you type
00:12:02 - in what tag, one, and then you type in enable, enter. That now
00:12:09 - turns on RP for the this interface and it's sending out
00:12:12 - hellos, well not hellos, but broadcast multi-cast traffic out
00:12:16 - that interface to say hello everybody I know about this network
00:12:20 - and its advertising this network and its advertisement. So I
00:12:23 - need to go under my interface 00/0.201
00:12:27 - frame relay interface and also type in IPV6 RIP one, enable.
00:12:33 - I go under the interfaces that I want to turn RIP on and just
00:12:37 - type in enable underneath there. Let's go onto router one
00:12:41 - and go on the global config mode; IPV6 router RIP and give
00:12:48 - it a tag and I'll stick with one. That's all we need to do
00:12:51 - to turn it on, I go underneath my interfaces, router one has fast ethernet 0/0
00:12:55 - and type in IPV6 RIP one enable,
00:13:01 - turn on RIP for that interface and interface serial 0/1/0.102
00:13:06 - which is my sub-net interface connecting the
00:13:10 - router two over frame relay.
00:13:12 - Hit the up arrow and I'm good. I now have RIP fully enabled on router
00:13:17 - one and router two.
00:13:19 - Now before I do the exciting ping attempt to router two's LAN
00:13:23 - interface, I wanted to show some of the verification commands. I
00:13:27 - can type show IPV6 RIP to see the process and see what's
00:13:32 - going on. It shows RIP process one, it's part of this multi-cast group,
00:13:36 - because remember you don't send broadcasts to ninety version six,
00:13:39 - you multi-casts, so this will be kind of its broadcasts address it is sending
00:13:43 - to you. Administrative distance is still the same, that's believability.
00:13:47 - Updates once every 30 seconds and it's working for these
00:13:50 - two interfaces. I am going to type in, remember the show IP RIP, oh
00:13:56 - sorry show IP route command; I am going to type in show IPV6 route to see
00:14:01 - the version six routing table and you can see that we have
00:14:06 - all of these routes that are being sent, we've got the keys
00:14:13 - appearing, connected interface, this is linked local connected, you
00:14:16 - know, connected.
00:14:19 - I am pondering here because I am not not seeing my RIP route from
00:14:23 - the router two; that's not good. Hang on let's look on router two, show IPV6 route,
00:14:31 - now wait a sec, it's got it there;
00:14:39 - hmm, well let's hang on router two for a second, because I've got one
00:14:45 - working. We've got router two right here that has learned about your RIP
00:14:49 - IFEO:1111 you see that right here.
00:14:53 - It learned about that from router one administrative distance of
00:14:56 - 120 two hops to get there. So
00:15:01 - it says via this, this is the next hop address, it's a link local
00:15:05 - address on 00/0/201 that's the frame
00:15:09 - relay link. Let me just go back up to router one, show IPV6
00:15:13 - route; interesting, I wonder why router one isn't learning that.
00:15:21 - Let me verify my config on router two. Let's do show run interface
00:15:27 - ethernet 0/0.
00:15:30 - Oh, ladies and gentlemen the interface is shut down. It's
00:15:37 - easy fix, I am going to go to ethernet 0/0 and do a no shut down
00:15:43 - and now we should have that interface come back on line.
00:15:48 - There we go and now let me jump back up to
00:15:53 - router one, show IPV6 route; there it is, that's
00:16:00 - it the RIP out IFE0:2222, which is the route
00:16:03 - sitting behind router two over here. Now let's do a ping, we've got
00:16:08 - a ping, ping IPV6
00:16:15 - 1FE0:2222::1,
00:16:21 - that's the LAN interface of router two. There it is, we have a successful ping.
00:16:26 - Let's try trace route, IPV6 and I'm sure with these addresses
00:16:31 - I'll be used to cutting and pasting, copy and paste.
00:16:36 - Wasn't very exciting, but one hop to get there. We went through
00:16:40 - router two, 2001:210:10:1:2, router two and then
00:16:45 - it was able to reach that address. So you can see all these
00:16:49 - commands have been modified to support IPV6.
00:16:53 - The last thing and like to talk about in IP version six is
00:16:57 - the migration strategy. How does one migrate to IPV6? Well
00:17:04 - technology exists right now to provide a smooth non pressure
00:17:09 - to transition, meaning the internet is slowly moving over to
00:17:13 - the internet version two. Companies are going to upgrade to IP version
00:17:16 - six, but the developers of this protocol and the developers
00:17:20 - of the internet to, didn't want this to be like a Y2K
00:17:23 - sort of crisis where all of a sudden on this date we're going to
00:17:27 - be making the big cut over and if you don't meet the the standards
00:17:30 - by this date your cut off, you can't access the internet anymore.
00:17:34 - It's going to be a smooth non pressured. The way that we can
00:17:37 - do it, there's three different strategies. Number one is by using
00:17:40 - dual stack routers.
00:17:43 - What we can do is go in here and set up a router that runs
00:17:49 - both protocols at the same time, IP version four and IP version
00:17:53 - version six. The router can have an IP version four internet
00:17:57 - will be around for quite some time to come, but the broader
00:18:00 - can have one link over there and one linked to the IP version
00:18:03 - six internet or internet two and as we slowly migrate our clients
00:18:08 - one by one, we have IP version called for clients, they can
00:18:12 - keep using the IP version four internet and IP version six
00:18:15 - clients will be able to use the new version six internet and
00:18:17 - we can slowly phase in phases my greater clients over. Now you
00:18:22 - might be wondering, well will there be like this great
00:18:26 - divide on the internet, where like half the sites are on the
00:18:29 - version four and half the sites are on version six; the answer is no
00:18:33 - because the internet service providers are going to be doing
00:18:36 - translations for us, meaning ISPs will offer connections
00:18:41 - to both and if you're a version four clients and you are on
00:18:44 - a version four internet through the ISP and all of a sudden you
00:18:47 - access the site that's only available on the version six, there'll
00:18:51 - be a system of the NAT, which we'll talk about just a moment
00:18:55 - that will allow you to go through a router in get NATTED out
00:18:59 - to the version six internet and likewise if you're version
00:19:02 - six client out here and you need to access the website that's
00:19:05 - only available on version four, you will kind of NAT through or translate
00:19:09 - through to the version four website and communicate with that.
00:19:13 - You will be able to reach that information. What the websites
00:19:18 - and in powers that be on the websites themselves will have
00:19:23 - websites that are assigned version four and version six addresses,
00:19:27 - so that
00:19:29 - this is a four, version four version six addresses
00:19:32 - so that they are accessible from both networks. So that's
00:19:36 - the first system is to have dual stack routers. The second
00:19:41 - one is going to be doing tunneling, meaning maybe you've got
00:19:44 - a version six internet that you are connecting to and your internal
00:19:49 - networks over here are still only running version four. Well you
00:19:53 - can create a type of tunnel which is kind of like a VPN through
00:19:59 - the over version six internet, let me just get my drawings right
00:20:03 - here through the version six internet that allows the version
00:20:06 - four protocol to work through there and communicate between
00:20:10 - these two version four networks; that will allow you, you know,
00:20:13 - even after the internet has moved to version six it will allow
00:20:17 - you to have your network still using version four and
00:20:21 - likewise, you know, maybe the internet hasn't moved to version six yet.
00:20:25 - We are still using a version four for internet. Well, you could tunnel
00:20:29 - your version six networks if you migrated your networks over
00:20:34 - to version six, through the version four internet,
00:20:38 - this is version four and allow you to run version six on your
00:20:41 - networks and tunnel through the existing internet. That is
00:20:45 - what a lot of agencies are doing overseas that have begun the
00:20:48 - migration to version six, places like Japan and China have a
00:20:52 - huge step forward in version six. Over in the United States they're
00:20:55 - running version six right now and tunneling through version
00:20:58 - four internet for most of their networks. Last but not least
00:21:02 - is NAT PT. NAT PT stands for NAT Protocol Translation.
00:21:11 - This is a specially tweaked version of NAT that can go between
00:21:16 - version four and version six protocols. So if I'm running IP version
00:21:20 - six on my internal network and connecting to the version four
00:21:23 - internet, I can NAT between those two and allow my version six clients
00:21:29 - to surf the web over here. Likewise if I have, you know, version
00:21:33 - four over here and I have not upgraded version six and the
00:21:37 - whole internet changes over and only version six internet is
00:21:41 - left, I can NAT between my version for IPV4 network and
00:21:46 - IPV6 and not really suffer any major disadvantages. Static
00:21:51 - that will work, NAT overload will work; it's just like, you know,
00:21:55 - NAT as we know it. So the cool news is, yes the internet
00:21:59 - two is out there, it's been out there for years and it slowly
00:22:03 - overtaking the world like a virus, piece by piece, network
00:22:07 - by network the internet two is growing larger and larger. In
00:22:11 - the internet that we know today the internet version four is
00:22:14 - shrinking smaller and smaller and smaller. I guess technically that's not true,
00:22:18 - it's always growing, but it will eventually shrink smaller
00:22:21 - and smaller until all that's left is the internet two where
00:22:24 - IP version six internet. At that point NAT once again comes
00:22:28 - to save the day, allowing us to run either version of the protocol
00:22:32 - on ether network.
00:22:34 - That should give you a really good idea of IP version six,
00:22:38 - what it is and where we're going with it. So let's review, we
00:22:42 - talked about assigning IPV6 addresses to your router, very similar
00:22:47 - to IPV4, we just type in IPV6 and follow it up with that
00:22:51 - address and what our address is. It's getting used to those addresses
00:22:55 - that is always going to take the time. We looked at the new routing protocol,
00:22:58 - seeing that every routing protocol has been updated to work
00:23:02 - with IP version six, including RIP version, I was going to say version six, RIP
00:23:07 - NG, next generation and we even went through and set up the
00:23:11 - base configuration of RIP to exchange IPV6 routes on our
00:23:15 - network. Finally, we just looked at all the IPV4 version
00:23:19 - six migration strategies, non pressure is the key. People will
00:23:23 - be able to move to IP version six as they get the expertise
00:23:28 - and as their network equipment allow them. I hope this is
00:23:32 - has been informative for you and I'd like to thank you for viewing.

Certification: Some Last Words for Test Takers

Advanced TCP/IP: Working with Binary

Advanced TCP/IP: IP Subnetting, Part 1

Advanced TCP/IP: IP Subnetting, Part 2

Advanced TCP/IP: IP Subnetting, Part 3

This forum is for community use – trainers will not participate in conversations. Share your thoughts on training content and engage with other members of the CBT Nuggets community. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Community Standards

We encourage you to share your wisdom, opinions, and questions with the CBT Nuggets community. To keep things civil, we have established the following policy.

We reserve the right not to post comments that:
contain obscene, indecent, or profane language; contain threats or defamatory statements; contain personal attacks; contain hate speech directed at race, color, sex, sexual orientation, national origin, ethnicity, age, religion, or disability; contributes to a hostile atmosphere; or promotes or endorses services or products. Non-commercial links, if relevant to the topic, are acceptable. Comments are not moderated, however, all comments will automatically be filtered for content that might violate our comment policies. If your comment is flagged by our filter, it will not be published.

We will be continually monitoring published comments and any content that violates our policies will be removed. Users who repeatedly violate our comments policy may be prohibited from commenting.

Course Features

Speed Control

Play videos at a faster or slower pace.


Pick up where you left off watching a video.


Jot down information to refer back to at a later time.

Closed Captions

Follow what the trainers are saying with ease.

MP3 Downloads

Listen to videos anytime, anywhere
Jeremy Cioara

Jeremy Cioara

CBT Nuggets Trainer

Cisco CCNA, CCDA, CCNA Security, CCNA Voice, CCNP, CCSP, CCVP, CCDP, CCIE R&S; Amazon Web Services CSA; Microsoft MCP, MCSE, Novell CNA, CNE; CompTIA A+, Network+, iNet+

Area Of Expertise:
Cisco network administration and development. Author or coauthor of numerous books, including: CCNA Voice 640-461 Official Cert Guide; CCNA Voice Official Exam Certification Guide (640-460 IIUC); CCENT Exam Prep (Exam 640-822); CCNA Exam Cram (Exam 640-802) 3rd Edition; and CCNA Voice 640-461 Official Cert Guide.

Add training to a playlist
or create a new list
Add to current playlist
or add to an existing list
Add to new playlist
Add New Bookmark

IPv6: Configuring, Routing, and Interoperating
Bookmark Title:

Login is required to access this feature.

Your browser cannot access Virtual Labs
Video Options

This advanced buffering is applied to all streams regardless if you installed the doublespeed control or not. Sometimes the advanced buffering causes the video to hang or behave erratically. If you are experienceing issues with video playback please disable the doublespeed buffer.

Remember to re-enable the buffer if you want to use the doublespeed control.

If you are experiencing problems with our content delivery, please click here to switch to our alternate content delivery network or go to our network FAQ.
For other common video playback issues, including firewall and corporate network issues, please visit our Tech Support forum.