VSRD International Journal of Electrical, Electronics & Communication Engineering, Vol. V Issue V June 2015 / 119 e-ISSN: 2231-3346, p-ISSN: 2319-2232 © VSRD International Journals: www.vsrdjournals.com

RESEARCHPAPER

IPV4 & IPV6 INTEGRATION AND TRANSITION 1Mohd. Firoz Alam*, 2Jai Singh and 3Ravinder Kumar

1,2Research Scholar, 3Assistant Professor, 1,2DepartmentofElectronics& Communication Engineering,

Al-Falah University, Faridabad, Haryana, INDIA. *Corresponding Author’s Email ID: firoz2k@gmail.com

ABSTRACT Protocol transitions are not easy, and the transition from Internet Protocol version 4 (IPv4) to Internet Protocol version 6 (IPv6) is no exception. Protocol transitions are typically deployed by installing and configuring the new protocol on all nodes within the network and verifying that all host and router operations work successfully. Although this might be easily managed in a small or midsize organization, the challenge of making a rapid protocol transition in a large organization is very difficult. Rapid protocol transition from IPv4 to IPv6 of the total networking environment is an impossible task. This paper demonstrates the coexistence of IPv4 and IPV6and show when to immigrate from IPv4 to IPV6.

Keywords: Internet Protocol Version 4 (IPv4), Internet Protocol Version 6 (IPv6), Coexistence, Dual Stack Mechanism, Transition Mechanism and TCP/IP Protocol Suite.

1. INTRODUCTION The IPv4 address structure is based on a 32-bit address length and It can manage 4.3 billion addresses, but not sufficient for the whole population of the world. The next-generation Internet Protocol, initially known as IP next generation (IPng) and then later as Internet Protocol version6 (IPv6) has been developed by the Internet Engineering Task Force (IETF) to replace the current Internet Protocol version 4 (IPv4).Transition from IPv4 to IPv6 in an instant is impossible because of the huge size of the Internet and of the large number of IPv4 users. Moreover, many organizations are becoming more and more dependent on the Internet for their daily work, and they therefore cannot tolerate downtime for the replacement of the IP protocol. When both IPv4 and IPv4 are available and the users of Internet want to connect without any restrictions, a transition mechanism is required. To enable the integration of IPv6 into current networks, several transition mechanisms have been proposed by the IETF.As a result, there will not be one special day on which IPv4 will be shifted to IPv6 completely because the two protocols can coexist without any problems.

2. BRIEF HISTORY Architecture of IPv4 and IPv6: Transmission Control Protocol/Internet Protocol (TCP/IP) is an industry standard suite of protocols that is designed for large networks consisting of network segments that are connected by routers. TCP/IP is the protocol that is used

on the Internet, which is the collection of thousands of networks worldwide that connect research facilities, universities, libraries, government agencies, private companies, and individuals. In 1970, ARPANET hosts started to use Network Control Protocol (NCP), a preliminary form of what would become the Transmission Control Protocol (TCP). In 1972, the Telnet protocol was introduced. Telnet is used for terminal emulation to connect dissimilar systems. In the early 1970s, these systems were different types of mainframe computers. In 1973, the File Transfer Protocol (FTP) was introduced. FTP is used to exchange files between dissimilar systems.In1974, the Transmission Control Protocol (TCP) was specified in detail. TCP replaced NCP and provided enhanced reliable communication services. In 1981, the Internet Protocol (IP) (also known as IP version 4 [IPv4]) was specified in detail. IP provides addressing and routing functions for end-to-end delivery. In 1982, the Defense Communications Agency (DCA) and ARPA established the Transmission Control Protocol (TCP) and Internet Protocol (IP) as the TCP/IP protocol suite. In 1983, ARPANET switched from NCP to TCP/IP. In 1984, the Domain Name System (DNS) was introduced. DNS resolves domain names (such as www.google.com) to IP addresses (such as 192.168.5.18). In 1996, the first set of IP version 6 (IPv6) standards were published.TCP/IP is the entire suite of protocols defined for use on private networks and the Internet. TCP/IP includes both the IPv4 and IPv6 sets of protocols.

Mohd. Firoz Alam, Jai Singh and Ravinder Kumar VSRDIJEECE, Vol. V (V) June 2015 / 120

Fig. 1: The Architecture of the TCP/IP Protocol Suite 3. TRANSITION MECHANISMS OF IPV4

TO IPV6 The designers of IPv6 recognized that the transition from IPv4 to IPv6 will take years and that there might be organizations or nodes within organizations that will continue to use IPv4 indefinitely. Therefore, although migration is the long-term goal, equal consideration must be given to the interim coexistence of IPv4 and IPv6 nodes.

Fig. 2: IPv4 and IPv6 Transition Mechanism

To coexist with an IPv4 infrastructure and to provide an eventual transition to an IPv6-onlyinfrastructure, the following mechanisms are used: Dual stack (Using both IPv4 and IPv6 or dual IP

layer architectures) Tunneling (IPv6 over IPv4 tunneling) Translation (IPv6 and IPv4 traffic translation)

