Transition from IPv4 to IPv6 with Windows Vista

[Fanishwar]

The current IP protocol, IPv4 is reaching saturation. Then I was told that to replace it, a new protocol, IPv6 was developed. Now frankly speaking, I got no ideas in this (networking). All I am trying to do is, transition from IPv4 to IPv6 with Windows Vista. Also I am not having much knowledge about the IPv4 and neither IPv6. So it would be much better if you provide some notes regarding it. It would be really very helpful for me, if someone from your side provides some helpful information.

[Quattro]

IPv4 was designed in 1983, it uses an IP address is a 32 bit address space to 4,294,967,296 addresses. But this address space is reduced because some addresses are reserved for private networks and multicast groups, the address space is so limited. Moreover, as the Internet is essential today, the number of hosts increases exponentially and leads to suffocation long term IPv4. To overcome this problem the "Network Address Translation (NAT) was implemented, but it has only delayed the inevitable. The design of a new protocol became necessary, IPv6. The transition to IPv6 offers new opportunities, it can serve to address the countries that have little in IPv4, such as Asian countries for example, it facilitates the deployment of mobile Internet, the management of persistent connections (ADSL, cable ) and IP mobility, the use of IP in the electronics trade and general public as well as the deployment of new applications of IP terminal devices (voice, video telephony, games, interactive applications ...).

[spuff]

Under IPv6, the architecture of the address space has been remodeled, the headers have been simplified, the flows are prioritized, thereby simplifying the routing. The first 64 bits are reserved for infrastructure and subnetting. In these 64 bits, 48 bits are used to provide companies a unique prefix more or less. 16 bits allow them to do subnetting is to say their offer the possibility to create up to 65,536 subnets. The last 64 bits are reserved for the addressing of machines on each subnets, the size of the current Internet, power 2. Because of the vastness of this subnet, it has an implicit safety. Indeed, with IPv4, a subnet is generally much smaller, the scanner is fairly easy and can be done in a very short time. Now perform the same operation on an IPv6 subnet of 64 bits, will require much more resources and more time. With IPv6, the broadcast has disappeared, there remains only the unicast and multicast. However a new type of address appears, the anycast. This technique of addressing and routing that allows to redirect data to the server computer the "closest" or "more efficient" by policy routing.
Appears also multihoming: each machine has multiple IP addresses:

• An IP address link-local type, used if needed to connect the link current year (the equivalent of APIPA addresses, the prefix of the address type is fe80:.
• A unique local address (equivalent of IPv4 private addresses, but with a global unique ID for each firm type prefix FC00:.
• A global address type (equivalent to public IPv4 addresses) used to communicate over the Internet.

To date, only the prefix 2001:: is delegated to the INA, for the allocation of public address space. The majority of IPv6 addresses current public will and type 2001: ....

[Wannabe]

Apart from the huge address space, IPv6 brings many changes, NAT is no longer needed, so we can get rid of it and at the same time get rid of the false sense of security it brings with it . In addition, it will be possible to implement IPSec butt machine to machine, which is not possible through an architecture based on IPv4 NATs. In addition, recognition of the network will be protected by authentication in ICMP. IPv6 includes a mechanism for self configuration. Thus a machine when it connects to a new network, simply construct its address prefix from a broadcast by the local router, without necessarily using a DHCP server. It also simplifies the user experience, because IPv6 addresses are auto-configurable, and can be routable butt. Windows XP and Windows Server 2003 use a dual stack architecture.

[Zeverto]

Its shortcoming is the fact that the management of IPv4 and IPv6 is done in 2 TCP / IP stacks differ. Each has its own UDP and TCP, as originally Dual Stack was not designed to support IPv6. Now it is possible to independently enable or disable IPv6 or IPv4. TCP traffic over IPv6 is improved. This new architecture is based on the progress made in terms of performance, the IPv4 stack. It also implements further improvements. For example "Receive Window Auto Tuning and Compound TCP" makes much more efficient connections subject to high latency or a significant delay and provides better support for TCP traffic subject to large losses as with wireless networks. Windows Vista and Windows Server Longhorn, IPv6 is installed and enabled by default, most components of these systems now support IPv6.

[Aienstaien]

When IPv6 and IPv4 are enabled, then use the new IPv6 stack of preference. This stack provides better network connectivity to applications using IPv6, without damaging the connections using IPv4. To take full advantage of the benefits of IPv6, network applications must update the Windows Sockets functions that do not specifically specify IPv6 or IPv4. Although IPv6 addresses are auto-configurable, it can happen that we should change it. Windows XP and Windows Server 2003 as the maneuver is done via the netsh interface ipv6. Windows Vista and Windows Server Longhorn authorize the use of a graphical interface. Windows XP and Windows Server 2003, support for IPsec (Internet Protocol Security) for IPv6 traffic was limited, it did not support the IKE (Internet Key Exchange), or data encryption. It should also configure IPsec through a text file that was applied with the tool IPsec6.exe.

[Rixwel]

With Vista and Windows Server Longhorn, IPsec is supported by both IPv4 and IPv6, and similarly for IKE and data encryption. Windows Vista and Windows Server Longhorn supports the MLDv2 (Multicast Listener Discovery version 2). This technology offers the opportunity to register machines to multicast sources with their local routers. For a given multicast address, a host can specify the sources it wishes to or not listen. There are two filtering modes:

• Include mode, the host will source only from places specified in the Inclusion List.
• Exclude mode, the sources it will not come from no addresses specified in the exclusion list.

Windows Vista and Windows Server Longhorn implement LLMNR (Link-Local Multicast Name Resolution). IPv6 machines located on a subnet that does not contain a DNS server, perform only a name resolution using LLMNR. They send their requests (request and response on UDP port 5355) to a multicast group. The latter is monitored by other equipment supporting LLMNR. Whoever can satisfy this request will then respond to the sender by unicast. The WinInet API in Windows Vista and Windows Server "Longhorn" allows the use of literal addresses in the URL. For example, it will be possible to connect to a web server IPv6 address 2001: db8: 100:2 A5F: 1, just enter the URL http:// [2001: db8: 100:2 A5F:: 1] in a web browser with WinInet API, such as Internet Explorer.