ISSN ONLINE(2320-9801) PRINT (2320-9798)

Yakışıklı erkek tatil için bir beldeye gidiyor burada kendisine türk Porno güzel bir seksi kadın ayarlıyor Onunla beraber otel odasına gidiyorlar Otel odasına rokettube giren kadın ilk önce erkekle sohbet ederek işi yavaş halletmeye çalışıyor sex hikayeleri Kocası fabrikatör olan sarışın Rus hatun şehirden biraz uzak olan bir türk porno kasabaya son derece lüks bir villa yaptırıp yerleşiyor Kocasını işe gönderip mobil porno istediği erkeği eve atan Rus hatun son olarak fotoğraf çekimi yapmak üzere türk porno evine gelen genç adamı bahçede azdırıyor Güzel hatun zengin bir iş adamının porno indir dostu olmayı kabul ediyor Adamın kendisine aldığı yazlık evde sikiş kalmaya başlayan hatun bir süre sonra kendi erkek arkadaşlarını bir bir çağırarak onlarla porno izle yapıyor Son olarak çağırdığı arkadaşını kapıda üzerinde beyaz gömleğin açık sikiş düğmelerinden fışkıran dik memeleri ile karşılayıp içeri girer girmez sikiş dudaklarına yapışarak sevişiyor Evin her köşesine yayılan inleme seslerinin eşliğinde yorgun düşerek orgazm oluyor

Implementation of IPv6/IPv4 Dual-Stack Transition Mechanism

Niranjan Ravi1, Muppidathi @ Saravanan A2, Manoranjan Periyasamy3
  1. BE, Department of Electronics & Communication Engineering, PSNACET, Dindigul, Tamil Nadu, India
  2. BE, Department of Electronics & Communication Engineering, PSNACET, Dindigul, Tamil Nadu India
  3. BE, Department of Electronics & Communication Engineering, PSNACET, Dindigul, Tamil Nadu, India
Related article at Pubmed, Scholar Google

Visit for more related articles at International Journal of Innovative Research in Computer and Communication Engineering


With the exhaustion of the IPv4 addressing space quickly approaching, it has become a high priority for service providers, enterprises, IP appliances manufacturers, application developers, and governments to begin their own deployments of IPv6. A seamless migration from IPv4 to IPv6 is hard to achieve. Therefore several mechanisms are required which ensures smooth, stepwise and independent change to IPV6. Not only is the transition, integration of IPv6 is also required into the existing networks. The solutions (or mechanisms) can be divided into three categories: dual stack, tunneling and translation. Dual-stack is a preferred, most versatile way to deploy IPv6 in existing IPv4 environments. IPv6 can be enabled wherever IPv4 is enabled along with the associated features required to make IPv6 routable, highly available, and secure. In some cases, IPv6 is not enabled on a specific interface or device because of the presence of legacy applications or hosts for which IPv6 is not supported. Inversely, IPv6 may be enabled on interfaces and devices for which IPv4 support is no longer needed. In this project the Dual-Stack transition mechanism is implemented in GNS3 (Graphical Network Simulator), using CISCO routers. The operation of this network is viewed with the help of Wireshark (Packet analyzer). The topology combines both, Dual-Stack and tunneling technologies, which can be observed by capturing the packets in the router interfaces.


IPV4,IPv6,Dual-Stack, Wireshark.


