Network Transition from IPv4 to IPv6

By

Kaleem Iqbal Siddiqui

December 2014
Table of Contents
1. Introduction:........................................................................................................................................1
2. Simulation Software:...........................................................................................................................1
3. Network Design:..................................................................................................................................2
4. Network Devices:.................................................................................................................................4
5. Transition Plan:....................................................................................................................................4
5.1. Goals................................................................................................................................................4
5.2. Assessment of Existing.....................................................................................................................5
5.3. Gap Analysis.....................................................................................................................................5
5.4. Bridging Methodology.....................................................................................................................5
5.5. Disturbance Avoidance....................................................................................................................5
5.6. Implementation Plan.......................................................................................................................5
5.7. Testing.............................................................................................................................................5
6. Conclusions and Recommendations:...................................................................................................5
7. References & Bibliography:.................................................................................................................5
1. Introduction:
The internetworking is transforming towards an advanced network base, i.e., Internet Protocol version 6
(IPv6). At present, it’s largely dependent on IPv4 enabled systems with IPv6 islands-like network.
Organizations have started transition slowly without losing its existence on IPv4. The service providers
are now equipped with IPv6 subnets for those client organizations which are migrating to remain in line
with the advancements of technology. However, the individual consumers are still using the legacy
setup. The main hindrance is the invested amount in the existing equipment which lacks dual capability
to work on the legacy and the advanced protocols at the same time. The next in line are the services.
Availability of the services are the utmost priority nowadays.

Organizations normally conduct a feasibility analysis to understand the potential impact on their
business while they would migrate from IPv4 network to the advanced IPv6 network. This is a study for
a firm to understand transition scenario from Internet Protocol version 4 (IPv4) to IPv6. It includes
simulation of an IPv6 network using a free network simulator software to verify if different network
segments may work without any problem.

A network with dual-stack IP protocols, i.e., IPv4 and IPv6, is designed, where some segments are
operating on IPv4-only network, some are on IPv6-only and a few junction points with dual capabilities.
In this design, network address translation and tunneling techniques are used to communicate between
different versions of Internet Protocols. It is assumed that the Internet Service Provider (ISP) is on IPv4
whereas the contents on the internet may vary in nature. The designed network is configured on a free
simulator software which supports Cisco Integrated Operating System (IOS) images. Network
reachability is verified using Ping test.

2. Simulation Software:
A number of software are available for simulation of networks. In order to provide complete
and accurate simulations, GNS3 [1] actually uses the following emulators to run the very same
operating systems as in real networks [2]:

 Dynamips [3], the well-known Cisco IOS emulator

 VirtualBox [4], runs desktop and server operating systems as well as Juniper JunOS
 QEMU [5], a generic open source machine emulator, it runs Cisco ASA, PIX and IPS

Outcome should be realistic, practical and applicable to real environment even without conversion. The
selection of the hardware and software is based on the following parameters:

a) Capability of true emulation of hardware available in the market

b) Capability to integration with servers, virtual or physical machines
c) Capability to integrate with the Internet or any other physical network
d) Free of Cost & Availability
e) Compatibility & Functionality
f) No conversion but direct deployment to the real hardware after successful test results

1
3. Network Design:
At present, network of a firm is based on IPv4 protocol with 40 clients including Windows 7, 8 and Linux
Ubuntu operating systems, 25 Voice over IP (VoIP) phones, 02 printers. They have a local web server for
office automation application and a SIP server as VoIP phone exchange. The Internet bandwidth is 8
Mbps with 8 global IPs version 4. The network include a Cisco router for Network Address Translation
(NAT) and 02 Cisco Switches, one is 24 port and other is 48 port with Power over Ethernet (PoE) enabled
for VoIP phone sets. Figure - I depicts existing network architecture showing only limited network
devices to increase readability.

Figure - I: Existing Network Architecture

Recently, the firm has established another department and a small branch. This network extension is
planned on IPv6, keeping existing IPv4 network operational and integrated. In this regard, a network
with dual-stack IP protocols, i.e., IPv4 and IPv6, is designed, where some segments are operating on
IPv4-only network, some are on IPv6-only, whereas a few junction points are with dual capabilities. In
this design, network address translation and tunneling techniques are used to communicate between
different versions of Internet Protocols. Internet Service Providers (ISPs) of both sites are connected to
the Internet using IPv4 protocol. In Main Office, 02 switches are added to the router, “Edge -Router1”;
one for ERP server running on IPv6 and other for client machines running on Microsoft Windows 8.1. In

2
the branch office, one File Transfer Protocol (FTP) server is installed and 40 clients including VoIP phone
connected to SIP server of Main Office, a Wireless Access Point (WAP) and Personal Computers (PCs)
with Mix of operating systems; Windows and Linux. Figure - II depicts complete network setup having
capability of dual stack networking, translation and tunneling features:

Figure - II: Intermediate Network Design

Edge-Router1 in Main Office is performing multiple roles including:

 IPv4 – IPv4 network address translation for Internet connectivity

 IPv4 – IPv4 Routing between hosts of Cli-Switch and Svr-Switch
 IPv4 – IPv6 and vice versa network translation between hosts of Cli-Switch & IPv6-Cli-Sw, hosts