Dual Stack or Dual IP Layer Architecture: One of the conceptually easiest ways of introducing IPv6 to a network is called the “dual stack mechanism”, which is an update of RFC 2893 [RFC2893]. Using this method a host or a router is equipped with both IPv4 and IPv6 protocol stacks in the operating system. Each such node, called an “IPv4/IPv6 node”, is configured with both IPv4 and IPv6 addresses. It can therefore both send and receive datagram belonging to both protocols and thus communicate with every node in the IPv4 and IPv6 network.IPv6/IPv4 hosts can be based on a dual IP layer or dual stack architecture. In either architecture, the

following types of traffic are possible: IPv4 IPv6 IPv6 traffic sent with an IPv4 header (IPv6 over IPv4

tunneling)

A dual IP layer contains a single implementation of Transport layer protocols such as TCP and UDP. Figure below shows a dual IP layer architecture.

Fig. 3: The Dual IP Layer Architecture

The TCP/IP protocol in Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 8, Windows 7, and Windows Vista include both IPv4 and IPv6 in a dual IP layer architecture. A node running Windows can create IPv4 packets, IPv6 packets and IPv6-over-IPv4 packets (These are IPv6 packets encapsulated with an IPv4 header.)

Fig. 4: Types of Packets with a dual IP Layer

Architecture

Mohd. Firoz Alam, Jai Singh and Ravinder Kumar VSRDIJEECE, Vol. V (V) June 2015 / 121

Dual-Stack Architecture: Dual-stack architecture contains both IPv4 and IPv6 Internet layers, but they are within different protocol stacks that contain separate implementations of Transport layer protocols such as TCP and UDP. Windows Server 2003 and Windows XP have dual-stack architecture. With both IPv4 and IPv6 protocol stacks installed, a host running Windows Server 2003 or Windows XP can create IPv4 packets, IPv6 packets and IPv6-over-IPv4 packets.

Fig. 5: The Dual-Stack Architecture

Fig. 6: Types of Packets with Dual-Stack Architecture

4. MATERIALS AND PROCEDURES In this experiment we evaluate one transition mechanism namely “Dual-Stack” mechanism using GNS3.It was configured a setup of hardware and software to achieve the desired results. The hardware include two Cisco routers of C3600 series and running Cisco IOS Software, RJ-45 connectors, UTP straight cables (cat5/cat6/cat6e), two Ethernet switches and four end-workstations running windows 7 in two different sites. The entire testing process was carried out within the GNS3 Emulation Environment using a virtual topology. We explore the impact of this approach on end to end user application using “ping” command. The prime benefit of dual stacking in the scenario is helping to understand the transition in the network from IPv4 to IPv6 and also the coexistence of IPv4 and IPv6.The prime aim of this approach is also to establish the communication between: IPv4 versus IPv4 sites end-workstations IPv6versusIPv6 sites end-workstations

The diagram below indicates that initially the end-workstations C1,C2,C3,C4corresponding to router R1 were configured with IPv4 and later end-workstations C3,C4 were replaced by IPv6 for transition purpose from IPv4 to IPv6.Similarly the end-workstations C5,C6,C7,C8 corresponding to router R2 were configured with IPv4 initially and later end-workstations C7,C8 were replaced by IPv6 for transition purpose from IPv4 to IPv6.Now the new existing network is called the network with coexistence of IPv4 and IPv6.Now the main purpose and aim of the present scenario is to configure the network in such a way that the IPv4 LAN of router R1 can share resources with IPv4 LAN of router R2 and IPv6 LAN of router R1 can share resources with IPv6LAN of router R2 also. The IP addresses assigned to the router interfaces and the end-workstations are given below:

Fig. 7: Network with Coexistence of IPv4 & IPv6

Mohd. Firoz Alam, Jai Singh and Ravinder Kumar VSRDIJEECE, Vol. V (V) June 2015 / 122

Router Interface IP Address ---------------------------------------------------------------------------------------------------------------------------------------- R1 Serial1/0 IPv4 -172.16.1.1/16 IPv6 -2001:3::1/64 Fast Ethernet 0/0 IPv4 - 192.168.1.1/24 IPv6 -2001:1::1/64 R2 Serial 1/1 IPv4 – 172.16.1.2/16 IPv6 -2001:3::2/64 Fast Ethernet 0/0 IPv4 – 10.0.0.1/8 IPv6 – 2001:2:1::1/64 ----------------------------------------------------------------------------------------------------------------------------------------

Workstation(VPC) Local Port Remote Port IP address ---------------------------------------------------------------------------------------------------------------------------------------- C1 30000 20000 IPv4 – 192.168.1.2/24 C2 30001 20001 IPv4 – 192.168.1.3/24 C3 30002 20002 IPv6 – 2001:1::2/64 C4 30003 20003 IPv6 – 2001:1::3/64 C5 30004 20004 IPv4 – 10.0.0.2/8 C6 30005 20005 IPv4 – 10.0.0.3/8 C7 30006 20006 IPv6 – 2001:2::2/64 C8 30007 20007 IPv6 – 2001:2::3/64 ---------------------------------------------------------------------------------------------------------------------------------------- 5. CONFIGURATION If IPv4 and IPv6 are configured on the same interface of a router, the router is dual-stacked. Dual-stack techniques allow IPv4 and IPv6 to co-exist in the same devices and networks.

