Using IPv6 in Windows Server 2008

Using IPv6 in Windows Server 2008
IPv6 Addresses problems in IPv4

* Automatic Address Configuration – Stateful hosts use DHCPv6. Stateless hosts configure themselves.
* Header Size – Non-essential and optional fields are found in extension headers.
* Routing Table Size – Designed to be more efficient.
* Network Level Security – IPSec is now mandatory.
* Real Time Data Delivery – payload encryption does not affect QoS.
* Removal of Broadcast Traffic – Neighbour discovery replaces ARP broadcasts, ICMPv4, Router Discovery and ICMPv4 redirect messages.
* IPV6 Address Structure
* IPv6 Address Syntax

IPv6 is a 128-address divided into 16-bit boundaries. Each 16 bit block is converted to a 4 bit hex number and colons are used to separate the bits. Leading zeros can be removed and long sequences of zeros can be compressed. For example 21cd:0048:0000:0000:03ac:ae45:8e4c can be expressed as 21cd:48::3ac:ae45:8e4c
IPv6 Address Prefix

Like we do in IPv4 and express subnets as 192.168.12.0/24, we can also do this in IPv6 and would look like 21cd:53::/64
IPv6 Address Types

* Unicast
* Multicast
* Anycast

IPv6 Unicast Addresses

* Global
* Link-Local
* Site-Local
* Special
* Network Service Access Point and Internet Packet Exchange mapped addresses Microsoft MCTS Training

Planning an IPv4 to IPv6 Transition Strategy

Those Strategies include:

* Dual Stack Transition
* Configured Tunneling Transition
* Automatic Tunneling
* 6to4
* Teredo
* Intra-Site Automatic Tunnel Addressing Protocol

Implementing IPv4-to-IPv6 Compatibility

* IPv4 Compatible Address
* IPv4 Mapped Address
* Teredo Address
* ISATAP Addresses

Using IPv6 Tools

Ping works by specifying the IPv6 address. IPconfig /all will show you the IPv6 setting and IPv4 settings. Netsh interface ipv6 – ipv6 added to netsh interface commands specifies the IPv6 stack
Configuring Clients through DHCPv6

Configuring a DHCPv6 scope is very much the same as configuring an IPv4 DHCP scope. Page 87 of the book goes through a great description of configuring DHCPv6. Remember the 80/20 rule.
Planning an IPv6 Network

There are three steps to planning your IPv6 network. First step is to identify and analyze hardware requirements. Look at all the hardware you have and identify if it will all work with IPv6. If not, will you replace this hardware or continue to support the hardware.

The second step is to analyze software and application requirements Microsoft MCITP Certification. Does everything work with IPv6? If not, how will you support these applications?

Finally your last step is to document the requirements. How many sites are there, how should the prefix allocation be delegated, etc. These three steps will take a lot of time but once complete, you can draw up the project plan. Project planning isn’t covered in this lesson.

That’s all for Chapter 2, Lesson 1. There is a lot of information to digest there and for most of us, its relatively new and will take some time work through and understand it. Lesson 2 of the chapter covers Configuring DNS.

Using IPv6 in Windows Server 2008

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top