Internet Protocol version 4 (IPv4) is the current Layer 3 protocol used on the Internet and most networks. IPv4 has survived for over 30 years and has been an integral part of the Internet evolution. It was originally described in RFC 760 (January 1980) and obsoleted by RFC 791 (September 1981).In the early years, even with the advent of the World Wide Web in the early 1990s, there were only about 16 million users on the Internet worldwide compared to over 2 billion by 2011 (reference: Internet World Statistics, The actual number of devices increases dramatically when taking into account that today’s users usually have multiple Internet-enabled devices such as smart phones, tablets, and laptops.In the late 1970s, a family of experimental protocols was developed known as Internet Stream Protocol (ST) and later ST2. Originally defined in Internet Engineering Note IEN-119 (1979), it was later revised in RFC 1190 and RFC 1819.ST was an experimental resource reservation protocol intended to provide quality of service (QoS) for real-time multimedia applications such as video and voice. ST consisted of two protocols— ST (Internet Stream Protocol) and Stream Control Message Protocol (SCMP). Internet Stream Protocol version 2 (ST-II or ST2) was not designed as a replacement for IPv4. The idea was that a multimedia application would use both protocols—IPv4 for the transfer of traditional packets and ST-II for packets carrying real-time data.Although it was never recognized as IPv5, when encapsulated in IP, ST uses IP Protocol Number 5 (RFC 1700). In other words, although it was never implemented, the designation “IP version 5” was already taken. Today’s standard for resource reservation is the transport layer protocol Resource Reservation Protocol (RSVP), which can be used to provide receiver-initiated setup over IPv4. RSVP is described in RFC 2205.


In [1], the myriad defined IPv4/IPv6 co-existence technologies and discusses the salient features and advantages of each to help us to decide where a given technology choice makes the most sense. From a general perspective, the set of IPv4/IPv6 co-existence technologies can be organized into three categories: dual stack - implementation of both IPv4 and IPv6 protocols on network devices; tunneling - encapsulation of an IPv6 packet within an IPv4 packet for transmission over an IPv4 network or vice-versa; translation - IP header, address, and/or port translation such as that performed by host, gateway or network address translation (NAT) devices. The paper discusses the application support of IPv6. Finally it talks about some service providers' dual protocol strategies involving a combination of technologies from multiple categories.
Internet has experienced decades of rapid development, as the cornerstone of the entire network the IPv4 also has become very mature. However, due to its own limitations, it has been gradually exposed many shortcomings, so IPv6 designed by IETF as an alternative to IPv4. This paper put forward three major transition technologies: dual-stack (Dual Stack), tunnel (Tunnel), the address protocol conversion (NAT-PT) and the experimental model of the three technologies, which provide a useful reference for future IPv6 network design. [2]
IPv6 transition presents many challenges to the Internet community, and various solutions have been proposed, including dual stack, tunneling, and translation. Tunneling supports "like-to-like" IP connectivity across an "unlike" network, whereas translation supports "like-to-unlike" IP interconnectivity. No overarching strategy exists to address all possible scenarios. Because tunneling can keep the end-to-end model that the Internet is built on, the authors have developed a tunnel-based framework that solves the transition problems in backbone and access networks with different tunneling mechanisms. [3]
With the rapid development of Internet, IPv4 protocol can no longer meet the needs of users. This is mainly due to the limitations of IPv4 in terms of addresses, routing and security. Correspondingly, IPv6 has the advantage of large address space, security, mobility, quality of service and so on. So IPv6 protocol has become the inevitable trend of network development. However IPv4 and IPv6 are incompatible protocols, so a solution to transition is required. In order to achieve smooth and stepwise transition, IETF recommends three kinds of transition mechanisms: dual stack, tunneling and translation technology. This paper introduces the principle of these transition mechanisms, emphatically proposes a solution to smooth IPv6 transition based on tunneling and translation technology. Finally, they implement two kinds of tunnel and deploy a IVI transition system. The experiment results show that the proposed solution is feasible. [4]


The migration to IPv6 needs to happen. For at least the foreseeable future, IPv4 and IPv6 will coexist and there is no deadline or switchover date to go from IPv4 to IPv6. The transition is expected to take years. The Internet Engineering Task Force (IETF) has created various protocols, tools, and mechanisms to help network administrators migrate their networks to IPv6. These techniques can be divided into three categories:
A. Dual-Stack
A dual-stack device has complete support for both IPv4 and IPv6. It can be a host, printer, server, router, or any device that can be configured to support both protocols. In the IPv4 world, this includes IPv4 addresses, Address Resolution Protocol (ARP), and Internet Control Message Protocol (ICMP) for IPv4. An IPv4 router supports IPv4 static routes and IPv4 routing protocols such as Enhanced Interior Gateway Routing Protocol (EIGRP) and Open Shortest Path First version 2 (OSPFv2). In the IPv6 realm, support means more than just a network header with longer addresses. IPv6 support includes IPv6 global unicast and link-local addresses, ICMPv6 operations including Stateless Address Auto configuration (SLAAC), and Duplicate Address Detection (DAD). An IPv6 router needs to route IPv6 packets using static routes and IPv6 routing protocols such as EIGRP for IPv6 and OSPFv3. An IPv6 router sends out ICMPv6 Router Advertisement messages and can perform tunnelling or translation services.When communicating with an IPv4 device, it behaves like an IPv4-only device. When communicating with an IPv6 device, it acts like an IPv6-only device. In Step 1 of Figure.1, dual-stack host A sends a DNS query for the quad-A (AAAA) record for In Step 2, the DNS server returns a DNS query response containing both the quad-A and A records for Host A uses the quad-A record to begin communications with the server. [5]
B. Transition
Another type of IPv4-to-IPv6 transition mechanism is tunneling. Like other transition methods, tunnelling should be considered a temporary solution until native IPv6 can be employed. A tunnel is nothing more than encapsulating one IP packet inside another. A tunnel can be an IPv4 packet encapsulated in another IPv4 packet or, for that matter, any network layer protocol over another network layer protocol. One of the challenges in integrating IPv6 into the current IPv4 networks is the ability to transport IPv6 packets over IPv4-only networks. One way to do this is to use a tunnel or, in IPv6, what is known as aTunneling is a technique that allows devices in isolated IPv6 networks to send IPv6 packets over the IPv4 network. [6] A tunnel has two types of protocols, a transport protocol and a passenger protocol. overlay tunnel. Overlay tunnels encapsulate IPv6 packets in IPv4 packets for delivery across an IPv4 infrastructure.
C. Translation
Network Address Translation (NAT) is a familiar method in IPv4, commonly used to translate between private (RFC 1918) addresses and public IPv4 address space. NAT64 transparently provides access between IPv6-only and IPv4- only networks. Address Family Translation (AFT) or simply translation, provides communications between IPv6-only and IPv4-only hosts and networks. AFT performs IP header and address translations between these two network layer protocols. [7] Like other transition methods, translation is not a long-term strategy and the ultimate goal should be native IPv6. However translation offers two major advantages over tunneling:
i. Translation provides a means for gradual and seamless migration to IPv6.
ii. Content providers can provide services transparently to IPv6 Internet users.
NAT64 is the replacement for NAT-PT, Network Address Translation – Protocol Translation, as documented in RFC 6144, Framework for IPv4/IPv6 Translation. Cisco recommends not using NAT-PT, supporting its replacement NAT64. NAT-PT has been included at the end of this chapter for reference and continuity. At the time of this writing, NAT-PT is still part of some Cisco curriculums, although it will eventually be phased out. At present, NAT-PT is more widely supported on Cisco platforms than NAT64. This will most likely change. [8]
NAT-PT has been deemed deprecated by IETF because of its tight coupling with Domain Name System (DNS) and general limitation in translation. These reasons are documented in RFC 4966, Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status. IETF proposed NAT64 as the successor to NAT-PT.


The network diagram in Figure. 3 shows the Dual-Stack implemented topology, in which R1 and R2 are two Dual- Stack routers. The router R2 is configured only with IPv4 stack.
The Network addresses are also denoted near their respective networks. A Tunneling technique is needed when we are in need of connecting IPv6 Domains via IPv4 Clouds. 6to4 Tunneling is implemented in this network to achieve connectivity between the IPv6 networks. It is a point-to-multipoint tunnel. The destination IPv4 address of the tunnel is determined from the destination IPv6 address of the packet. 6to4 tunnels require a relationship between the IPv6 prefix or network address and IPv4 tunnel addresses. The IPv6 address is reverse engineered from the IPv4 tunnel address using the format 2002: tunnel-IPv4-address::/48. This allows a single tunnel to be created that has multiple destinations - a point-to-multipoint tunnel.
Wireshark captures and Results
We can see that the ICMP message contains both, IPv4 and IPv6 fields in its packet. The contents inside these fields are examined in the following figures 5 and 6.
The main contents to be noted in the IPv4 field are the Protocol Type and the Source and Destination addresses. The Protocol field in the IPv4 header tells the Network layer at the destination host, to which Protocol this packet belongs to. Protocol 41 represents the encapsulation of IPv6 packets inside the IPv4. [9]
The Ping is done to the host in 2001:DB8:0:3::/64 network from the host in 2001:DB8:0:1::/64 network. But we can see that the Source and Destination addresses captured by the Wireshark are the IPv4-only interfaces of the Routers R1 and R3, which are the two end-points of the 6to4 Tunnel
The analysis of the IPv6 fields are shown in the figure below. The main content to be noted in IPv6 is its Source and Destination addresses.
The Source and Destination addresses in IPv6 shows the actual end-to-end addresses of the communicating hosts.


Nowadays, lots of works and researches have been done on IPv6 and its related issues, and there is still a long way to go. IPv4 and IPv6 must coexist for some number of years, and their coexistence must be transparent to end users. If an IPv4-to-IPv6 transition is successful, end users should not even notice it. Dual stacking is the preferred solution in many scenarios. The dual-stacked device can interoperate equally with IPv4 devices, IPv6 devices, and other dualstacked devices. Tunnels can be created where there are IPv6 islands separated by an IPv4 ocean, which is the norm during these early stages of the transition to IPv6.
To experiment and understand the role which IPv6 will play in the future, it is necessary for us to develop hands on experience with the IPv6 technology. Through our effort in creating a Dual-Stack network using GNS3 have allowed us to develop expertise and become technically competent with IPv6 technology in an academic environment. It can increase our knowledge towards the IPv4 to IPv6 transition and migration. We have also been able to discover the basic of IPv6 technology and implementation of transition mechanisms. It also gave us the opportunity to test and understand the IPv6 technology before any real implementation time comes. This project could be applied to other organizational setting which intends to implement IPv6 in their network interconnection.

Figures at a glance

Figure 1 Figure 2 Figure 3
Figure 1 Figure 2 Figure 3
Figure 1 Figure 2 Figure 3
Figure 4 Figure 5 Figure 6