Configuration ofRouter R1Interfaces

The syntax’s are: R1#configure terminal R1(config)# interface fastethernet0/0 R1(config-if)# ip address 192.168.1.1 255.255.255.0 R1(config-if)# ipv6 address 2001:1::1/64 R1(config-if)#no shutdown R1(config-if)#exit R1(config)#interface serial 1/0 R1(config-if)#ip address 172.16.1.1 255.255.0.0 R1(config-if)#ipv6 address 2001:3::1/64 R1(config-if)#no shutdown R1(config-if)#encapsulation hdlc R1(config-if)#clockrate 64000 R1(config-if)#exit R1(config)#

Configuration of Router R2Interfaces

The syntax’s are: R2#configure terminal R2(config)# interface fastethernet0/0 R2(config-if)# ip address 10.0.0.1 255.0.0.0 R2(config-if)# ipv6 address 2001:2::1/64 R2(config-if)#no shutdown R2(config-if)#exit R2(config)#interface serial 1/1

R2(config-if)#ip address 172.16.1.2255.255.0.0 R2(config-if)#ipv6 address 2001:3::2/64 R2(config-if)#no shutdown R2(config-if)#encapsulation hdlc R2(config-if)#clockrate 64000 R2(config-if)#exit R2(config)#

IP Routing (Static) Configurationon Router R1

The syntax’s are: R1#configure terminal R1(config)#ip routing R1(config)#ip route 10.0.0.0 255.0.0.0 172.16.1.2 R1(config)#ipv6 unicast-routing R1(config)#ipv6 route 2001:2::/64 2001:3::2 R1(config)#

IP Routing (Static) Configuration on Router R2

The syntax’s are: R2#configure terminal R2(config)#ip routing R2(config)#ip route 192.168.1.0255.255.255.0172.16.1.1 R2(config)#ipv6 unicast-routing R2(config)#ipv6 route 2001:1::/642001:3::1 R2(config)#

Verification of Router R1 to Router R2 Communication: After configuring the routers R1 and R2 the communication between the routers is verified by using “ping” command and the result is given below:

Mohd. Firoz Alam, Jai Singh and Ravinder Kumar VSRDIJEECE, Vol. V (V) June 2015 / 123

Fig. 8: Router to Router Communication Result

6. RESULTS After configuring all the devices like routers, switches and virtual PCs the communication among the IPv4 end-workstations of different sites and the communication among the IPv6 end-workstations of different sites are verified using the “ping” command. The result is given below:

Fig. 9: End-Workstations Communication Result

Packets are captured at the serial or Ethernet interface of a router. The router accepts both IPv4 and IPv6 packets. The result is given below:

Mohd. Firoz Alam, Jai Singh and Ravinder Kumar VSRDIJEECE, Vol. V (V) June 2015 / 124

Fig. 9: Packets Capturing at the Routes Interface

7. CONCLUSION Dual Stack is the simplest and most desirable way for IPv4 and IPv6 to coexist and is most likely to be the next step in a network’s evolution in general, before a wider transition to an IPv6-only Internet can be achieved worldwide (in the long term future). There are no real transition mechanisms to use within the dual stack scenario, as “Dual Stack” is a method to integrate IPv6 itself. Since configuring IPv6 routing in a dual stack network is usually completely independent from the configuration of IPv4 routing. Another challenge lies in the interaction of the two protocols, and how this interaction is managed, given that a dual-stack network will (in an early stage of worldwide IPv6 deployment) generally be interacting with IPv4 external networks. DSTM (Dual Stack Transition Mechanism is a tunneling solution for IPv6-only networks, where IPv4 applications are still needed on dual-stack hosts within an IPv6-only infrastructure. IPv4traffic is tunneled over the IPv6-only domain until it reaches an IPv6/IPv4 gateway, which is incharge of packet encapsulation/decapsulation and forwarding between the IPv6-only and IPv4-onlydomains. The solution proposed by DSTM is transparent to any type of IPv4 application and allows the use of layer 3 security.

8. REFRENCES [1] Martin Dunmore, (An IPv6 Deployment Guide), The

6NET Consortium, September 2005. [2] Understanding IPv6 by Joseph Devies, Microsoft 3rd

Edition. [3] Cisco.com IPv6 information at http://www.cisco.com/ipv6 [4] Cisco Certified Network Associated by Richard Deal, Tata

McGraw-Hill Edition, 2010

[5] Sustainable IPv4 to IPv6 Transition / Chiranjit Dutta, Ranjeet Singh / International Journal of Advanced Research in Computer Science and Software Engineering / Volume 2, Issue 10, October 2012 ISSN: 2277128X