of Cli-Switch & IPv6-Svr-Sw, hosts of Svr-Switch & IPv6-Cli-Sw and hosts of Svr-Switch &
IPv6-Svr-Sw
 IPv6 – IPv6 Routing between hosts of IPv6-Cli-Sw and IPv6-Svr-Sw
 IPv6 – IPv4 – IPv6 tunnel with Edge-Router2 in Branch Office

Edge-Router2 in Branch Office is performing the following roles:

 IPv6 – IPv6 Routing between SW3 clients and FTP Server

 IPv4 – IPv4 network address translation for Internet connectivity
 IPv6 – IPv4 – IPv6 tunnel with Edge-Router1 in Main Office

Since, IPv4 and IPv6 addresses are 32-bit and 128-bit long, respectively, therefore, one-to-one
translation may be one sided only, i.e., from IPv4 to IPv6 network. In this case, 96-bit prefix is defined to
be padded with IPv4 for conversion into IPv6 address [6]. This padding is done by Edge Routers towards
IPv6 network. In the opposite direction, a state full translation is performed. Specific IPv4 address(es)
are reserved for service(s). This is achieved by implementing Network Address Translation – Port

3
Translation (NAT-PT) for IPv6 [7]. For connecting both sites, two techniques are incorporated:
translation and overlay tunnel. Translation is required for IPv4 hosts in Main Office to communicate with
hosts of Branch Office. Whereas overlay tunnel is used to encapsulate IPv6 packet within an IPv4 packet
[8].

4. Network Devices:
Particulars of network devices used in the simulation are given in Table - I:

Table - I: Network Devices

S/N Emulated
Device Name Device Type Software Purpose
o Hardware
i. Edge-Router1 Router Cisco 7200 15.T10 See Section 3
ii. Edge-Router2 Router Cisco 3725 15.T14 See Section 3
iii. IPv6-Svr-Sw Switch Soft switch Built-in GNS3 Aggregation of all servers
hosted on IPv6 and
connectivity with Edge-Router1
iv. IPv6-Cli-Sw Switch Soft switch Built-in GNS3 Aggregation of all clients
hosted on IPv6 and
connectivity with Edge-Router1
v. Svr-Switch Switch Soft switch Built-in GNS3 Aggregation of all servers
hosted on IPv4 and
connectivity with Edge-Router1
vi. Cli-Switch Switch Soft switch Built-in GNS3 Aggregation of all clients
hosted on IPv4 and
connectivity with Edge-Router1
vii. SW3 Switch Soft switch Built-in GNS3 Aggregation of all clients
hosted on IPv6 and
connectivity with Edge-Router2

5. Transition Plan:
IPv4-only and IPv6-only networks works well in isolation if deployed from the scratch, however, careful
analysis and execution are required for integration and change in existing network. In this regard, the
following are considered:

a) Goals
b) Assessment of Existing
c) Gap Analysis
d) Bridging Methodology
e) Disturbance Avoidance
f) Implementation Plan
g) Testing & Fine-tuning

4
5.1. Goals
There are primarily two goals in consideration; firstly, business continuity and secondly, network
implementation within given timeframe.

5.2. Assessment of Existing

Existing requirement of the users include availability of the Internet for email, browsing and few online
services, e.g., cloud storage, skype etc. Working hours are from 9 am to 6 pm, Monday through Friday.
However, off-timing may be utilized for the project. Inventory of IT equipment is available.

5.3. Gap Analysis

Additional hardware is purchased including a router, three switches, two server machines, 60 PCs and
Internet connection of 4 MB for branch office.

5.4. Bridging Methodology

Before implementation, the whole network is simulated as described in this report. Tests are conducted
to assess functionality.

5.5. Disturbance Avoidance

Network diagram and backup of configuration of all network devices are secured before any change. All
work is done in off-timings. Firstly, IPv6-only portion is set up to work independently then integration is
carried out one network segment at a time.

5.6. Implementation Plan

For implementation, configuration files used in the simulator are used.

5.7. Testing
Network is be tested against functionality, stability and performance. Test are conducted through
network reachability, i.e., Ping test.

6. Conclusions and Recommendations:

It is recommended that IPv4-only network segments be upgraded to IPv6 network so that complexity
and processing load of the network may be reduced.

7. References & Bibliography:

[1] GNS3 Official Website, http://www.gns3.com
[2] Wikipedia GNS3 page, http://en.wikipedia.org/wiki/GNS3
[3] Dynamips Source code, https://github.com/GNS3/dynamips/tree/v0.2.10
[4] Virtualbox Official Website, https://www.virtualbox.org/
[5] QEMU Official website, http://wiki.qemu.org/Main_Page
[6] Network Address Translation - Protocol Translation (NAT-PT), RFC 2766
https://tools.ietf.org/html/rfc2766

5
[7] IP Addressing: NAT Configuration Guide, Cisco IOS Release 15M&T, NAT-PT for IPv6,
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/15-mt/nat-15-mt-
book/ip6-natpt.html
[8] Cisco’s Implementing Tunneling for IPv6,
http://www.cisco.com/c/en/us/td/docs/ios/ipv6/configuration/guide/12_4t/ipv6_12_4t_book/ip6-
tunnel.html