Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol
1 like289 views
The final year project report analyzes packet delay in IPv4 and IPv6 networks using the Open Shortest Path First (OSPF) routing protocol. It aims to determine which protocol exhibits better performance regarding packet delay and emphasizes the necessity of migrating to IPv6 due to the exhaustion of IPv4 addresses. The report includes extensive research, data collection, and analysis to assess network performance and suggest improvements.
![Lumbini ICT Campus
Tribhuvan University
Gaindakot -2 , Nawalparasi, Nepal
Institute of Science and Technology (IOST)
Final year project on
“Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in
Open Short Path First Routing Protocol ”
[CSC – 404]
A final year project report submitted in the partial fulfillment of the requirements for
the degree of Bachelors of Science in Computer Science and Information Technology
awarded by Tribhuvan University
Under the supervision of
Er. Sulav Adhikari
Co-ordinator, Lumbini ICT Campus
Submitted by :
Kaushik Raj Panta (T.U Roll no. 3865)
Rabin Ghimire (T.U Roll no.3874)
Bishnu Sapkota (T.U Roll no.3859)
Sudip Kafle (T.U Roll no.3879)
Submitted to
Lumbini ICT Campus,
Department of Computer Science and Information Technology
Gaindakot – 2, Nawalparasi
September 11, 2017](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-1-320.jpg)
![Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in
Open Short Path First Routing Protocol
[CSC – 404]
A final year project submitted in partial fulfillment of the requirement
for the degree of Bachelor of Science in Computer Science and
Information Technology awarded by Tribhuvan University
Submitted by :
Kaushik Raj Panta (T.U Roll no. 3865)
Rabin Ghimire (T.U Roll no. 3874)
Bishnu Sapkota (T.U Roll no. 3859)
Sudip Kafle (T.U Roll no. 3879)
Submitted to
Lumbini ICT Campus,
Department of Computer Science and Information Technology
Gaindakot – 2, Nawalparasi
September 11, 2017](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-2-320.jpg)
![CHAPTER – 1 : INTRODUCTION
1.1 Background of Project
Internet Protocol is the standard protocol being used on the Internet which allows computers
to be able to communicate in order to exchange information such as data, voice, and Video.
IPv4 is the current Internet protocol that is widely used across the Internet, but in the near
future, there exist issues like insufficient public Internet Protocol version 4 address space that
does not allow the growth of the Internet. Nowadays, most of mobile devices are required to
have an IP address to connect to the Internet which leads to high consumption of IP address.
Internet Engineer Task Force has considered this issue and proposed a new version of Internet
Protocol namely IPv6 .
IPv6 is the solution to the massive growth of the Internet due to the size of the address spaces.
IPv6 addressing contains 128 bits binary value that provide 2^128 addresses. In the near
future the current IPv4 will slowly migrate to IPv6. Sailan, Hassan, and Patel state that
“Currently IPv6 network penetration is still low but it is expected to grow, while IPv4 address
pool is projected by Regional Internet Registry to be exhausted by the end of 2011”[1].
Migration from IPv4 to IPv6 is the the work done in single day because there exists some
issues in both networks. During the migration period there will be compatibility and
interoperability issues relating to IPv4 and IPv6 because IPv6 is not backward compatible
with IPv4. Govil, Govil, Kaur, and Kaur states that “The transition between IPv4 Internet
and IPv6 will be a long process as they are two completely separate protocols and it is
impossible to switch the entire Internet over to IPv6 over night. IPv6 is not backward
compatible with IPv4 and IPv4 hosts and routers will not be able to deal directly with IPv6
traffic and vice- versa” [2]. As IPv4 and IPv6 will co-exist for a long time, this requires the
transition and inter-operation mechanisms. Migrating from IPv4 to IPv6 is a complicated task
that cannot be done overnight. The size and complexity of the Internet cause this migration
task to become enormously difficult and time consuming. Next Generation Transition
proposed three main transition mechanisms that included dual stack, tunneling, and
translation [3]. These solution allow IPv4 to be able to coexist with IPv6 during the migration
period.
A Computer Network is a collection of computers, servers, mainframes, network devices,
peripherals, or other devices connected to one another to allow the sharing of data. An
excellent example of a network is the Internet, which connects millions of people all over the
world [4].
The IP is designed for use in interconnected systems of packet-switched computer
communication networks. The Internet protocol provides for transmitting blocks of data
called datagrams from sources to destinations, where sources and destinations are hosts
identified by fixed length addresses. The Internet protocol also provides for fragmentation and
reassembly of long datagrams [5].
IPv4 is the one of the core connectionless protocols of standards-based inter networking
methods of Packet Switched Network which operates on a best effort delivery model i.e. it
1](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-14-320.jpg)
![does not guarantee delivery nor does it assure proper sequencing or avoidance of duplicate
delivery. IPV4 uses 32-bit address scheme which limits the address space to 232
addresses
represented by integer value written in the dot-decimal notation consisting of four octets
expressed individually in decimal numbers and separated by periods [6].
IPv6 is an Internet Layer protocol for packet-switched inter networking and provides end-to-
end datagram transmission across multiple IP networks, closely adhering to the design
principles developed in the previous version of the protocol, IPv4. IPv6 uses a 128-bit address,
theoretically allowing 2128, or approximately 3.4X1038 addresses. It simplifies aspects of
address assignment, network renumbering, and router announcements when changing
network connectivity providers. It simplifies processing of packets in routers by placing the
responsibility for packet fragmentation into the end points [7].
OSPF is an IGP that follows LSR Algorithm for routing IP packets solely with in a single
routing domain i.e. an Autonomous system. It gathers link state information from available
routers and constructs a topology map of the network. OSPF is based on Dijkstra Algorithm
for finding shortest path and supports IPv4 and IPv6 networks and supports the CIDR
addressing model [8].
QoS is a set of technologies that work on a network to guarantee its ability to dependably run
high-priority applications and traffic under limited network capacity. Achieving the required
QoS by managing the delay, delay variation, bandwidth, and packet loss parameters on a
network becomes the secret to a successful end-to-end business solution [9].
Packet Delay is the difference in end-to-end one-way delay between selected packets in a flow
with any lost packets being ignored. The effect is sometimes referred to as jitter, although the
definition is an imprecise fit. The Packet Delay is the difference between the one-way-delay of
the selected packets [10].
The main target of this research is to study the performance between the IPv4 and IPv6 on the
basis of Packet Delay when implemented on both Dual Stack and Single Stack Mode in OSPF
routing Protocols. The result of this research will discuss later in this report.
1.2 Statement of the Problem
Networking is an important factor in every sector in today’s world. All computers if linked to
one another provide a lot of benefit such as file or resource sharing, flexibility and boosting of
storage capacity. If networking is not done in any organization.
First of all let us explore the problems in IPv4 and there are two main problems with IPv4.
First of all, today, there are 7.3 billion people in the world. Half of them own a computer of
some sort, and 6 billion have access to mobile phones. If we handed out just one IPv4 address
to every person, we would be 3 billion IP addresses short. This makes reclaiming lost address
space essentially pointless. Obviously, more addresses are needed for a modern Internet. The
other problem with IPv4 is NAT. Overloaded NAT, one IP with multiple private IP’s behind
it breaks quite a few applications and provides no additional security against Internet threats.
This results in a cost increase with no counter-benefit.
2](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-15-320.jpg)
![CHAPTER – 2 : LITERATURE REVIEW
2.1 Introduction
A literature review is a text of a scholarly paper, which includes the current knowledge
including substantive findings, as well as theoretical and methodological contributions to a
particular topic. Literature reviews are secondary sources, and do not report new or original
experimental work. Most often associated with academic-oriented literature, such reviews are
found in academic journals, and are not to be confused with book reviews that may also
appear in the same publication. Literature reviews are a basis for research in nearly every
academic field. A narrow-scope literature review may be included as part of a peer-reviewed
journal article presenting new research, serving to situate the current study within the body of
the relevant literature and to provide context for the reader. In such a case, the review usually
precedes the methodology and results sections of the work.
2.2 Related Technologies
2.2.1 Internet Protocol
The IP is the principal communications protocol in the Internet protocol suite for relaying
datagrams across network boundaries. Its routing function enables inter networking, and
essentially establishes the Internet. The Internet protocol provides for transmitting blocks of
data called datagrams from sources to destinations, where sources and destinations are hosts
identified by fixed length addresses. The Internet protocol also provides for fragmentation
and reassembly of long datagrams. The Internet protocol is specifically limited in scope to
provide the functions necessary to deliver a package of bits from a source to a destination over
an interconnected system of networks. The Internet protocol can capitalize on the services of
its supporting networks to provide various types and qualities of service .
IP usually works in combination with the TCP, which establishes a virtual connection between
a source and a destination or with UDP. As an analogy, UDP can be thought of as sending a
postcard via the postal system. It permits a user to address a packet and drop it in the
system/network whereby the user does not have direct contact with the receiver of the message
packet. TCP/IP, on the other hand, is more like a bidirectional phone call, where a connection
is established the connection between the two hosts so that the two hosts can communicate
between themselves for some time with each party acknowledging what the other party is
sending [11].
The two versions of Internet Protocol in use are IPv4 and IPv6. IPv6 was designed when it
became apparent that the number of allocated IPv4 addresses would eventually run out.
Protocol developers IPv6 as a replacement IPv4 and added many more added security features
beyond solely adding exponentially more addresses than IPv4. IPv4 and IPv6 are not
interpolatable and IPv6 will not be immediately replicable by IPv6. While many transition
mechanisms exist, host based solution where end hosts are simultaneously configured with
both IPv4 and IPv6 is the preferred configuration. This “dual stack solution” allows for a
5](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-18-320.jpg)
![single change on each host and provider shortcomings in terms of transit can be addressed
separately on upstream devices.
2.2.2 Internet Protocol version 4
2.2.2.1 Introduction
IPv4 is the one of the core connectionless protocols of standards-based inter networking
methods of Packet Switched Network which operates on a best effort delivery model i.e it
does not guarantee delivery nor does it assure proper sequencing or avoidance of duplicate
delivery. IPV4 uses 32-bit address scheme which limits the address space to 232
addresses
represented by integer value written in the dot-decimal notation consisting of four octets
expressed individually in decimal numbers and separated by periods. That means that each
device including cell phones, office phones, game consoles and computers each need their own
IP address in order to connect and communicate over the Internet. With the ever-growing
number of devices that need to connect to the Internet, it is no surprise that the amount of
available IPv4 addresses will soon be exhausted. Already, there are more devices connected
than there are routable IPv4 addresses. This is possible through a technology known as NAT
which allows multiple machines to appear as a single routable address. This comes with the
cost of the complexity involved in supporting devices deployed behind a NAT device [12].
2.2.2.2 IPv4 Packet Header
The IP uses a Datagram service to transfer packets of data between end systems using routers.
The IPv4 packet header consists of 20 bytes of data. An option exists within the header that
allows further optional bytes to be added, but this is not normally used [13]. The full header is
shown below:
Figure – 1 : Packet Header of IPv4
The header fields are discussed below:
• Version always set to the value 4 in the current version of IP
• IP Header Length number of 32 -bit words forming the header, usually five
• Differentiated Services Code Point (DSCP) is 6 bit field, which reflect the Quality of
Service needs of an application to the network.
6](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-19-320.jpg)
![• Explicit Congestion Notification (ECN) Field is 2 bits which indicates the transport
flow.
• Size of Datagram is in bytes, which gives the combined length of the header and the
data
• Identification is 16-bit number which together with the source address uniquely
identifies this packet and used during reassembly of fragmented datagrams.
• Flags, a sequence of three flags used to control whether routers are allowed to fragment
a packet, and to indicate the parts of a packet to the receiver.
• Fragmentation Offset is a byte count from the start of the original sent packet, set by
any router which performs IP router fragmentation.
• Time To Live is Number of hops /links which the packet may be routed over.
• Protocol is a SAP which indicates the type of transport packet being carried .
• Header Checksum is used to detect processing errors introduced into the packet inside
a router or bridge.
• Source Address indicates the IP address of the original sender of the packet.
• Destination Address indicates the IP address of the final destination of the packet.
• Options is used when the IP header length will be greater than five 32-bit words to
indicate the size of the options field/
2.2.2.3 IPv4 Addressing Scheme
IPv4 addresses may be represented in any notation expressing a 32-bit integer value. They are
most often written in the dot-decimal notation, which consists of four octets of the address
expressed individually in decimal numbers and separated by periods. The CIDR notation
standard combines the address with its routing prefix in a compact format, in which the
address is followed by a slash character (/) and the count of consecutive 1 bits in the routing
prefix (subnet mask) [14].
Figure – 2 : Quad-dotted IPv4 address representation
2.2.2.4 Classfull and Classless IPv4 Protocol
A classfull network is a network addressing architecture where the method divides the address
space for IPv4 into five address classes by address range. Classes A, B, C are networks of three
different network sizes, i.e. number of hosts for unicast addresses. Class D is for multicast.
7](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-20-320.jpg)
![The class E address range is reserved for future or experimental purposes. Classfull addressing
divides an IP address into the Network and Host portions along octet boundaries [15].
Classless addressing uses a variable number of bits for the network and host portions of the
address. Classless addressing treats the IP address as a 32 bit stream of ones and zeros, where
the boundary between network and host portions can fall anywhere between bit 0 and bit 31.
The network portion of an IP address is determined by how many 1's are in the subnet mask.
Again, this can be a variable number of bits, and although it can fall on an octet boundary, it
does not necessarily need to. A subnet mask is used locally on each host connected to a
network, and masks are never carried in IPv4 datagrams. All hosts on the same network are
configured with the same mask, and share the same pattern of network bits. The host portion
of each host's IP address will be unique. It allows us to use variable length subnet mask so also
known as VLSM. [16] [17].
VLSM enables you to have more than one mask for a given class of address, albeit a class A,
B, or C network number. VLSM, allows you to apply different subnet masks to the same class
address space Classfull protocols, such as RIPv1 and IGRP, do not support VLSM. To
deploy VLSM requires a routing protocol that is classless - BGP, EIGRP, OSPF, or RIPv2,
for instance[18].
2.2.2.5 Problem with IPv4
The problems with IPv4 are given below :
1) Scarcity of Address :
The IPv4 addressing system uses 32-bit address space. This 32-bit address space is
further classified to usable A, B, and C classes. 32-bit address space allows for
4,294,967,296 IPv4 addresses, but the previous and current IPv4 address allocation
practices limit the number of available public IPv4 addresses. Because scarcity of IPv4
addresses, many organizations implemented NAT to map multiple private IPv4
addresses to a single public IPv4 address. By using NAT we can map many internal
private IPV4 addresses to a public IPv4 address, which helped in conserving IPv4
addresses. But NAT also have many limitations.
2) Security Related issues:
IPSec is a protocol suit which enables network security by protecting the data being
sent from being viewed or modified. IPSec provides security for IPv4 packets, but
IPSec is not built-in and optional. Many IPSec implementations are proprietary.
3) Quality of Service:
QoS is available in IPv4 and it relies on the 8 bits of the IPv4 TOS field and the
identification of the payload. IPv4 TOS field has limited functionality and payload
identification (uses a TCP or UDP port) is not possible when the IPv4 datagram packet
payload is encrypted.
4) Address related configuration issue:
Networks and also Internet is expanding and many new computers and devices are
using IP. The configuration of IP addresses (static or dynamic) should be simple.
8](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-21-320.jpg)
![2.2.3 Internet Protocol version 6
2.2.3.1 Introduction
IPv6 is an Internet Layer protocol for packet-switched inter networking and provides end-to-
end datagram transmission across multiple IP networks. IPv6 uses a 128-bit address,
theoretically allowing 2128, or approximately 3.4X1038 addresses.It simplifies aspects of
address assignment, network renumbering, and router announcements when changing
network connectivity providers. It simplifies processing of packets in routers by placing the
responsibility for packet fragmentation into the end points [19].
2.2.3.2 IPv6 Packet Header
The fixed header of an IPv6 packet consists of its first 40 octets (320 bits). It has the following
format [20]:
Figure – 3 : Packet Header of IPv6
The header fields are discussed below:
• Source address - The 128-bit source address field contains the IPv6 address of the
originating node of the packet.
• Destination address - The 128-bit contains the destination address of the recipient node
of the IPv6 packet.
• Version/IP version - The 4-bit version field contains the number 6. It indicates the
version of the IPv6 protocol.
• Packet priority/Traffic class - The 8-bit Priority field in the IPv6 header can assume
different values to enable the source node to differentiate between the packets
generated by it by associating different delivery priorities to them.
• Flow Label/QoS management - The 20-bit flow label field in the IPv6 header can be
used by a source to label a set of packets belonging to the same flow.
• Payload length - The 16-bit payload length field contains the length of the data field in
octets/bits following the IPv6 packet header.
9](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-22-320.jpg)
![• Next Header - The 8-bit Next Header field identifies the type of header immediately
following the IPv6 header and located at the beginning of the data field (payload) of
the IPv6 packet.
• Time To Live (TTL)/Hop Limit (8 bits) - The 8-bit Hop Limit field is decremented by
one, by each node (typically a router) that forwards a packet.
2.2.3.3 IPv6 Addressing Format and Scheme
An IPv6 address is represented as eight groups of four hexadecimal digits, each group
representing 16 bits (two octets, a group sometimes also called a hextet). The groups are
separated by colons (:). An example of an IPv6 address is:
2001:0db8:85a3:0000:0000:8a2e:0370:7334
The hexadecimal digits are case-insensitive, but IETF recommendations suggest the use of
lower case letters. The full representation of eight 4-digit groups may be simplified by several
techniques, eliminating parts of the representation [21] [22]. Leading zeros in a group may be
omitted, but each group must retain at least one hexadecimal digit. Thus, the example address
may be written as [23]:
2001:db8:85a3:0:0:8a2e:370:7334
One or more consecutive groups of zero value may be replaced with a single empty group
using two consecutive colons (::), but the substitution may only be applied once in the address,
because multiple occurrences would create an ambiguous representation. Thus, the example
address can be further simplified:
2001:db8:85a3::8a2e:370:7334
IPv6 addresses are classified by the primary addressing and routing methodologies common in
networking: unicast addressing, anycast addressing, and multicast addressing.
• A unicast address identifies a single network interface. The Internet Protocol delivers
packets sent to a unicast address to that specific interface.
• An anycast address is assigned to a group of interfaces, usually belonging to different
nodes. A packet sent to an anycast address is delivered to just one of the member
interfaces, typically the nearest host, according to the routing protocol's definition of
distance.
• A multicast address is also used by multiple hosts, which acquire the multicast address
destination by participating in the multicast distribution protocol among the network
routers. A packet that is sent to a multicast address is delivered to all interfaces that
have joined the corresponding multicast group.
2.2.3.4 The Advantages of IPv6
The benefits of the Internet are drawn directly from the platform of interoperability created by
use of the Internet Protocol, leading to a large "network effect". That is, the benefits to a
company from the Internet arise not just by the extent to which the company itself uses the
10](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-23-320.jpg)
![address, significant costs will be incurred. In IPv4 based networks, this requirement has been
alleviated by the use of server based configuration of devices using DHCP which is able to
automatically allocate IP addresses to new devices on the network with the parameters set by
the network administrator. However, for this approach to work, each new device must
interact with a DHCP server, which in the case of large-scale networks is resource- and time-
intensive. In contrast, IPv6 address allocation is done by the device itself and can occur
independently of a server, or in conjunction with an IPv6 enabled router, as appropriate.
While many Internet based applications will continue to operate under IPv4, the challenges of
network administration and security management continue to grow. For instance, if two
companies merge and want to merge their IP based networks then there will have to be
renumbering. On the Internet, if the source of malevolent activity needs to be identified, the
closest identification by IP address possible under an IPv4 NAT architecture is the globally
routable IPv4 address of the top level NAT server [24].
2.2.4 Routing Protocols
A routing protocol specifies how routers communicate with each other, disseminating
information that enables them to select routes between any two nodes on a computer network.
Routing algorithms determine the specific choice of route. Each router has a priori knowledge
only of networks attached to it directly. A routing protocol shares this information first
among immediate neighbors, and then throughout the network. This way, routers gain
knowledge of the topology of the network [25].
Although there are many types of routing protocols, three major classes are in widespread use
on IP networks:
• Interior gateway protocols type 1, link-state routing protocols, such as OSPF
• Interior gateway protocols type 2, distance-vector routing protocols, such as Routing
Information Protocol, RIPv2.
• Exterior gateway protocols are routing protocols used on the Internet for exchanging
routing information between Autonomous Systems, such as Border Gateway Protocol
(BGP), Path Vector Routing Protocol.
Exterior gateway protocols should not be confused with Exterior Gateway Protocol (EGP), an
obsolete routing protocol.
2.2.4.1 Autonomous System
Autonomous system (AS) is a collection of connected IP routing prefixes under the control of
one or more network operators on behalf of a single administrative entity or domain that
presents a common, clearly defined routing policy to the Internet [26].
Autonomous systems can be grouped into four categories, depending on their connectivity
and operating policy.
• A multi homed autonomous system is an AS that maintains connections to more than
one other AS. This allows the AS to remain connected to the Internet in the event of a
complete failure of one of their connections. However, unlike a transit AS, this type of
AS would not allow traffic from one AS to pass through on its way to another AS.
12](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-25-320.jpg)
![• A stub autonomous system refers to an AS that is connected to only one other AS. This
may be an apparent waste of an AS number if the network's routing policy is the same
as its upstream AS's. However, the stub AS may, in fact, have peering with other
autonomous systems that is not reflected in public route-view servers. Specific
examples include private interconnections in the financial and transportation sectors.
• A transit autonomous system is an AS that provides connections through itself to other
networks. That is, network A can use network B, the transit AS, to connect to network
C. If one AS is an ISP for another, then the former is a transit AS.
• An Internet Exchange Point autonomous system (IX or IXP) is a physical
infrastructure through which Internet service providers (ISPs) or content delivery
networks (CDNs) exchange Internet traffic between their networks.
2.2.4.2 Interior Routing Protocol
An IGP is a type of protocol used for exchanging routing information between gateways
(commonly routers) within an autonomous system (for example, a system of corporate local
area networks). This routing information can then be used to route network-layer protocols
like IP [27].
2.2.4.2.1 Distance Vector Routing Protocol
Distance-vector routing protocols use the Bellman–Ford algorithm. In these protocols, each
router does not possess information about the full network topology. It advertises its distance
value (DV) calculated to other routers and receives similar advertisements from other routers
unless changes are done in local network or by neighbors (routers). Using these routing
advertisements each router populates its routing table. In the next advertisement cycle, a
router advertises updated information from its routing table. This process continues until the
routing tables of each router converge to stable values [28].
Some of these protocols have the disadvantage of slow convergence.
Examples of distance-vector routing protocols:
• Routing Information Protocol (RIP)
• Routing Information Protocol Version 2 (RIPv2)
• Routing Information Protocol Next Generation (RIPng), an extension of RIP version 2
with support for IPv6
• Interior Gateway Routing Protocol (IGRP)
2.2.4.2.2 Link State Routing Protocol
In link-state routing protocols, each router possesses information about the complete network
topology. Each router then independently calculates the best next hop from it for every
possible destination in the network using local information of the topology. The collection of
best-next-hops forms the routing table.
13](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-26-320.jpg)
![This contrasts with distance-vector routing protocols, which work by having each node share
its routing table with its neighbors. In a link-state protocol, the only information passed
between the nodes is information used to construct the connectivity maps [29].
Examples of link-state routing protocols:
• Open Shortest Path First (OSPF)
• Intermediate system to intermediate system (IS-IS)
2.2.4.2.3 Hybrid Routing Protocol
Hybrid routing protocols have both the features of distance vector routing protocols and
linked state routing protocols. One example is EIGRP.
2.2.4.3 Exterior Routing Protocol
An Exterior Gateway Protocol is a routing protocol used to exchange routing information
between autonomous systems. This exchange is crucial for communications across the
Internet. Notable exterior gateway protocols include Exterior Gateway Protocol (EGP), now
obsolete, and Border Gateway Protocol (BGP) [30].
2.2.5 Open Short Path First
OSPF is an IGP that follows LSR Algorithm for routing IP packets solely with in a single
routing domain i.e. an Autonomous system. It gathers link state information from available
routers and constructs a topology map of the network. OSPF is based on Dijkstra Algorithm
for finding shortest path and supports IPv4 and IPv6 networks and supports the CIDR
addressing model [31].
OSPF detects changes in the topology, such as link failures, and converges on a new loop-free
routing structure within seconds. It computes the shortest-path tree for each route using a
method based on Dijkstra's algorithm. The OSPF routing policies for constructing a route
table are governed by link metrics associated with each routing interface. Cost factors may be
the distance of a router (round-trip time), data throughput of a link, or link availability and
reliability, expressed as simple unitless numbers. This provides a dynamic process of traffic
load balancing between routes of equal cost. An OSPF network may be structured, or
subdivided, into routing areas to simplify administration and optimize traffic and resource
utilization. Areas are identified by 32-bit numbers, expressed either simply in decimal, or often
in the same octet-based dot-decimal notation used for IPv4 addresses. By convention, area 0
(zero), or 0.0.0.0, represents the core or backbone area of an OSPF network. [32].
OSPF does not use a transport protocol, such as UDP or TCP, but encapsulates its data
directly in IP packets with protocol number 89. This is in contrast to other routing protocols,
such as the RIP and the BGP. OSPF implements its own transport layer error detection and
correction functions. OSPF uses multicast addressing for distributing route information
within a broadcast domain [33].
14](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-27-320.jpg)
![2.2.5.1 OSPF Interfaces
Another important idea in OSPF is that interfaces used to exchange information with OSPF
neighbors have different types. There are too many types to discuss here but you should be
aware of two important ones .
1. An OSPF broadcast interface is connected to a shared network, like Ethernet.
2. An OSPF point-to-point interface is connected to a link where there can only be a
single OSPF router on either end, such as a WAN link or a purpose-built Ethernet link.
The reason for the various interface types is to make sure that all routers know about all
routes from all other routers.
On point-to-point links, there’s no mystery — the two routers know they’re the only OSPF
routers on the link and so they exchange routes with each other.
On broadcast links, there’s a potential for many different OSPF routers to be on the network
segment. To minimize the number of neighbor relationships that form on broadcast links,
OSPF elects a designated router (as well as a backup) whose job it is to neighbor with all other
OSPF routers on the segment and share everyone’s routes with everyone else. [34]
2.2.5.2 OSPF Areas
Areas in OSPF are collections of routers grouped together. With the exception of area border
routers, OSPF routers in one area don’t neighbor with routers in other areas. Among other
reasons, areas were once used to scale large OSPF networks.
Back when router CPUs were less powerful than they are today, a general rule of thumb was
to keep an OSPF area to no more than 50 routers. That would keep the number of OSPF
shortest path computations and database updates to a manageable amount as interfaces went
up and down, routes were learned and withdrawn, and so on.
The most important area in OSPF is the backbone area, also known as area 0. The backbone
area is the area that all OSPF areas must traverse to get to other OSPF areas.
While OSPF routers within an area know everything there is to know about the network
topology, topology information is hidden at area borders [35].
Figure – 4 : Area System of OSPF
15](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-28-320.jpg)
![2.2.5.3 OSPFv3 vs OSPFv2
The difference between OSPFv2 and OSPFv3 are [36]:
1) Link-local addresses: OSPFv3 packets are sourced from link-local IPv6 addresses.
2) Links, not networks: OSPFv3 uses the terminology links where we use networks in
OSPFv2.
3) New LSA types: there are two new LSA types, and LSA type 1 and 2 have changed.
4) Interface commands: OSPFv3 uses interface commands to enable it on the interface,
we don’t use the network command anymore as OSPFv2 does.
5) OSPFv3 router ID: OSPFv3 is unable to set its own router ID like OSPFv2 does.
Instead, you have to manually configure the router ID. It is configured as a 32-bit
value, same as in OSPFv2.
6) Multiple prefixes per interface: if you have multiple IPv6 prefixes on an interface
then OSPFv3 will advertise all of them.
7) Flooding scope: OSPFv3 has a flooding scope for different LSAs.
8) Multiple instances per link: You can run multiple OSPFv3 instances on a single link.
9) Authentication: OSPFv3 doesn’t use plain text or MD5 authentication as OSPFv2
does. Instead, it uses IPv6’s IPSec authentication.
10) Prefixes in LSAs: OSPFv2 shows networks in LSAs as network + subnet mask,
OSPFv3 shows prefixes as prefix + prefix length.
2.2.5.4 OSPFv2 and OSPFv3 Header Comparison
Figure – 5 : OSPFv2 and OSPFv3 Header Comparison
2.2.5.5 Hello Packet Comparison
Figure -6 : OSPFv2 and OSPFv3 Hello Packet Comparison
16](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-29-320.jpg)
![2.2.6 Internet Control Message Protocol
The ICMP is a supporting protocol in the Internet protocol suite. It is used by network
devices, including routers, to send error messages and operational information indicating, for
example, that a requested service is not available or that a host or router could not be reached.
ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to
exchange data between systems, nor is it regularly employed by end-user network applications.
ICMP uses the basic support of IP as if it were a higher level protocol, however, ICMP is
actually an integral part of IP. Although ICMP messages are contained within standard IP
packets, ICMP messages are usually processed as a special case, distinguished from normal IP
processing. In many cases, it is necessary to inspect the contents of the ICMP message and
deliver the appropriate error message to the application responsible for transmission of the IP
packet that prompted the sending of the ICMP message [37].
2.2.6.1 ICMPv4
ICMPv4 is the implementation of the ICMP for IPv4. ICMPv4 is an integral part of IPv4 and
performs error reporting and diagnostic functions, and has a framework for extensions to
implement future changes. ICMP is not a transport protocol that sends data between systems.
While ICMP is not used regularly in end-user applications, it is used by network
administrators to troubleshoot Internet connections [38].
Figure – 7 : Header of ICMPv4
2.2.6.2 ICMPv6
ICMPv6 is the implementation of the ICMP for IPv6. ICMPv6 is an integral part of IPv6 and
performs error reporting and diagnostic functions, and has a framework for extensions to
implement future changes [39].
Several extensions have been published, defining new ICMPv6 message types as well as new
options for existing ICMPv6 message types. NDP is a node discovery protocol in IPv6 which
replaces and enhances functions of ARP. SEND is an extension of NDP with extra security.
MLD is used by IPv6 routers for discovering multicast listeners on a directly attached link,
much like IGMP is used in IPv4. MRD allows discovery of multicast routers [40].
8 bit type 8 bit code 16 bit checksum
17](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-30-320.jpg)
![32 bit Message body
Figure – 8 : Header of ICMPv6
2.2.7 Quality of Service
QoS is the description or measurement of the overall performance of a service, such as a
telephony or computer network or a Cloud computing service, particularly the performance
seen by the users of the network. To quantitatively measure quality of service, several related
aspects of the network service are often considered, such as error rates, bit rate, throughput,
transmission delay, availability, jitter, etc. Not only is QoS necessary for voice and video
streaming over the network, it's also an important factor in supporting the growing IoT. The
goal of QoS is to provide preferential delivery service for the applications that need it by
ensuring sufficient bandwidth, controlling latency and jitter, and reducing data loss [41].
Fundamentally, QoS enables you to provide better service to certain flows. This is done by
either raising the priority of a flow or limiting the priority of another flow. When using
congestion-management tools, you try to raise the priority of a flow by queuing and servicing
queues in different ways. The queue management tool used for congestion avoidance raises
priority by dropping lower-priority flows before higher-priority flows. Policing and shaping
provide priority to a flow by limiting the throughput of other flows. Link efficiency tools limit
large flows to show a preference for small flows. QoS tools can help alleviate most congestion
problems. However, many times there is just too much traffic for the bandwidth supplied. In
such cases, QoS is merely a bandage. [42].
2.2.7.1 QOS Basic Architecture
The basic architecture introduces the three fundamental pieces for QoS implementation [43]:
• QoS identification and marking techniques for coordinating QoS from end to end
between network elements
• QoS within a single network element (for example, queuing, scheduling, and traffic-
shaping tools)
• QoS policy, management, and accounting functions to control and administer end-to-
end traffic across a network
18](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-31-320.jpg)
![Figure – 9 : Basic Architecture of QoS
2.2.7.2 Qualities of QOS
In packet-switched networks, quality of service is affected by various factors, which can be
divided into “human” and “technical” factors. Human factors include: stability of service,
availability of service, delays, user information. Technical factors include: reliability,
scalability, effectiveness, maintainability, grade of service, etc.
Many things can happen to packets as they travel from origin to destination, resulting in the
following problems as seen from the point of view of the sender and receiver [44]:
1. Low throughput
Due to varying load from disparate users sharing the same network resources, the bit
rate (the maximum throughput) that can be provided to a certain data stream may be
too low for real time multimedia services if all data streams get the same scheduling
priority.
2. Dropped packets
The routers might fail to deliver (drop) some packets if their data loads are corrupted,
or the packets arrive when the router buffers are already full. The receiving application
may ask for this information to be retransmitted, possibly causing severe delays in the
overall transmission.
3. Errors
Sometimes packets are corrupted due to bit errors caused by noise and interference,
especially in wireless communications and long copper wires. The receiver has to detect
this and, just as if the packet was dropped, may ask for this information to be
retransmitted.
4. Latency
It might take a long time for each packet to reach its destination, because it gets held
up in long queues, or it takes a less direct route to avoid congestion. This is different
from throughput, as the delay can build up over time, even if the throughput is almost
normal. In some cases, excessive latency can render an application such as VoIP or
online gaming unusable.
5. Jitter
Packets from the source will reach the destination with different delays. A packet's
delay varies with its position in the queues of the routers along the path between source
and destination and this position can vary unpredictably. This variation in delay is
known as jitter and can seriously affect the quality of streaming audio and/or video.
6. Out-of-order delivery
When a collection of related packets is routed through a network, different packets
may take different routes, each resulting in a different delay. The result is that the
packets arrive in a different order than they were sent. This problem requires special
additional protocols responsible for rearranging out-of-order packets to an
isochronous state once they reach their destination. This is especially important for
19](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-32-320.jpg)
![video and VoIP streams where quality is dramatically affected by both latency and lack
of sequence.
2.2.8 Latency
Latency is the delay from input into a system to desired outcome; the term is understood
slightly differently in various contexts and latency issues also vary from one system to another.
Latency greatly affects how usable and enjoyable electronic and mechanical devices as well as
communications are. Latency in communication is demonstrated in live transmissions from
various points on the earth as the communication hops between a ground transmitter and a
satellite and from a satellite to a receiver each take time. People connecting from distances to
these live events can be seen to have to wait for responses. This latency is the wait time
introduced by the signal traveling the geographical distance as well as over the various pieces
of communications equipment [45].
2.2.8.1 Types of latency
Network latency is an expression of how much time it takes for a packet of data to get from
one designated point to another. In some environments (for example, AT&T), latency is
measured by sending a packet that is returned to the sender; the round-trip time is considered
the latency. Ideally, latency is as close to zero as possible.
1) Internet latency is just a special case of network latency - the Internet is a very large
WAN. The same factors as above determine latency on the Internet. Internet latency
measurement would generally start at the exit of a network and end on the return of the
requested data from an Internet resource.
2) Interrupt latency is the length of time that it takes for a computer to act on an
interrupt, which is a signal telling the operating system to stop until it can decide what
it should do in response to some event.
3) WAN latency itself can be an important factor in determining Internet latency. A
WAN that is busy directing other traffic will produce a delay whether a resource is
being requested from a server on the LAN, another computer on that network or
elsewhere on the Internet. LAN users will also experience delay when the WAN is busy.
4) Audio latency is the delay between sound being created and heard. In sound created
in the physical world, this delay is determined by the speed of sound, which varies
slightly depending on the medium the sound wave travels through.
5) Computer and operating system latency is the combined delay between an input or
command and the desired output. In a computer system, latency is often used to mean
any delay or waiting that increases real or perceived response time beyond what is
desired. Specific contributors to computer latency include mismatches in data speed
between the microprocessor and input/output devices, inadequate data buffers and the
performance of the hardware involved, as well as its drivers. The processing load of the
computer can also add significant latency.
Latency issues are noticeable for an individual, generally increasing user annoyance and
impacting productivity as the level increases above 30ms. The severity of the effect varies from
20](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-33-320.jpg)
![forwarding. It is basically happen due to priority scheme of the network. In our
concept, Forwarding Delay can be seen in IPv6 packets because priority is given to
only IPv4 packets.
2.2.9.2 Types of Delays in Packet Switch Networks
There are four major types of delays on each node of a packet-switched network:
a) Processing Delay
When a packet reaches a router, the router reads the header, locates its final
destination, and decides which outbound link to send it on. It also may do some
transmission error checking. These account for the processing delay.
b) Queuing Delay
Most routers utilize a first-come-first-serve queue for packet traffic. If traffic on the
router is busy, then the packet will have to wait in a queue for its turn to be transmitted
by the router. This accounts for the queuing delay.
c) Transmission Delay
The amount of time it takes a router to push out the next packet on to the link is the
transmission delay. This delay is a function of the size of the packet and the
transmission rate of the link.
d) Propagation Delay
The amount of time it takes to propagate the packet from the beginning of the link to
the next link is the propagation delay. It is a function of the length of the link and the
speed of the link.
2.2.9.3 Cause of Packet Delays
There are two main reasons why delays occur :
1. Network connections – If there are a high number of users connected, or there is a
high volume of bandwidth being used while you are also trying to use a VoIP
connection, you will likely see a drop in call quality. Be aware that peak usage times
e.g., working hours for businesses, may result in some delays.
2. End systems – Sometimes, it is the end system – the system where the data packets are
reassembled into data – that creates the delay. The cause of this is usually older
equipment that lacks the computing power to handle fast connections and large data
transfers.
2.2.9.4 Ways to reduce Reduce Packet Delays
Following are the some of the reasons using which we can reduce Packet delays [46]:
a) Content Delivery Network
22](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-35-320.jpg)
![The most important factor that gives rise to Internet latency is distance. The speed of
communications over the Internet is limited. And as such the greater the distance
between a website or application server and the end user the longer it will take to load
that particular website or application. A good way to overcome distance related
network latency is to use a CDN. CDNs have a network of geographically distributed
edge locations in close proximity to end users.
b) Prioritizing the packets
Generally, we must have to find the type of packets that we will be using and must have
to prioritize the networks packets according to it. For example if we are using IPv6
networks, then we must prioritize the routers to process IPv6 packets at first rather
than processing IPv4 packets and same for vice versa.
c) Anycast
Building an anycast architecture can also help to decrease latency. There are two
aspects of anycast that are important to the discussion about reducing latency: Anycast
DNS and BGP anycast. Anycast DNS allows DNS queries to be routed to the
topologically nearest DNS server, resulting in reduced network latency and quicker
DNS query responses. Once your query has been resolved into a unique IP address.
Anycast BGP takes over and routes your request to the topologically nearest web
server. Anycast BGP again has the advantage of reducing the distance that requests
have to travel leading to lower latency.
d) Network Monotoning
Monitoring your network to identify potential network bottlenecks can be helpful in
reducing Internet latency. Tools like the network latency test can be used to test
networt latency to different IP prefixes. Network monitoring is a good strategy to get
in front of potential network problems. However, network monitoring can only take
you so far. Once a network problem like high latency has been identified, network
engineers have to go ahead and make manual changes to network topology. Network
monitoring can also end up being reactive in nature.
2.2.10 Dual Stack
Dual-stack is one of the most widely adopted techniques for IPv6 migration. It helps to
establish communication between your IPv6 network and the native IPv4 hosts and
applications [47]. A dual-stack node has support for both protocol versions and is referred to
as an IPv6/IPv4 node. IPv6/IPv4 nodes have three modes of operation:
• IPv4 only - IPv4 stack enabled and IPv6 stack disabled
• IPv6 only - IPv6 stack enabled and IPv4 stack disabled
• Both IPv4 and IPv6 stacks enabled
23](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-36-320.jpg)
![2.2.10.1 Dual Stack Transition Mechanism
DSTM is a transition mechanism based on the usage of IPv4-over-IPv6 tunnels to facilitate
interoperability between newly deployed IPv6 networks and existing IPv4 networks [48].
Significant Advantages:
• Transparent to the network and to the application
• Legacy IPv4 applications can be run over IPv6-only networks without modification
• IPv4 addresses are dynamically allocated as needed and then reclaimed
• Based on standard protocols
2.3 Review of Conceptual Prospective of the study
In this section we cover the parameters that affects the performance of the network, among
those some are :
• Packet Delay
• Packet Header
• Routing Protocol
• Dual Stack Mode
Brief Description of those parameters are:
1) Packet Delay:
Packet delay PDV is the difference in end-to-end one-way delay between selected
packets in a flow with any lost packets being ignored.
2) Packet Header
An IP packet consists of a header section and a data section. The data section is the size
of data that is desired to be transfer from one host to another where the packet header
is always remained attached with the in either of the two protocols, IPv4 and IPv6. The
header structure of IPv4 remains same and only the size and the padding value differs
according to the header length. The header length is the four bit binary the starts from
decimal 5 to 15 that makes the variation on the header size ranges from minimum 20
bytes to 60 bytes. The header structure of IPv6 have some changes with respect to some
fields values. The size of the IPv6 header always remains same as the the header length
is always equal to 40 bytes.
Thus, the performance of IPv6 only differs due to the amount of data sent over the
network whereas the performance of IPv4 can get variation due to its changing header
size.
3) Routing Protocol
A routing protocol specifies how routers communicate with each other, distributing
information that enables them to select routes between any two nodes on a computer
network. Routing algorithms determine the specific choice of route. Each router has a
priori knowledge only of networks attached to it directly. A routing protocol shares
this information first among immediate neighbors, and then throughout the network.
This way, routers gain knowledge of the topology of the network. There are various
routing protocols that can be used according to the required environment. Among
which we here will use the OSPF and OSPFv3 routing Protocol which is Dynamic
24](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-37-320.jpg)
![Routing Protocol. There are other various routing Protocols that can be used and
which can differ the performance of overall network.
4) Dual Stack Mode
Dual Stack mode is the transition mechanism that enables both IPv4 and IPv6 to be
configured in a same interface from where the communication between IPv4 and IPv6
is possible. This is because the hosts with different IP can get communicate between
each other using this transition mechanism. However the problem with Dual Stack is
that it gives more priority to IPv4 packets rather than the IPv6 packets which as a
result makes the variation in the transferring of packets.
2.4 Related Literature Review
As we were researching in the domain of our project we got to read different related works
and documents which somehow relates to our domain and we too developed our ideas on the
basis of these researched documents. Here are number of studies related to IPv4 and IPv6
transition mechanisms have been studied in the past. This section covers review of studies
relating to the performance evaluation of various transition mechanisms, which will be using
as part of secondary resources in data gathering. The following are the five studies:
1) Study – 1 : IPv4 vs. IPv6 on various Operating Systems using Jumbo Frames
First of all we review the research document on “Performance Analysis of IPv4 vs.
IPv6 on various Operating Systems using Jumbo Frames” [49]. The purpose of this
study is to evaluate the performance of Jumbo frames on a network environment
employing six operating systems from two different distributions. These operating
systems are Microsoft Windows Server 2008, Microsoft Windows Server 2003 and
Microsoft Windows 7 Professional and from the Linux distributions, Linux Fedora,
Ubuntu and OpenSUSE. In this study, two transmission protocols were employed
namely, TCP and the UDP. Two Internet protocols were also engaged in these
performance experiments,IPv6 and IPv4. There were five main performance metrics
extracted from the data collected in this experimental study namely the throughput,
delay, jitter, the CPU utilizations on the software routers and the packets dropped rate.
The Jumbo frame sizes involved ranging from 1518 Bytes to 9014 Bytes.
The findings of this study concluded that for traffic employing TCP as transport
protocol, Microsoft Windows Server 2008 and Microsoft Windows 7 yielded the
highest throughput on both IPv6 and IPv4 and also Linux OpenSUSE on IPv4 only.
When UDP was employed as transmission protocol, all of the operating systems
yielded similar throughput values. This project developed us the idea that using a
jumbo frames on Microsoft Products will provide highest throughput, jitter and lower
delay compared linux products where as the concept of jumbo frames were out of our
research domain.
2) Study – 2 : IPv4 and IPv6 transition mechanisms on various operating systems
As we were moving ahead we landed on the research document of “Performance
evaluation of IP version 4 and IP version 6 transition mechanisms on various operating
systems” [50]. The purpose of this research is to evaluate performance of two tunneling
mechanisms (Configured Tunnel and 6to4 tunneling mechanisms) operate on four
25](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-38-320.jpg)
![selected operating systems (Windows Server 2003, Windows Server 2008, Ubuntu 9.10,
and Fedora Core 11). This performance measurement research examined on two types
of transmission protocols namely UDP and TCP. The result of this research focused on
four metrics such as throughput, delay, jitter, and CPU utilization. The experiments
conducted using different payload sizes, ranging from 64 bytes to 1536 bytes.
Results of this experimental research indicated that, Configured Tunnel and 6to4
perform differently on Windows Server 2003, Windows Server 2008, Ubuntu 9.10, and
Fedora 11. By using TCP as transport protocol, Configured Tunnel on Fedora 11
produced the highest throughput. However, it also produced a very high delay as
compared to Ubuntu 9.10, Windows Server 2003, and Windows Server 2008.On the
other hand, after measuring UDP traffic, the results indicated that 6to4 on Ubuntu
9.10 produced the highest throughput with the lowest delay, which designate as the best
choice for video and voice traffics.
But again from this research we gain the concept of different packet sizes that can be
used in the networks where as the concept of tunneling mechanism were way out of our
research domain.
3) Study – 3 : IPv6 vs. IPv4 under a Dual-Stack Environment
In this paper done by Uk-Nam Law, Man-Chiu Lai, Wee Lum Tan and Wing Cheong
Lau(), they present comprehensive empirical measurements of the IPv6 network
performance from an end-users perspective [51]. First of all they particularly have
chooses about 2000 dual stack host worldwide and send the probing traffic to each of
the host which acts as the test bed for their research domain. They quantify the
performance differences of using IPv6 vs. IPv4, in terms of various network metrics like
network connectivity, hop count, RTT, throughput, operating systems dependencies as
well as the address configuration latency. They have also investigated the performance
impact of using IPv6 tunneling brokers instead of native IPv6 services. Whenever
possible, They also compare their measurement results with previously published ones
to reflect on the progress of IPv6 deployment/performance improvements in the past
few years. They have designed and implemented an active measurement methodology
to evaluate the performance of IPv6 against IPv4 from an end-user’s perspective. Our
measurements are conducted between our dual-stack testbed and 2,014 other dual-
stack sites in the world. They used both ICMP and TCP traffic to measure the IPv6
network performance. In addition to that, they have also evaluated the latency
performance of IPv6 address provisioning mechanisms. Finally, they have also
investigated the performance of tunneled-IPv6 connections through the services of 3
tunnel brokers; AARNet, Euro6IX and FreeNet6.
In general, Their measurement results indicate that the IPv6 network is able to provide
stable network connectivity for IPv6 end-hosts. Due to the relatively light traffic load
and abundant bandwidth in the IPv6 backbone, the IPv6 throughput is easily superior
to that of IPv4. They have also seen that the tunneled-IPv6 services can achieve
performance similar to that of native-IPv6 services. On the other hand, there is still
considerable room for improvement in terms of reducing the IPv6 path RTT through
the deployment of more IPv6 nodes in the backbone in order to increase the link
connectivity of the IPv6 networks around the world. Furthermore, Their results also
26](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-39-320.jpg)
![show the need for an improvement in the IPv6 performance of Windows-based clients,
as compared to Unix-based clients. This is necessary in order to reduce the dependence
of the IPv6 performance on the type of operating systems used by the IPv6 end-hosts.
4) Study – 4 : IPv4 and IPv6 Routing Protocols on Wired, Wireless and Hybrid
Networks
A research on “Performance Evaluation of IPv4 and IPv6 Routing Protocols on Wired,
Wireless and Hybrid Networks” [52] where they basically used a sample network of an
network configured by both Ipv4 and IPv6 in different routing protocols such as RIP &
OSPF. Here they primarily developed three type of scenario wired, wireless and Hybrid
scenario. Each of the scenario is divided into three networks and each networks are
connected to routers. For storing the packets, a router uses the buffer and the size of
the buffer is set to 150000.The switch is used as layer 2 device. If a node on one
network wants to communicate with a node on another network, the packet is first sent
to layer 2 device. It first checks into the same network and then forwards to the router.
The router searches its routing table and sends the packets to the correct destination.
In our wireless scenario, every node in the network act as a router for forwarding the
packets. If a node is within the transmission range, node directly sends the packets,
but if it is out of the transmission range, node relies on the intermediate node for
forwarding the packets. The omni-directional antenna model is used due to the fact
that it works in all directions. Their radiation cone is 360 degrees in all directions.
Simulation is carried out in 50 nodes using CBR as traffic. A number of packets sent
by each node are 7500 with the size of 512 bytes.
In mixed scenario consists of a wireless and a wired domain. The simulation was
performed with 30 wireless nodes and 20 wired nodes. For our hybrid network
environment, they have an access point located at the center of the simulation area.
Every communication between wired and wireless nodes goes through the access
point. The station association type is dynamic. The access point is connected to the hub
(layer 2 device). If a node on wired network wants to send the packet to the wireless
node, the packet is first sent to the access point. With the use of ad hoc routing
protocol, the access point sends the packet to its correct destination. Similarly, the
packets from wireless nodes send the packets towards their assigned access points and
then the access point sends it to the wired domain.
They have evaluated the performance of different routing protocols for IPv4 and IPv6
over wired, wireless and the hybrid network. Some reasons for packet loss that they
observed that the size of the buffer, radio range, router load. From the results it has
been observed that out of all protocols the performance of AODV (IPv4) is best. It has
the maximum throughput and packet delivery ratio with minimum delay and jitter.
The paper compares different routing protocols in terms of throughput, jitter, end-to-
end delay and PDR which helps in designing the new protocol that can perform better.
In the future, they want to extend our work to test routing protocols with different
packet sizes and used the header compression technique to reduce the size of Ipv6
header for better performance
27](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-40-320.jpg)
![5) Study – 5 : Different Routing Protocols in IPv4 and IPv6 Networks on the basis
of Packet Sizes
A research alike similar to our project entitled “Performance Evaluation of Different
Routing Protocols in IPv4 and IPv6 Networks on the basis of Packet Sizes” [53] where
the performance is evaluated for different routing protocols like RIP, RIPng, OSPFv2
and OSPFv3 for IPv4 and IPv6 networks over Mobile Adhoc Networks. Simulations
are carried out on Exata Cyber 1.1 Simulator. The performance of networks is
measured on the basis of following parameters: throughput, end-to-end delay, jitter
and packet delivery ratio with varying packet sizes of 256, 512, 1024 and 2058 bytes.
Thus they use the Simulator named as Exata Cyber 1.1 where there are 100 of nodes in
the network and the traffic rate is of 1 packet per seconds and the simulation is done
for 100 seconds in wireless channel.
From the results it has been observed that as the packet sizes increases the overall
performance of the network increases. Due to small size of packet the number of
packets increased on the source node whereas as the of packet increases the number of
packets decreased and the control overheads also decreases. Out of the four protocols
the performance of RIPng is best among all the protocols. It is having the maximum
throughput and packet delivery ratio with minimum delay and jitter. OSPF for IPv4
networks is not performing well in this case. In future they will evaluate all these
protocols on wired and infrastructure based networks as well as also want to test BGP
protocol over such networks.
2.6 Development of Conceptual Framework of the study
So as we review through our related works mentioned above we assumed that the
Performance of Ipv6 networks is obviously better than IPv4 network using any types of
routing protocols in any operating system. This research we too tends to test and verify the
same condition which we have assumed. Since in the review of our related works the
performance analysis is done on the basis of throughput, delays, jitter, bandwidth and so on
and different types of simulating softwares are used too. But in our condition we tends to
analyze the performance of IPv4 and IPv6 networks on the basis of Packet Delay.
Here as we have mentioned above that there exists two types of Packet delays i.e. One-way
delay and Round trip time delay. Not only this the term gets confused with the term jitter and
latency. If we tends to find the instantaneous packet variation in one way delay then it is called
jitter where as if we only analyze the variation in times of packets to reach destination in one-
way then it is called Latency. So in our project we will be using the round trip time of the
packets i.e. the total time taken by the packets to reach to destination and came back.
First of all we will design a simple networks with IPv4 and IPv6 Protocols implied as
individually as well as in dual stack. The designed networks will be configured with OSPF
routing protocol and ICMP with used as primary form of packet. And we will be pinging the
destination and plotting the individual RTT time of each packets with versus to time(in
milliseconds) showing the fluctuation. We will vary the size of packets as 512 bytes, 1024 bytes
and 2048 bytes where the number of packets that are used will be always constant in each
condition. Not only this we too will too plot the minimum, average, maximum RTT and
Mean Deviation of the total packets and finally comparing our results and drawing out the
28](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-41-320.jpg)
![REFERENCES
[1] Sailan, Hassan, and Patel, “A comparative review of IPv4 and IPv6 for research test bed,”
in 2009 International Conference on Electrical Engineering and Informatics, Aug. 2009.
[2] Govil, Govil, Kaur, and Kaur, “An examination of IPv4 and IPv6 networks : Constraints
and various transition mechanisms,” in Southeastcon, 2008. IEEE International
Conference on Electrical Engineering and Informatics, April. 2008.
[3] T. Dunn, “The IPv6 Transition,” in IEEE Internet Computing, Vol.6, No.3, pp.11-13,
May/June 2002.
[4] “What is a Computer Network? - Types & Definition - Video & Lesson Transcript,”
Study.com. [Online]. Available: http://study.com/academy/lesson/what-is-a-computer-
network-types-definition-quiz.html.
[5] “IP (Internet Protocol) Definition.” [Online]. Available:
https://techterms.com/definition/ip.
[6] “IPv4 Definition.” [Online]. Available: https://techterms.com/definition/ipv4..
[7] “What is Internet Protocol Version 6 (IPv6)? - Definition from Techopedia,”
Techopedia.com. [Online]. Available:
https://www.techopedia.com/definition/5368/internet-protocol-version-6-ipv6.
[8] “OSPFv2.” [Online]. Available: https://www.ietf.org/rfc/rfc2328.txt. .
[9] “Quality of Service (QoS) - Cisco.” [Online]. Available:
https://www.cisco.com/c/en/us/products/ios-nx-os-software/quality-of-service-
qos/index.html.
[10] “What is IP Packet Delay Variation (IPDV), also called ‘jitter’?,” RIPE Network
Coordination Centre. [Online]. Available: https://www.ripe.net/analyse/archived-
projects/ttm/test-traffic-measurements/what-is-ip-packet-delay-variation-ipdv-also-
called-jitter.
[11] N. Unuth, “The Internet Protocol (IP) Explained,” Lifewire. [Online]. Available:
https://www.lifewire.com/internet-protocol-explained-3426713.
[12] J. Postel, “Internet Protocol.” [Online]. Available:
https://tools.ietf.org/html/rfc791#page-9.
[13] “Iv4P Packet Header.” [Online]. Available:
http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.html.
[14] “Understanding IPv4 Addressing - Technical Documentation - Support - Juniper
Networks.” [Online]. Available:
https://www.juniper.net/documentation/en_US/junos/topics/concept/interface-security-
logical-property-ipv4-addressing-understanding.html.
59](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-72-320.jpg)
![[15] “Types of Routing Protocols (3.1.4) > Cisco Networking Academy’s Introduction to
Routing Dynamically.” [Online]. Available:
http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=7.
[16] “Classless Vs Classful - 24528 - The Cisco Learning Network.” [Online]. Available:
https://learningnetwork.cisco.com/docs/DOC-24528.
[17] “Classful vs Classless Routing Protocols | NetworkLessons.com.” [Online]. Available:
https://networklessons.com/cisco/ccna-routing-switching-icnd1-100-105/classful-vs-
classless-routing-protocols/.
[18] “What is VLSM ? Explained with Examples.” [Online]. Available: http://www.orbit-
computer-solutions.com/variable-length-subnet-mask-vlsm/.
[19] “Ipv6 RFC.” [Online]. Available: https://www.ietf.org/rfc/rfc2460.txt.
[20] “IPv6 Extension Headers Review and Considerations [IP Version 6 (IPv6)],”
Cisco. [Online]. Available:
http://www.cisco.com/en/US/technologies/tk648/tk872/technologies_white_paper0900aec
d8054d37d.html.
[21] “IPv6 Addressing,” IPv6.com, 22-Apr-2006. .
[22] R. M. Hinden and S. E. Deering, “IP Version 6 Addressing Architecture.” [Online].
Available: https://tools.ietf.org/html/rfc4291.
[23] T. Narten, S. Thomson, and T. Jinmei, “IPv6 Stateless Address Autoconfiguration.”
[Online]. Available: https://tools.ietf.org/html/rfc4862#section-5.5.1.
[24] “Advantages of IPv6 | IPv6 Now.” [Online]. Available:
http://ipv6now.com.au/primers/IPv6Advantages.php.
[25] “Routing protocols.” [Online]. Available: http://study-ccna.com/routing-protocols/.
[26] J. Hawkinson and T. Bates, “Guidelines for creation, selection, and registration of an
Autonomous System (AS).” [Online]. Available: https://tools.ietf.org/html/rfc1930.
[27] “What is IGP (Interior Gateway Protocol)? - Definition from WhatIs.com,”
SearchSecurity. [Online]. Available: http://searchsecurity.techtarget.com/definition/IGP.
[28] “Types of Distance Vector Routing Protocols (3.2.2) > Cisco Networking Academy’s
Introduction to Routing Dynamically.” [Online]. Available:
http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=9.
[29] “Link State Routing Protocols > Dynamic Routing Protocols.” [Online]. Available:
http://www.ciscopress.com/articles/article.asp?p=24090&seqNum=4.
[30] “What is Exterior Gateway Protocol (EGP)? - Definition from WhatIs.com.” [Online].
Available: http://whatis.techtarget.com/definition/Exterior-Gateway-Protocol-EGP.
[31] A. Networks, “Open Shortest Path First OSPF Protocol Explained,” Auvik Networks,
04-Nov-2014. [Online]. Available: https://www.auvik.com/media/blog/ospf-protocol-
explained/.
[32] “OSPF (Open Shortest Path First) Definition.” [Online]. Available:
https://techterms.com/definition/ospf.
60](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-73-320.jpg)
![[33] I. Price-Evans, “What is Open Shortest Path First (OSPF)?” [Online]. Available:
https://www.metaswitch.com/resources/what-is-open-shortest-path-first-ospf.
[34] “IP Routing: OSPF Configuration Guide, Cisco IOS Release 12.4T - Configuring OSPF
[Cisco IOS Software Releases 12.4 T],” Cisco. [Online]. Available:
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_ospf/configuration/12-4t/iro-
12-4t-book/iro-cfg.html.
[35] “What Are OSPF Areas and Virtual Links?,” Cisco. [Online]. Available:
https://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13703-
8.html.
[36] “OSPFv2 vs OSPFv3 | NetworkLessons.com.” [Online]. Available:
https://networklessons.com/ipv6/ospfv2-vs-ospfv3/.
[37] “Internet Control Message Protocol (ICMP).” [Online]. Available:
http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.html.
[38] J. Postel, “Internet Control Message Protocol.” [Online]. Available:
https://tools.ietf.org/html/rfc792.
[39] J. Postel, “Internet Control Message Protocol.” [Online]. Available:
https://tools.ietf.org/html/rfc792.
[40] A. Conta and M. Gupta, “Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification.” [Online]. Available:
https://tools.ietf.org/html/rfc4443.
[41] “ICMPv6 Functions, ICMPv6 Header Packet Format and Types of ICMPv6 messages.”
[Online]. Available: http://www.omnisecu.com/tcpip/ipv6/icmpv6-functions-icmpv6-
packet-format-and-icmpv6-message-types.php.
[42] “Quality of Service (QoS),” Cisco. [Online]. Available:
https://www.cisco.com/c/en/us/products/ios-nx-os-software/quality-of-service-
qos/index.html.
[43] “Quality of Service Networking - DocWiki.” [Online]. Available:
http://docwiki.cisco.com/wiki/Quality_of_Service_Networking.
[44] “The Basics Of QoS,” Network Computing, 15-Aug-2016. [Online]. Available:
http://www.networkcomputing.com/networking/basics-qos/402199215.
[45] “Quality of Service (QOS).” [Online]. Available:
http://ecomputernotes.com/computernetworkingnotes/communication-networks/quality-
of-service.
[46] “What is latency? - Definition from WhatIs.com,” WhatIs.com. [Online]. Available:
http://whatis.techtarget.com/definition/latency.
[47] NerdsSupport, “What exactly is a packet delay?,” Nerds Support, 07-Nov-2013. [Online].
Available: https://nerdssupport.com/blog/what-exactly-is-a-packet-delay/.
[48] “What is a Dual Stack Network? - Definition from Techopedia.” [Online]. Available:
https://www.techopedia.com/definition/19025/dual-stack-network.
61](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-74-320.jpg)
![[49] Paula Raymond Lutui, “Performance Analysis of IPv4 vs. IPv6 on various Operating
Systems using Jumbo Frames” in 2012 International Conference on Electrical
Engineering and Informatics, Aug. 2012.
[50] Sotharith Tauch, “Performance evaluation of IP version 4 and IP version 6 transition
mechanisms on various operating systems” in 2010 International Conference on
Electrical Engineering and Informatics, April. 2010.
[51] Yuk-Nam Law, Man-Chiu Lai, Wee Lum Tan and Wing Cheong Lau, “Empirical
Performance of IPv6 vs. IPv4 under a Dual-Stack Environment” in 2012 International
Conference on Electrical Engineering and Informatics, Aug. 2012.
[52] Sonal Telang Chandel, Sanjay Sharma, “Performance Evaluation of IPv4 and IPv6
Routing Protocols on Wired, Wireless and Hybrid Networks” in International Journal of
Computer Networks and Applications (IJCNA), Volume 3, Issue 3, May – June (2016)
[53] Dipti Chauhan, Sanjay Sharma, “Performance Evaluation of Different Routing
Protocols in IPv4 and IPv6 Networks on the basis of Packet Sizes ” in International
Conference on Information and Communication Technologies (ICICT), May – June
(2016)
62](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-75-320.jpg)
![!
!control-plane
!
!
!
Mgcp behavior rsip-range tgcp-only
Mgcp behavior comedia-role none
Mgcp behavior comedia-check-media-src disable
Mgcp behavior comedia-sdp-force disable
!
Mgcp profile default
!
!
!
!
!
Line con 0
No modem enable
Line aux 0
Line vty 0 4
Login
Transport input all
!
Scheduler allocate 20000 1000
!
End
Python Program For Plotting Each Packets RTT forming a line Graph
import pandas as pd
import csv
import matplotlib.pyplot as plt
plt.style.use('ggplot')
df = pd.read_csv('IP_Comparison_2048_bytes.csv')
a = df['Sequence of Packets']
b = df['IPv4 Packets (Dual Stack)']
c = df['IPv6 Packets (Dual Stack)']
d = df['IPv4 Packets (Single)']
e = df['IPv6 Packets (Single)']
plt.title('IPv4 & IPv6 Fluctuation Data (2048 Byte Packets)',
fontsize=14)
71](https://image.slidesharecdn.com/finalprojectreport-180220045901/85/Analysis-of-Packet-on-the-basis-of-Delay-on-IPv6-and-IPv4-Networks-in-Open-Short-Path-First-Routing-Protocol-84-320.jpg)
Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol
- 1. Lumbini ICT Campus Tribhuvan University Gaindakot -2 , Nawalparasi, Nepal Institute of Science and Technology (IOST) Final year project on “Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol ” [CSC – 404] A final year project report submitted in the partial fulfillment of the requirements for the degree of Bachelors of Science in Computer Science and Information Technology awarded by Tribhuvan University Under the supervision of Er. Sulav Adhikari Co-ordinator, Lumbini ICT Campus Submitted by : Kaushik Raj Panta (T.U Roll no. 3865) Rabin Ghimire (T.U Roll no.3874) Bishnu Sapkota (T.U Roll no.3859) Sudip Kafle (T.U Roll no.3879) Submitted to Lumbini ICT Campus, Department of Computer Science and Information Technology Gaindakot – 2, Nawalparasi September 11, 2017
- 2. Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol [CSC – 404] A final year project submitted in partial fulfillment of the requirement for the degree of Bachelor of Science in Computer Science and Information Technology awarded by Tribhuvan University Submitted by : Kaushik Raj Panta (T.U Roll no. 3865) Rabin Ghimire (T.U Roll no. 3874) Bishnu Sapkota (T.U Roll no. 3859) Sudip Kafle (T.U Roll no. 3879) Submitted to Lumbini ICT Campus, Department of Computer Science and Information Technology Gaindakot – 2, Nawalparasi September 11, 2017
- 3. Lumbini ICT Campus Tribhuvan University SUPERVISOR RECOMMENDATION I hereby recommend that this project prepared under my supervision by Kaushik Raj Panta, Bishnu Sapkota, Rabin Ghimire and Sudeep Kafle entitled “Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol” in partial fulfillment of the requirements for the degree of Bachelors of Science in Computer Science and Information Technology be processed for the evaluation. ……………………….. Er. Sulav Adhikari Co-ordinator, Lumbini ICT Campus I
- 4. ACKNOWLEDGEMENT The success and final outcome of this project required a lot of guidance and assistance from many individuals and we are very fortunate to have got this all along the duration of this project. We would like to extend our sincere thanks and gratitude to our respected supervisor and Co-ordinator of Lumbini ICT Campus, Er. Sulav Adhikari, Department of Computer Science and Information Technology for his valuable suggestions, guidance, encouragement and inspirations that assisted us in completing this work. His useful recommendations and co- operative behavior are sincerely acknowledged. An honorable mention also goes to Er Kumar Pudasaini, for his understanding and support during our project. He was highly valuable to us in completing the project work. Furthermore A big thanks goes to Mr Rahul Sakya. We are indebted to them for making their valuable time available to us, to answer our questions and queries. Nevertheless a big thanks go to the family of Lumbini ICT Campus and all of my friends for guiding us through out the project and helping in our project directly and indirectly. Kaushik Raj Panta Rabin Ghimire Bishnu Sapkota Sudeep Kafle II
- 5. ABSTRACT In a packet network, the term packet delay characterizes as the difference in end-to-end one- way delay between selected packets in a flow with any lost packets being ignored. The effect is sometimes referred to as jitter, although the definition is an imprecise fit. The delay is specified from the start of the packet being transmitted at the source to the start of the packet being received at the destination. Analysis of packet delay in both protocol IPv4 and IPv6 is essential to measure network performance. This project entitled “Analysis of Packet on the basis of Delay on IPv6 and IPv4 Networks in Open Short Path First Routing Protocol” intends to analyze the packet delay in both protocol IPv4 and IPv6 under the same condition and find out the fact that which one is better in term of packet delay parameter of network performance. Due to the insufficient IPv4 addresses and other issues, the world should migrate to IPv6 in near future. So, measuring the network parameter is necessary. OSPF (Open Shortest Path First) is a routing protocol for Internet Protocol networks. It uses a link state routing algorithm and falls into the group of interior gateway protocols, operating within a single autonomous system. It is defined as OSPF Version 2 in IPv4 and the updates for IPv6 are specified as OSPF Version 3. This project deals with the techniques of measure and analyze the packet delay. As, the number of Internet users growing exponentially, it is really necessary to reduce the packet delay in every possible way to improve network performance. Keywords: Packet delay, IPv4, IPv6, OSPF, Dual Stack. III
- 6. TABLE OF CONTENTS SUPERVISOR RECOMMENDATION………………………………………………………….I ACKNOWLEDGEMENT………………………………………………………………………..II ABSTRACT…………………………………………………………………………………….....III LIST OF FIGURES……………………………………………………………………………..VII LIST OF TABLES………………………….…………………………………………………….IX LIST OF ABBREVIATIONS……………………………………………………………………..X CHAPTER – 1 : INTRODUCTION.....................................................................................................1 1.1 Background of Project....................................................................................................................1 1.2 Statement of the Problem...............................................................................................................2 1.3 Project Question.............................................................................................................................3 1.4 Scope of the Project........................................................................................................................3 1.5 Report Structure..............................................................................................................................3 CHAPTER – 2 : LITERATURE REVIEW..........................................................................................5 2.1 Introduction....................................................................................................................................5 2.2 Related Technologies......................................................................................................................5 2.2.1 Internet Protocol.....................................................................................................................5 2.2.2 Internet Protocol version 4......................................................................................................6 2.2.2.1 Introduction.....................................................................................................................6 2.2.2.2 IPv4 Packet Header.........................................................................................................6 2.2.2.3 IPv4 Addressing Scheme................................................................................................7 2.2.2.4 Classfull and Classless IPv4 Protocol.............................................................................7 2.2.2.5 Problem with IPv4..........................................................................................................8 2.2.3 Internet Protocol version 6......................................................................................................9 2.2.3.1 Introduction.....................................................................................................................9 2.2.3.2 IPv6 Packet Header.........................................................................................................9 2.2.3.3 IPv6 Addressing Format and Scheme...........................................................................10 2.2.3.4 The Advantages of IPv6................................................................................................10 2.2.4 Routing Protocols.................................................................................................................12 2.2.4.1 Autonomous System.....................................................................................................12 2.2.4.2 Interior Routing Protocol..............................................................................................13 2.2.4.2.1 Distance Vector Routing Protocol.........................................................................13 2.2.4.2.2 Link State Routing Protocol..................................................................................13 2.2.4.2.3 Hybrid Routing Protocol.......................................................................................14 2.2.4.3 Exterior Routing Protocol.............................................................................................14 2.2.5 Open Short Path First............................................................................................................14 2.2.5.1 OSPF Interfaces............................................................................................................15 2.2.5.2 OSPF Areas...................................................................................................................15 2.2.5.3 OSPFv3 vs OSPFv2......................................................................................................16 2.2.5.4 OSPFv2 and OSPFv3 Header Comparison...................................................................16 2.2.5.5 Hello Packet Comparison..............................................................................................16 2.2.6 Internet Control Message Protocol.......................................................................................17 2.2.6.1 ICMPv4.........................................................................................................................17 2.2.6.2 ICMPv6.........................................................................................................................17 2.2.7 Quality of Service.................................................................................................................18 2.2.7.1 QOS Basic Architecture................................................................................................18 2.2.7.2 Qualities of QOS...........................................................................................................19 2.2.8 Latency..................................................................................................................................20 IV
- 7. 2.2.8.2 Latency testing..............................................................................................................21 2.2.8.3 Reducing latency...........................................................................................................21 2.2.9 Network Latency...................................................................................................................21 2.2.9.1 Types of Packet Delays.................................................................................................21 2.2.9.2 Types of Delays in Packet Switch Networks................................................................22 2.2.9.3 Cause of Packet Delays.................................................................................................22 2.2.9.4 Ways to reduce Reduce Packet Delays.........................................................................22 2.2.10 Dual Stack...........................................................................................................................23 2.2.10.1 Dual Stack Transition Mechanism..............................................................................24 2.3 Review of Conceptual Prospective of the study...........................................................................24 2.4 Related Literature Review............................................................................................................25 2.6 Development of Conceptual Framework of the study..................................................................28 CHAPTER – 3 : METHODOLOGY..................................................................................................30 3.1 Introduction..................................................................................................................................30 3.2 Hypothesis....................................................................................................................................30 3.3 Research Methods for study.........................................................................................................30 3.4 Data Collection Tools and Methods.............................................................................................31 CHAPTER – 4 : EXPERIMENTAL DESIGN...................................................................................32 4.1 Hardware Specifications...............................................................................................................32 4.2 Software Specifications................................................................................................................32 4.3 Network Design............................................................................................................................33 4.3.1 Virtual Network Design........................................................................................................33 4.3.2 Actual Network Design.........................................................................................................34 4.3.3 IP Addressing Scheme..........................................................................................................34 4.3.3.1 IPv4 Addressing............................................................................................................34 4.3.3.2 IPv6 addressing.............................................................................................................37 4.3.4 OSPF Configurations............................................................................................................37 4.3.4.1 OSPF Configuration for IPv4 Addresses......................................................................37 4.3.4.1 OSPF configuration for Ipv6 Addresses.......................................................................38 4.4 Testing..........................................................................................................................................40 4.4.1 Ping Testing..........................................................................................................................40 4.4.2 HTTP Server Testing............................................................................................................41 4.4.3 FTP Server Testing................................................................................................................42 4.4.4 E-Mail Testing......................................................................................................................43 4.4.4.1 E-Mail Testing over IPv4..............................................................................................43 4.4.4.2 E-Mail Testing over IPv6..............................................................................................44 4.5 Project Time line...........................................................................................................................46 4.6 Project Grant Chart.......................................................................................................................47 CHAPTER – 5 : DATA COLLECTION AND ANALYSIS...............................................................48 5.1 Data Collection Process................................................................................................................48 5.2 Plotting the RTT of each packet in each condition.......................................................................49 5.3 Graphing the total RTT of packet in each condition....................................................................51 CHAPTER – 6 : DISCUSSION.........................................................................................................55 6.1 Plotting the individual RTT of Packets.........................................................................................55 6.1.1 Variable Header Size.............................................................................................................55 6.1.2 Priority and Processing Delay...............................................................................................55 6.2 Plotting the average RTT of packets in dual stack and single stack mode...................................56 CHAPTER – 7 : CONCLUSION.......................................................................................................57 7.1 Limitations....................................................................................................................................57 7.2 Future Enhancement.....................................................................................................................58 V
- 8. REFERENCES...................................................................................................................................59 APPENDIX........................................................................................................................................63 Configuration of Router -1 at Side -1............................................................................................63 Configuration of Router – 2 of Side 2...........................................................................................65 Configuration of Main Router.......................................................................................................68 Building Configuration…..............................................................................................................68 Python Program For Plotting Each Packets RTT forming a line Graph........................................71 Python Program for Plotting Average RTT of Packets forming a Bar Graph....................72 VI
- 9. LIST OF FIGURES Figure-1: Packet header of IPv4 Figure-2: Quad-dotted IPv4 address representation Figure-3: Packet header of IPv6 Figure-4: Area system of OSPF Figure-5: OSPFv2 and OSPFv3 header comparison Figure-6: OSPFv2 and OSPFv3 hello packet comparison Figure-7: Header of ICMP version 4 Figure-8: Header of ICMP version 6 Figure-9: Basic architecture of QoS Figure-10: Virtual Network Design Figure-11: Actual Network Design Figure-12: Dividing network into side-1, side-2 and main-router Figure-13: Assigning IPV4 address Figure-14: Assigning IPV6 address Figure-15: OSPFv2 configuration Figure-16: OSPFv2 route Discovery Figure-17: OSPFv2 neighbor discovery Figure-18: OSPFv3 configuration Figure-19: OSPFv3 route Discovery Figure-20: OSPFv3 neighbor Discovery Figure-21: IPV4 communication between two sides Figure-22: IPV6 communication between two sides Figure-23: HTTP server test in IPv4 Figure-24: HTTP server test in IPv6 Figure-25: FTP server test in IPV4 Figure-26: FTP server test in IPV6 Figure-27: Email compose from admin to client in IPv4 Figure-28: Email sent result from admin to client in IPv4 Figure-29: Email reply result in client in IPv4 Figure-30: Email receive in client in IPv4 Figure-31: Email send in IPv6 from admin Figure-32: Send success from admin Figure-33: Email receive at client VII
- 10. Figure-34: Reply from user to admin Figure-35: User reply mail at admin Figure-36: Ping process information Figure-37: Plotting each individual packet RTT forming graph example Figure-38: Plotting total RTT of packet in each condition forming bar graph Figure-39: Overall project time line Figure-40: Project grant chart Figure–41 : Plotting Each individual Packet RTT forming graph at 512 Bytes Figure–42 : Plotting Each individual Packet RTT forming graph at 1024 Bytes Figure–43 : Plotting Each individual Packet RTT forming graph at 1024 Bytes Figure–44 : Plotting total RTT of Packets in Each Condition when 512 bytes Figure–45 : Plotting total RTT of Packets in Each Condition when 1024 bytes Figure–46 : Plotting total RTT of Packets in Each Condition when 2048 bytes VIII
- 11. LIST OF TABLES Table – 1 : Hardware Requirements Table – 2 : Plotting total RTT of Packets in Each Condition when 512 bytes Table – 2 : Plotting total RTT of Packets in Each Condition when 1024 bytes Table – 2 : Plotting total RTT of Packets in Each Condition when 2048 bytes Table – 5 : Difference in Total Average RTT in both Network i.e. Avg RTT of IPv6 – Avg RTT of IPv4 IX
- 12. LIST OF ABBREVIATIONS IP = Internet Protocol IPv4 = Internet Protocol version 4 IPv6 = Internet Protocol version 6 OSPF = Open Short Path First TCP/IP = Transmission Control Protocol / Internet Protocol VoIP = Voice over Internet Protocol IETF = Internet Engineering task Force NGTrans = Next Generation Transition TCP = Transmission Control Protocol UDP = User Datagram Protocol RTT = Round Trip Time IGP = Interior Gateway Protocol NAT = Network Address Translation LSR = Link State Routing CIDR = Classless Inter Domain Routing QoS = Quality of Service PDV = Packet Delay Variation DSCP = Differentiated Services Code Point ECN = Explicit Congestion Notification IGMP = Internet Group Message Protocol SAP = Service Access Point VLSM = Variable Length Subnet Mask RFC = Request For Comments RIPv1/RIPv2 = Routing Information Protocol version 1/ version 2 BGP = Border Gateway Protocol EIGRP = Enhanced Interior Gateway Routing Protocol IPSec = Internet Protocol Security TOS = Type of Service DHCP = Dynamic Host Configuration Protocol EGP = Exterior Gateway Protocol IXP = Internet Exchange Point X
- 13. CDN = Content Delivery Networks AS = Autonomous System ICMP = Internet Control Message Protocol CSV = Comma Separated Values NIC = Network Interface Card LTS = Long Term Support TEP = Tunnel End Point XI
- 14. CHAPTER – 1 : INTRODUCTION 1.1 Background of Project Internet Protocol is the standard protocol being used on the Internet which allows computers to be able to communicate in order to exchange information such as data, voice, and Video. IPv4 is the current Internet protocol that is widely used across the Internet, but in the near future, there exist issues like insufficient public Internet Protocol version 4 address space that does not allow the growth of the Internet. Nowadays, most of mobile devices are required to have an IP address to connect to the Internet which leads to high consumption of IP address. Internet Engineer Task Force has considered this issue and proposed a new version of Internet Protocol namely IPv6 . IPv6 is the solution to the massive growth of the Internet due to the size of the address spaces. IPv6 addressing contains 128 bits binary value that provide 2^128 addresses. In the near future the current IPv4 will slowly migrate to IPv6. Sailan, Hassan, and Patel state that “Currently IPv6 network penetration is still low but it is expected to grow, while IPv4 address pool is projected by Regional Internet Registry to be exhausted by the end of 2011”[1]. Migration from IPv4 to IPv6 is the the work done in single day because there exists some issues in both networks. During the migration period there will be compatibility and interoperability issues relating to IPv4 and IPv6 because IPv6 is not backward compatible with IPv4. Govil, Govil, Kaur, and Kaur states that “The transition between IPv4 Internet and IPv6 will be a long process as they are two completely separate protocols and it is impossible to switch the entire Internet over to IPv6 over night. IPv6 is not backward compatible with IPv4 and IPv4 hosts and routers will not be able to deal directly with IPv6 traffic and vice- versa” [2]. As IPv4 and IPv6 will co-exist for a long time, this requires the transition and inter-operation mechanisms. Migrating from IPv4 to IPv6 is a complicated task that cannot be done overnight. The size and complexity of the Internet cause this migration task to become enormously difficult and time consuming. Next Generation Transition proposed three main transition mechanisms that included dual stack, tunneling, and translation [3]. These solution allow IPv4 to be able to coexist with IPv6 during the migration period. A Computer Network is a collection of computers, servers, mainframes, network devices, peripherals, or other devices connected to one another to allow the sharing of data. An excellent example of a network is the Internet, which connects millions of people all over the world [4]. The IP is designed for use in interconnected systems of packet-switched computer communication networks. The Internet protocol provides for transmitting blocks of data called datagrams from sources to destinations, where sources and destinations are hosts identified by fixed length addresses. The Internet protocol also provides for fragmentation and reassembly of long datagrams [5]. IPv4 is the one of the core connectionless protocols of standards-based inter networking methods of Packet Switched Network which operates on a best effort delivery model i.e. it 1
- 15. does not guarantee delivery nor does it assure proper sequencing or avoidance of duplicate delivery. IPV4 uses 32-bit address scheme which limits the address space to 232 addresses represented by integer value written in the dot-decimal notation consisting of four octets expressed individually in decimal numbers and separated by periods [6]. IPv6 is an Internet Layer protocol for packet-switched inter networking and provides end-to- end datagram transmission across multiple IP networks, closely adhering to the design principles developed in the previous version of the protocol, IPv4. IPv6 uses a 128-bit address, theoretically allowing 2128, or approximately 3.4X1038 addresses. It simplifies aspects of address assignment, network renumbering, and router announcements when changing network connectivity providers. It simplifies processing of packets in routers by placing the responsibility for packet fragmentation into the end points [7]. OSPF is an IGP that follows LSR Algorithm for routing IP packets solely with in a single routing domain i.e. an Autonomous system. It gathers link state information from available routers and constructs a topology map of the network. OSPF is based on Dijkstra Algorithm for finding shortest path and supports IPv4 and IPv6 networks and supports the CIDR addressing model [8]. QoS is a set of technologies that work on a network to guarantee its ability to dependably run high-priority applications and traffic under limited network capacity. Achieving the required QoS by managing the delay, delay variation, bandwidth, and packet loss parameters on a network becomes the secret to a successful end-to-end business solution [9]. Packet Delay is the difference in end-to-end one-way delay between selected packets in a flow with any lost packets being ignored. The effect is sometimes referred to as jitter, although the definition is an imprecise fit. The Packet Delay is the difference between the one-way-delay of the selected packets [10]. The main target of this research is to study the performance between the IPv4 and IPv6 on the basis of Packet Delay when implemented on both Dual Stack and Single Stack Mode in OSPF routing Protocols. The result of this research will discuss later in this report. 1.2 Statement of the Problem Networking is an important factor in every sector in today’s world. All computers if linked to one another provide a lot of benefit such as file or resource sharing, flexibility and boosting of storage capacity. If networking is not done in any organization. First of all let us explore the problems in IPv4 and there are two main problems with IPv4. First of all, today, there are 7.3 billion people in the world. Half of them own a computer of some sort, and 6 billion have access to mobile phones. If we handed out just one IPv4 address to every person, we would be 3 billion IP addresses short. This makes reclaiming lost address space essentially pointless. Obviously, more addresses are needed for a modern Internet. The other problem with IPv4 is NAT. Overloaded NAT, one IP with multiple private IP’s behind it breaks quite a few applications and provides no additional security against Internet threats. This results in a cost increase with no counter-benefit. 2
- 16. IPv4 lacks of efficient routing because each and every IPv4 network prefix might be different inside the single organization too due to which routing gets difficult. Not only this in an IPv4 network too fragmentation is handled by the router not by the source devices. IPv4 contains an IP - level checksum, so the checksum is calculated at every router hop. But with most link-layer technologies already containing checksum and error-control capabilities, and most transport layers having a checksum that enables error detection where the routers spent most of time checking packet integrity before moving the packets. Regarding the above mentioned problems, if we migrate to IPv6 network we can some how eradicate maximum of the problems that are arising in IPv4 networks currently. 1.3 Project Question Before the starting of the project, we had a meet up and discussed about the real scenario of project and the questions that can arises throughout the completion of our project. By the end of that meeting we had concluded the following as Project Questions: 1) Will the IPv6 gives better performance on the basis of packet delay as compared to IPv4 in same condition? 2) Which mode will give better performance, Dual Stack or Single Stack? 3) Is the parameter Packet Delay is sufficient for measuring the performance of the network? 4) Why should we choose IPv6 over IPv4? 1.4 Scope of the Project Project scope is the part of project planning that involves determining and documenting a list of specific project goals, deliverables, features, functions, tasks, deadlines, and ultimately costs. In other words, it is what needs to be achieved and the work that must be done to deliver a project. The main purpose of the scope definition is to clearly describe the boundaries of your project. The Scopes of our project are as follows : 1) To experiment the performance of IPv4 and IPv6 networks individually and in Dual Stack mode on the basis of Packet Delay. 2) To analyze the performance of IPv4 and IPv6 networks individually and in Dual Stack mode on the basis of Packet Delay. 3) To encourage for using IPv6 over IPv4. 1.5 Report Structure The overview of our project is given below : Chapter 1 : Introduction 3
- 17. In this chapter we basically introduces background of our project, its significance as well as its scope including the definition of key terms that we are using in our project. Chapter – 2 : Literature Review In this chapter we review about conceptual perspective of our study, related documents and selected cases and best practices. Chapter-3 : Methodology In this chapter we introduces Hypothesis of our study, Research Methods, data collection tools and methods and how to process it. Chapter – 4 : Experimental Designated In this chapter we discuss about Hardware and Software Specification of our network, Virtual and Actual Network Design, Ip Addressing Schemes, OSPF configuration , system testing and Data Collection Process. This chapter also includes the Gantt Chart of our project. Chapter – 5 : Data Collection and Analysis In this chapter we present the data that we gathered for analysis as well describe it. Presentation of data will be based on plotting the individual RTT of each packets and Plotting the total RTT of packets in each condition. Chapter – 6 : Discussion In this chapter we discuss about the findings from the results of the experiments of this research. Chapter – 7 : Conclusion In this chapter we summarize and conclude our results and test the acceptance and rejection of our hypothesis. Here we too focus on the improvement of Network Performance as well as provide the suggestions for the future enhancements. 4
- 18. CHAPTER – 2 : LITERATURE REVIEW 2.1 Introduction A literature review is a text of a scholarly paper, which includes the current knowledge including substantive findings, as well as theoretical and methodological contributions to a particular topic. Literature reviews are secondary sources, and do not report new or original experimental work. Most often associated with academic-oriented literature, such reviews are found in academic journals, and are not to be confused with book reviews that may also appear in the same publication. Literature reviews are a basis for research in nearly every academic field. A narrow-scope literature review may be included as part of a peer-reviewed journal article presenting new research, serving to situate the current study within the body of the relevant literature and to provide context for the reader. In such a case, the review usually precedes the methodology and results sections of the work. 2.2 Related Technologies 2.2.1 Internet Protocol The IP is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries. Its routing function enables inter networking, and essentially establishes the Internet. The Internet protocol provides for transmitting blocks of data called datagrams from sources to destinations, where sources and destinations are hosts identified by fixed length addresses. The Internet protocol also provides for fragmentation and reassembly of long datagrams. The Internet protocol is specifically limited in scope to provide the functions necessary to deliver a package of bits from a source to a destination over an interconnected system of networks. The Internet protocol can capitalize on the services of its supporting networks to provide various types and qualities of service . IP usually works in combination with the TCP, which establishes a virtual connection between a source and a destination or with UDP. As an analogy, UDP can be thought of as sending a postcard via the postal system. It permits a user to address a packet and drop it in the system/network whereby the user does not have direct contact with the receiver of the message packet. TCP/IP, on the other hand, is more like a bidirectional phone call, where a connection is established the connection between the two hosts so that the two hosts can communicate between themselves for some time with each party acknowledging what the other party is sending [11]. The two versions of Internet Protocol in use are IPv4 and IPv6. IPv6 was designed when it became apparent that the number of allocated IPv4 addresses would eventually run out. Protocol developers IPv6 as a replacement IPv4 and added many more added security features beyond solely adding exponentially more addresses than IPv4. IPv4 and IPv6 are not interpolatable and IPv6 will not be immediately replicable by IPv6. While many transition mechanisms exist, host based solution where end hosts are simultaneously configured with both IPv4 and IPv6 is the preferred configuration. This “dual stack solution” allows for a 5
- 19. single change on each host and provider shortcomings in terms of transit can be addressed separately on upstream devices. 2.2.2 Internet Protocol version 4 2.2.2.1 Introduction IPv4 is the one of the core connectionless protocols of standards-based inter networking methods of Packet Switched Network which operates on a best effort delivery model i.e it does not guarantee delivery nor does it assure proper sequencing or avoidance of duplicate delivery. IPV4 uses 32-bit address scheme which limits the address space to 232 addresses represented by integer value written in the dot-decimal notation consisting of four octets expressed individually in decimal numbers and separated by periods. That means that each device including cell phones, office phones, game consoles and computers each need their own IP address in order to connect and communicate over the Internet. With the ever-growing number of devices that need to connect to the Internet, it is no surprise that the amount of available IPv4 addresses will soon be exhausted. Already, there are more devices connected than there are routable IPv4 addresses. This is possible through a technology known as NAT which allows multiple machines to appear as a single routable address. This comes with the cost of the complexity involved in supporting devices deployed behind a NAT device [12]. 2.2.2.2 IPv4 Packet Header The IP uses a Datagram service to transfer packets of data between end systems using routers. The IPv4 packet header consists of 20 bytes of data. An option exists within the header that allows further optional bytes to be added, but this is not normally used [13]. The full header is shown below: Figure – 1 : Packet Header of IPv4 The header fields are discussed below: • Version always set to the value 4 in the current version of IP • IP Header Length number of 32 -bit words forming the header, usually five • Differentiated Services Code Point (DSCP) is 6 bit field, which reflect the Quality of Service needs of an application to the network. 6
- 20. • Explicit Congestion Notification (ECN) Field is 2 bits which indicates the transport flow. • Size of Datagram is in bytes, which gives the combined length of the header and the data • Identification is 16-bit number which together with the source address uniquely identifies this packet and used during reassembly of fragmented datagrams. • Flags, a sequence of three flags used to control whether routers are allowed to fragment a packet, and to indicate the parts of a packet to the receiver. • Fragmentation Offset is a byte count from the start of the original sent packet, set by any router which performs IP router fragmentation. • Time To Live is Number of hops /links which the packet may be routed over. • Protocol is a SAP which indicates the type of transport packet being carried . • Header Checksum is used to detect processing errors introduced into the packet inside a router or bridge. • Source Address indicates the IP address of the original sender of the packet. • Destination Address indicates the IP address of the final destination of the packet. • Options is used when the IP header length will be greater than five 32-bit words to indicate the size of the options field/ 2.2.2.3 IPv4 Addressing Scheme IPv4 addresses may be represented in any notation expressing a 32-bit integer value. They are most often written in the dot-decimal notation, which consists of four octets of the address expressed individually in decimal numbers and separated by periods. The CIDR notation standard combines the address with its routing prefix in a compact format, in which the address is followed by a slash character (/) and the count of consecutive 1 bits in the routing prefix (subnet mask) [14]. Figure – 2 : Quad-dotted IPv4 address representation 2.2.2.4 Classfull and Classless IPv4 Protocol A classfull network is a network addressing architecture where the method divides the address space for IPv4 into five address classes by address range. Classes A, B, C are networks of three different network sizes, i.e. number of hosts for unicast addresses. Class D is for multicast. 7
- 21. The class E address range is reserved for future or experimental purposes. Classfull addressing divides an IP address into the Network and Host portions along octet boundaries [15]. Classless addressing uses a variable number of bits for the network and host portions of the address. Classless addressing treats the IP address as a 32 bit stream of ones and zeros, where the boundary between network and host portions can fall anywhere between bit 0 and bit 31. The network portion of an IP address is determined by how many 1's are in the subnet mask. Again, this can be a variable number of bits, and although it can fall on an octet boundary, it does not necessarily need to. A subnet mask is used locally on each host connected to a network, and masks are never carried in IPv4 datagrams. All hosts on the same network are configured with the same mask, and share the same pattern of network bits. The host portion of each host's IP address will be unique. It allows us to use variable length subnet mask so also known as VLSM. [16] [17]. VLSM enables you to have more than one mask for a given class of address, albeit a class A, B, or C network number. VLSM, allows you to apply different subnet masks to the same class address space Classfull protocols, such as RIPv1 and IGRP, do not support VLSM. To deploy VLSM requires a routing protocol that is classless - BGP, EIGRP, OSPF, or RIPv2, for instance[18]. 2.2.2.5 Problem with IPv4 The problems with IPv4 are given below : 1) Scarcity of Address : The IPv4 addressing system uses 32-bit address space. This 32-bit address space is further classified to usable A, B, and C classes. 32-bit address space allows for 4,294,967,296 IPv4 addresses, but the previous and current IPv4 address allocation practices limit the number of available public IPv4 addresses. Because scarcity of IPv4 addresses, many organizations implemented NAT to map multiple private IPv4 addresses to a single public IPv4 address. By using NAT we can map many internal private IPV4 addresses to a public IPv4 address, which helped in conserving IPv4 addresses. But NAT also have many limitations. 2) Security Related issues: IPSec is a protocol suit which enables network security by protecting the data being sent from being viewed or modified. IPSec provides security for IPv4 packets, but IPSec is not built-in and optional. Many IPSec implementations are proprietary. 3) Quality of Service: QoS is available in IPv4 and it relies on the 8 bits of the IPv4 TOS field and the identification of the payload. IPv4 TOS field has limited functionality and payload identification (uses a TCP or UDP port) is not possible when the IPv4 datagram packet payload is encrypted. 4) Address related configuration issue: Networks and also Internet is expanding and many new computers and devices are using IP. The configuration of IP addresses (static or dynamic) should be simple. 8
- 22. 2.2.3 Internet Protocol version 6 2.2.3.1 Introduction IPv6 is an Internet Layer protocol for packet-switched inter networking and provides end-to- end datagram transmission across multiple IP networks. IPv6 uses a 128-bit address, theoretically allowing 2128, or approximately 3.4X1038 addresses.It simplifies aspects of address assignment, network renumbering, and router announcements when changing network connectivity providers. It simplifies processing of packets in routers by placing the responsibility for packet fragmentation into the end points [19]. 2.2.3.2 IPv6 Packet Header The fixed header of an IPv6 packet consists of its first 40 octets (320 bits). It has the following format [20]: Figure – 3 : Packet Header of IPv6 The header fields are discussed below: • Source address - The 128-bit source address field contains the IPv6 address of the originating node of the packet. • Destination address - The 128-bit contains the destination address of the recipient node of the IPv6 packet. • Version/IP version - The 4-bit version field contains the number 6. It indicates the version of the IPv6 protocol. • Packet priority/Traffic class - The 8-bit Priority field in the IPv6 header can assume different values to enable the source node to differentiate between the packets generated by it by associating different delivery priorities to them. • Flow Label/QoS management - The 20-bit flow label field in the IPv6 header can be used by a source to label a set of packets belonging to the same flow. • Payload length - The 16-bit payload length field contains the length of the data field in octets/bits following the IPv6 packet header. 9
- 23. • Next Header - The 8-bit Next Header field identifies the type of header immediately following the IPv6 header and located at the beginning of the data field (payload) of the IPv6 packet. • Time To Live (TTL)/Hop Limit (8 bits) - The 8-bit Hop Limit field is decremented by one, by each node (typically a router) that forwards a packet. 2.2.3.3 IPv6 Addressing Format and Scheme An IPv6 address is represented as eight groups of four hexadecimal digits, each group representing 16 bits (two octets, a group sometimes also called a hextet). The groups are separated by colons (:). An example of an IPv6 address is: 2001:0db8:85a3:0000:0000:8a2e:0370:7334 The hexadecimal digits are case-insensitive, but IETF recommendations suggest the use of lower case letters. The full representation of eight 4-digit groups may be simplified by several techniques, eliminating parts of the representation [21] [22]. Leading zeros in a group may be omitted, but each group must retain at least one hexadecimal digit. Thus, the example address may be written as [23]: 2001:db8:85a3:0:0:8a2e:370:7334 One or more consecutive groups of zero value may be replaced with a single empty group using two consecutive colons (::), but the substitution may only be applied once in the address, because multiple occurrences would create an ambiguous representation. Thus, the example address can be further simplified: 2001:db8:85a3::8a2e:370:7334 IPv6 addresses are classified by the primary addressing and routing methodologies common in networking: unicast addressing, anycast addressing, and multicast addressing. • A unicast address identifies a single network interface. The Internet Protocol delivers packets sent to a unicast address to that specific interface. • An anycast address is assigned to a group of interfaces, usually belonging to different nodes. A packet sent to an anycast address is delivered to just one of the member interfaces, typically the nearest host, according to the routing protocol's definition of distance. • A multicast address is also used by multiple hosts, which acquire the multicast address destination by participating in the multicast distribution protocol among the network routers. A packet that is sent to a multicast address is delivered to all interfaces that have joined the corresponding multicast group. 2.2.3.4 The Advantages of IPv6 The benefits of the Internet are drawn directly from the platform of interoperability created by use of the Internet Protocol, leading to a large "network effect". That is, the benefits to a company from the Internet arise not just by the extent to which the company itself uses the 10
- 24. Internet, but far more from the extent to which others - suppliers, customers and individuals - also use the Internet. Because IPv6 will greatly increase the size and range of devices connected to the Internet, the benefit of the network effect will increase accordingly. The World Wide Web and other Internet applications currently use version 4 of the Internet Protocol - IPv4. IPv6 was developed by the Internet Engineering Task Force to deal with a looming shortage of addresses under IPv4. Since then, there have been numerous technical fixes to shore up IPv4 and postpone the need for a move to IPv6, as well as debate on whether IPv6 would even be required. That debate is now agreed to be over. The free IPv4 address space was exhausted between 2011 and 2015. In practice, the only sensible option for those building large new networks is to use IPv6. Complexity has been introduced into the way that IP based-networks are already implemented because of address space shortage. Parts of the IPv4 address space need to be reused around the world because there are now too few addresses remaining for the size of the Internet. Some IPv4 address space has been reserved for private (not globally routable) IPv4 addresses, to help overcome these problems. These allocations have been used with network address translation to enable networks to connect to the Internet using only one globally routable IPv4 address. For example, in India, up to three levels of Network Address Translation have been observed. IPv6 offers the potential to build a much more powerful Internet, with vastly larger scale compared to the current situation. Addresses in IPv4 have only 32 bits, allowing for only about 4 billion addresses, compared to 128-bit IPv6, with some 340 trillion, trillion, trillion addresses. As well as increasing the address space, the IETF took the opportunity to build additional features into the IPv6 specification. IPv6 has a new feature called auto configuration. This feature allows a device to generate an IPv6 address as soon as it is given power. Using this 'link local' address, there is no immediate need for any other infrastructure to allow that device to begin communicating via IPv6 on its local network, including communications with another local host or router. If an IPv6 router is present, any IPv6-capable device can generate not only a local address, but a globally routable address, allowing access to the wider Internet. Provision of sufficient address space will also allow re-establishment of an end-to-end architecture in the Internet. The shortage of IPv4 addresses has caused widespread use of private address spaces, which are not directly accessible from the Internet. Devices with IPv6 addresses and IPv6 connectivity can be directly reachable by their address. Such an approach gives rise to the potential to move beyond an "Internet of desktops" to an "Internet of Things" where device to device communication becomes possible. A range of other capabilities were included during the IPv6 development process, for instance mandatory support for security via IPsec. While some of the new features possible in IPv6 based networks are currently possible in IPv4 based networks, the critical exception is that they do not support the scale that IPv6 does, making it difficult or impossible to use them to meet current and future business requirements. The network applications being considered as a basis for new growth in industry productivity require a vastly higher scale of implementation than IPv4 can deliver; thousands or millions of devices and/or addresses. Manual intervention is the other critical element to be considered in the context of implementing large scale networks. If manual set-up is required for every device with an IP 11
- 25. address, significant costs will be incurred. In IPv4 based networks, this requirement has been alleviated by the use of server based configuration of devices using DHCP which is able to automatically allocate IP addresses to new devices on the network with the parameters set by the network administrator. However, for this approach to work, each new device must interact with a DHCP server, which in the case of large-scale networks is resource- and time- intensive. In contrast, IPv6 address allocation is done by the device itself and can occur independently of a server, or in conjunction with an IPv6 enabled router, as appropriate. While many Internet based applications will continue to operate under IPv4, the challenges of network administration and security management continue to grow. For instance, if two companies merge and want to merge their IP based networks then there will have to be renumbering. On the Internet, if the source of malevolent activity needs to be identified, the closest identification by IP address possible under an IPv4 NAT architecture is the globally routable IPv4 address of the top level NAT server [24]. 2.2.4 Routing Protocols A routing protocol specifies how routers communicate with each other, disseminating information that enables them to select routes between any two nodes on a computer network. Routing algorithms determine the specific choice of route. Each router has a priori knowledge only of networks attached to it directly. A routing protocol shares this information first among immediate neighbors, and then throughout the network. This way, routers gain knowledge of the topology of the network [25]. Although there are many types of routing protocols, three major classes are in widespread use on IP networks: • Interior gateway protocols type 1, link-state routing protocols, such as OSPF • Interior gateway protocols type 2, distance-vector routing protocols, such as Routing Information Protocol, RIPv2. • Exterior gateway protocols are routing protocols used on the Internet for exchanging routing information between Autonomous Systems, such as Border Gateway Protocol (BGP), Path Vector Routing Protocol. Exterior gateway protocols should not be confused with Exterior Gateway Protocol (EGP), an obsolete routing protocol. 2.2.4.1 Autonomous System Autonomous system (AS) is a collection of connected IP routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain that presents a common, clearly defined routing policy to the Internet [26]. Autonomous systems can be grouped into four categories, depending on their connectivity and operating policy. • A multi homed autonomous system is an AS that maintains connections to more than one other AS. This allows the AS to remain connected to the Internet in the event of a complete failure of one of their connections. However, unlike a transit AS, this type of AS would not allow traffic from one AS to pass through on its way to another AS. 12
- 26. • A stub autonomous system refers to an AS that is connected to only one other AS. This may be an apparent waste of an AS number if the network's routing policy is the same as its upstream AS's. However, the stub AS may, in fact, have peering with other autonomous systems that is not reflected in public route-view servers. Specific examples include private interconnections in the financial and transportation sectors. • A transit autonomous system is an AS that provides connections through itself to other networks. That is, network A can use network B, the transit AS, to connect to network C. If one AS is an ISP for another, then the former is a transit AS. • An Internet Exchange Point autonomous system (IX or IXP) is a physical infrastructure through which Internet service providers (ISPs) or content delivery networks (CDNs) exchange Internet traffic between their networks. 2.2.4.2 Interior Routing Protocol An IGP is a type of protocol used for exchanging routing information between gateways (commonly routers) within an autonomous system (for example, a system of corporate local area networks). This routing information can then be used to route network-layer protocols like IP [27]. 2.2.4.2.1 Distance Vector Routing Protocol Distance-vector routing protocols use the Bellman–Ford algorithm. In these protocols, each router does not possess information about the full network topology. It advertises its distance value (DV) calculated to other routers and receives similar advertisements from other routers unless changes are done in local network or by neighbors (routers). Using these routing advertisements each router populates its routing table. In the next advertisement cycle, a router advertises updated information from its routing table. This process continues until the routing tables of each router converge to stable values [28]. Some of these protocols have the disadvantage of slow convergence. Examples of distance-vector routing protocols: • Routing Information Protocol (RIP) • Routing Information Protocol Version 2 (RIPv2) • Routing Information Protocol Next Generation (RIPng), an extension of RIP version 2 with support for IPv6 • Interior Gateway Routing Protocol (IGRP) 2.2.4.2.2 Link State Routing Protocol In link-state routing protocols, each router possesses information about the complete network topology. Each router then independently calculates the best next hop from it for every possible destination in the network using local information of the topology. The collection of best-next-hops forms the routing table. 13
- 27. This contrasts with distance-vector routing protocols, which work by having each node share its routing table with its neighbors. In a link-state protocol, the only information passed between the nodes is information used to construct the connectivity maps [29]. Examples of link-state routing protocols: • Open Shortest Path First (OSPF) • Intermediate system to intermediate system (IS-IS) 2.2.4.2.3 Hybrid Routing Protocol Hybrid routing protocols have both the features of distance vector routing protocols and linked state routing protocols. One example is EIGRP. 2.2.4.3 Exterior Routing Protocol An Exterior Gateway Protocol is a routing protocol used to exchange routing information between autonomous systems. This exchange is crucial for communications across the Internet. Notable exterior gateway protocols include Exterior Gateway Protocol (EGP), now obsolete, and Border Gateway Protocol (BGP) [30]. 2.2.5 Open Short Path First OSPF is an IGP that follows LSR Algorithm for routing IP packets solely with in a single routing domain i.e. an Autonomous system. It gathers link state information from available routers and constructs a topology map of the network. OSPF is based on Dijkstra Algorithm for finding shortest path and supports IPv4 and IPv6 networks and supports the CIDR addressing model [31]. OSPF detects changes in the topology, such as link failures, and converges on a new loop-free routing structure within seconds. It computes the shortest-path tree for each route using a method based on Dijkstra's algorithm. The OSPF routing policies for constructing a route table are governed by link metrics associated with each routing interface. Cost factors may be the distance of a router (round-trip time), data throughput of a link, or link availability and reliability, expressed as simple unitless numbers. This provides a dynamic process of traffic load balancing between routes of equal cost. An OSPF network may be structured, or subdivided, into routing areas to simplify administration and optimize traffic and resource utilization. Areas are identified by 32-bit numbers, expressed either simply in decimal, or often in the same octet-based dot-decimal notation used for IPv4 addresses. By convention, area 0 (zero), or 0.0.0.0, represents the core or backbone area of an OSPF network. [32]. OSPF does not use a transport protocol, such as UDP or TCP, but encapsulates its data directly in IP packets with protocol number 89. This is in contrast to other routing protocols, such as the RIP and the BGP. OSPF implements its own transport layer error detection and correction functions. OSPF uses multicast addressing for distributing route information within a broadcast domain [33]. 14
- 28. 2.2.5.1 OSPF Interfaces Another important idea in OSPF is that interfaces used to exchange information with OSPF neighbors have different types. There are too many types to discuss here but you should be aware of two important ones . 1. An OSPF broadcast interface is connected to a shared network, like Ethernet. 2. An OSPF point-to-point interface is connected to a link where there can only be a single OSPF router on either end, such as a WAN link or a purpose-built Ethernet link. The reason for the various interface types is to make sure that all routers know about all routes from all other routers. On point-to-point links, there’s no mystery — the two routers know they’re the only OSPF routers on the link and so they exchange routes with each other. On broadcast links, there’s a potential for many different OSPF routers to be on the network segment. To minimize the number of neighbor relationships that form on broadcast links, OSPF elects a designated router (as well as a backup) whose job it is to neighbor with all other OSPF routers on the segment and share everyone’s routes with everyone else. [34] 2.2.5.2 OSPF Areas Areas in OSPF are collections of routers grouped together. With the exception of area border routers, OSPF routers in one area don’t neighbor with routers in other areas. Among other reasons, areas were once used to scale large OSPF networks. Back when router CPUs were less powerful than they are today, a general rule of thumb was to keep an OSPF area to no more than 50 routers. That would keep the number of OSPF shortest path computations and database updates to a manageable amount as interfaces went up and down, routes were learned and withdrawn, and so on. The most important area in OSPF is the backbone area, also known as area 0. The backbone area is the area that all OSPF areas must traverse to get to other OSPF areas. While OSPF routers within an area know everything there is to know about the network topology, topology information is hidden at area borders [35]. Figure – 4 : Area System of OSPF 15
- 29. 2.2.5.3 OSPFv3 vs OSPFv2 The difference between OSPFv2 and OSPFv3 are [36]: 1) Link-local addresses: OSPFv3 packets are sourced from link-local IPv6 addresses. 2) Links, not networks: OSPFv3 uses the terminology links where we use networks in OSPFv2. 3) New LSA types: there are two new LSA types, and LSA type 1 and 2 have changed. 4) Interface commands: OSPFv3 uses interface commands to enable it on the interface, we don’t use the network command anymore as OSPFv2 does. 5) OSPFv3 router ID: OSPFv3 is unable to set its own router ID like OSPFv2 does. Instead, you have to manually configure the router ID. It is configured as a 32-bit value, same as in OSPFv2. 6) Multiple prefixes per interface: if you have multiple IPv6 prefixes on an interface then OSPFv3 will advertise all of them. 7) Flooding scope: OSPFv3 has a flooding scope for different LSAs. 8) Multiple instances per link: You can run multiple OSPFv3 instances on a single link. 9) Authentication: OSPFv3 doesn’t use plain text or MD5 authentication as OSPFv2 does. Instead, it uses IPv6’s IPSec authentication. 10) Prefixes in LSAs: OSPFv2 shows networks in LSAs as network + subnet mask, OSPFv3 shows prefixes as prefix + prefix length. 2.2.5.4 OSPFv2 and OSPFv3 Header Comparison Figure – 5 : OSPFv2 and OSPFv3 Header Comparison 2.2.5.5 Hello Packet Comparison Figure -6 : OSPFv2 and OSPFv3 Hello Packet Comparison 16
- 30. 2.2.6 Internet Control Message Protocol The ICMP is a supporting protocol in the Internet protocol suite. It is used by network devices, including routers, to send error messages and operational information indicating, for example, that a requested service is not available or that a host or router could not be reached. ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications. ICMP uses the basic support of IP as if it were a higher level protocol, however, ICMP is actually an integral part of IP. Although ICMP messages are contained within standard IP packets, ICMP messages are usually processed as a special case, distinguished from normal IP processing. In many cases, it is necessary to inspect the contents of the ICMP message and deliver the appropriate error message to the application responsible for transmission of the IP packet that prompted the sending of the ICMP message [37]. 2.2.6.1 ICMPv4 ICMPv4 is the implementation of the ICMP for IPv4. ICMPv4 is an integral part of IPv4 and performs error reporting and diagnostic functions, and has a framework for extensions to implement future changes. ICMP is not a transport protocol that sends data between systems. While ICMP is not used regularly in end-user applications, it is used by network administrators to troubleshoot Internet connections [38]. Figure – 7 : Header of ICMPv4 2.2.6.2 ICMPv6 ICMPv6 is the implementation of the ICMP for IPv6. ICMPv6 is an integral part of IPv6 and performs error reporting and diagnostic functions, and has a framework for extensions to implement future changes [39]. Several extensions have been published, defining new ICMPv6 message types as well as new options for existing ICMPv6 message types. NDP is a node discovery protocol in IPv6 which replaces and enhances functions of ARP. SEND is an extension of NDP with extra security. MLD is used by IPv6 routers for discovering multicast listeners on a directly attached link, much like IGMP is used in IPv4. MRD allows discovery of multicast routers [40]. 8 bit type 8 bit code 16 bit checksum 17
- 31. 32 bit Message body Figure – 8 : Header of ICMPv6 2.2.7 Quality of Service QoS is the description or measurement of the overall performance of a service, such as a telephony or computer network or a Cloud computing service, particularly the performance seen by the users of the network. To quantitatively measure quality of service, several related aspects of the network service are often considered, such as error rates, bit rate, throughput, transmission delay, availability, jitter, etc. Not only is QoS necessary for voice and video streaming over the network, it's also an important factor in supporting the growing IoT. The goal of QoS is to provide preferential delivery service for the applications that need it by ensuring sufficient bandwidth, controlling latency and jitter, and reducing data loss [41]. Fundamentally, QoS enables you to provide better service to certain flows. This is done by either raising the priority of a flow or limiting the priority of another flow. When using congestion-management tools, you try to raise the priority of a flow by queuing and servicing queues in different ways. The queue management tool used for congestion avoidance raises priority by dropping lower-priority flows before higher-priority flows. Policing and shaping provide priority to a flow by limiting the throughput of other flows. Link efficiency tools limit large flows to show a preference for small flows. QoS tools can help alleviate most congestion problems. However, many times there is just too much traffic for the bandwidth supplied. In such cases, QoS is merely a bandage. [42]. 2.2.7.1 QOS Basic Architecture The basic architecture introduces the three fundamental pieces for QoS implementation [43]: • QoS identification and marking techniques for coordinating QoS from end to end between network elements • QoS within a single network element (for example, queuing, scheduling, and traffic- shaping tools) • QoS policy, management, and accounting functions to control and administer end-to- end traffic across a network 18
- 32. Figure – 9 : Basic Architecture of QoS 2.2.7.2 Qualities of QOS In packet-switched networks, quality of service is affected by various factors, which can be divided into “human” and “technical” factors. Human factors include: stability of service, availability of service, delays, user information. Technical factors include: reliability, scalability, effectiveness, maintainability, grade of service, etc. Many things can happen to packets as they travel from origin to destination, resulting in the following problems as seen from the point of view of the sender and receiver [44]: 1. Low throughput Due to varying load from disparate users sharing the same network resources, the bit rate (the maximum throughput) that can be provided to a certain data stream may be too low for real time multimedia services if all data streams get the same scheduling priority. 2. Dropped packets The routers might fail to deliver (drop) some packets if their data loads are corrupted, or the packets arrive when the router buffers are already full. The receiving application may ask for this information to be retransmitted, possibly causing severe delays in the overall transmission. 3. Errors Sometimes packets are corrupted due to bit errors caused by noise and interference, especially in wireless communications and long copper wires. The receiver has to detect this and, just as if the packet was dropped, may ask for this information to be retransmitted. 4. Latency It might take a long time for each packet to reach its destination, because it gets held up in long queues, or it takes a less direct route to avoid congestion. This is different from throughput, as the delay can build up over time, even if the throughput is almost normal. In some cases, excessive latency can render an application such as VoIP or online gaming unusable. 5. Jitter Packets from the source will reach the destination with different delays. A packet's delay varies with its position in the queues of the routers along the path between source and destination and this position can vary unpredictably. This variation in delay is known as jitter and can seriously affect the quality of streaming audio and/or video. 6. Out-of-order delivery When a collection of related packets is routed through a network, different packets may take different routes, each resulting in a different delay. The result is that the packets arrive in a different order than they were sent. This problem requires special additional protocols responsible for rearranging out-of-order packets to an isochronous state once they reach their destination. This is especially important for 19
- 33. video and VoIP streams where quality is dramatically affected by both latency and lack of sequence. 2.2.8 Latency Latency is the delay from input into a system to desired outcome; the term is understood slightly differently in various contexts and latency issues also vary from one system to another. Latency greatly affects how usable and enjoyable electronic and mechanical devices as well as communications are. Latency in communication is demonstrated in live transmissions from various points on the earth as the communication hops between a ground transmitter and a satellite and from a satellite to a receiver each take time. People connecting from distances to these live events can be seen to have to wait for responses. This latency is the wait time introduced by the signal traveling the geographical distance as well as over the various pieces of communications equipment [45]. 2.2.8.1 Types of latency Network latency is an expression of how much time it takes for a packet of data to get from one designated point to another. In some environments (for example, AT&T), latency is measured by sending a packet that is returned to the sender; the round-trip time is considered the latency. Ideally, latency is as close to zero as possible. 1) Internet latency is just a special case of network latency - the Internet is a very large WAN. The same factors as above determine latency on the Internet. Internet latency measurement would generally start at the exit of a network and end on the return of the requested data from an Internet resource. 2) Interrupt latency is the length of time that it takes for a computer to act on an interrupt, which is a signal telling the operating system to stop until it can decide what it should do in response to some event. 3) WAN latency itself can be an important factor in determining Internet latency. A WAN that is busy directing other traffic will produce a delay whether a resource is being requested from a server on the LAN, another computer on that network or elsewhere on the Internet. LAN users will also experience delay when the WAN is busy. 4) Audio latency is the delay between sound being created and heard. In sound created in the physical world, this delay is determined by the speed of sound, which varies slightly depending on the medium the sound wave travels through. 5) Computer and operating system latency is the combined delay between an input or command and the desired output. In a computer system, latency is often used to mean any delay or waiting that increases real or perceived response time beyond what is desired. Specific contributors to computer latency include mismatches in data speed between the microprocessor and input/output devices, inadequate data buffers and the performance of the hardware involved, as well as its drivers. The processing load of the computer can also add significant latency. Latency issues are noticeable for an individual, generally increasing user annoyance and impacting productivity as the level increases above 30ms. The severity of the effect varies from 20
- 34. one application to another, as do mitigating tactics. However, games can often be enjoyable up to around 90ms latency. In communications, delays can be a result of heavy traffic, hardware problems, incorrect set up and/or configuration. 2.2.8.2 Latency testing Latency testing can vary from application to application. In some applications, measuring latency requires special and complex equipment or knowledge of special computer commands and programs; in other cases, latency can be measured with a stop watch. In networking, an estimated latency to equipment or servers can be determined by running a ping command; information about latency through all the hops can be gathered with a trace route command. High-speed cameras might be used to capture the minute differences in response times for input to various mechanical and electronic systems. 2.2.8.3 Reducing latency Reducing latency is a function of tuning, tweaking and upgrading both computer hardware and software and mechanical systems. Within a computer, latency can be removed or hidden by such techniques as prefetching and multithreading or by using parallelism across multiple execution threads. Other steps to reduce latency and increase performance include uninstalling unnecessary programs, optimizing networking and software configurations and upgrading or over clocking hardware. 2.2.9 Network Latency Network Latency a.k.a Packet delay is the difference in end-to-end one-way delay between selected packets in a flow with any lost packets being ignored. 2.2.9.1 Types of Packet Delays Two types of delay are commonly measured: 1. One-Way Packet Delay One way packet delay is the time for the each packets taken to reach destination. In this type of delay we basically calculate instantaneous packet delay which means the time difference between each packet in the destination known as jitter. This is referred as the time for a packet to be received at a destination since it was sent from a source. Total delay can be separated into the following components: the time it takes for the source to send it, the time it takes the packet to travel along the physical links that make up the end-to-end path, the time it takes to pass through routers between those links and the time required for the server to process an incoming packet. 2. Round-Trip Packet delay The time for a packet to make the round trip from a source (possibly a client) to a destination (possibly a server) and back, also referred to as round-trip time. RTT can be separated into several components: forward delay, server delay and reverse delay. Forward delay is defined as the time loss done by the router or switch during 21
- 35. forwarding. It is basically happen due to priority scheme of the network. In our concept, Forwarding Delay can be seen in IPv6 packets because priority is given to only IPv4 packets. 2.2.9.2 Types of Delays in Packet Switch Networks There are four major types of delays on each node of a packet-switched network: a) Processing Delay When a packet reaches a router, the router reads the header, locates its final destination, and decides which outbound link to send it on. It also may do some transmission error checking. These account for the processing delay. b) Queuing Delay Most routers utilize a first-come-first-serve queue for packet traffic. If traffic on the router is busy, then the packet will have to wait in a queue for its turn to be transmitted by the router. This accounts for the queuing delay. c) Transmission Delay The amount of time it takes a router to push out the next packet on to the link is the transmission delay. This delay is a function of the size of the packet and the transmission rate of the link. d) Propagation Delay The amount of time it takes to propagate the packet from the beginning of the link to the next link is the propagation delay. It is a function of the length of the link and the speed of the link. 2.2.9.3 Cause of Packet Delays There are two main reasons why delays occur : 1. Network connections – If there are a high number of users connected, or there is a high volume of bandwidth being used while you are also trying to use a VoIP connection, you will likely see a drop in call quality. Be aware that peak usage times e.g., working hours for businesses, may result in some delays. 2. End systems – Sometimes, it is the end system – the system where the data packets are reassembled into data – that creates the delay. The cause of this is usually older equipment that lacks the computing power to handle fast connections and large data transfers. 2.2.9.4 Ways to reduce Reduce Packet Delays Following are the some of the reasons using which we can reduce Packet delays [46]: a) Content Delivery Network 22
- 36. The most important factor that gives rise to Internet latency is distance. The speed of communications over the Internet is limited. And as such the greater the distance between a website or application server and the end user the longer it will take to load that particular website or application. A good way to overcome distance related network latency is to use a CDN. CDNs have a network of geographically distributed edge locations in close proximity to end users. b) Prioritizing the packets Generally, we must have to find the type of packets that we will be using and must have to prioritize the networks packets according to it. For example if we are using IPv6 networks, then we must prioritize the routers to process IPv6 packets at first rather than processing IPv4 packets and same for vice versa. c) Anycast Building an anycast architecture can also help to decrease latency. There are two aspects of anycast that are important to the discussion about reducing latency: Anycast DNS and BGP anycast. Anycast DNS allows DNS queries to be routed to the topologically nearest DNS server, resulting in reduced network latency and quicker DNS query responses. Once your query has been resolved into a unique IP address. Anycast BGP takes over and routes your request to the topologically nearest web server. Anycast BGP again has the advantage of reducing the distance that requests have to travel leading to lower latency. d) Network Monotoning Monitoring your network to identify potential network bottlenecks can be helpful in reducing Internet latency. Tools like the network latency test can be used to test networt latency to different IP prefixes. Network monitoring is a good strategy to get in front of potential network problems. However, network monitoring can only take you so far. Once a network problem like high latency has been identified, network engineers have to go ahead and make manual changes to network topology. Network monitoring can also end up being reactive in nature. 2.2.10 Dual Stack Dual-stack is one of the most widely adopted techniques for IPv6 migration. It helps to establish communication between your IPv6 network and the native IPv4 hosts and applications [47]. A dual-stack node has support for both protocol versions and is referred to as an IPv6/IPv4 node. IPv6/IPv4 nodes have three modes of operation: • IPv4 only - IPv4 stack enabled and IPv6 stack disabled • IPv6 only - IPv6 stack enabled and IPv4 stack disabled • Both IPv4 and IPv6 stacks enabled 23
- 37. 2.2.10.1 Dual Stack Transition Mechanism DSTM is a transition mechanism based on the usage of IPv4-over-IPv6 tunnels to facilitate interoperability between newly deployed IPv6 networks and existing IPv4 networks [48]. Significant Advantages: • Transparent to the network and to the application • Legacy IPv4 applications can be run over IPv6-only networks without modification • IPv4 addresses are dynamically allocated as needed and then reclaimed • Based on standard protocols 2.3 Review of Conceptual Prospective of the study In this section we cover the parameters that affects the performance of the network, among those some are : • Packet Delay • Packet Header • Routing Protocol • Dual Stack Mode Brief Description of those parameters are: 1) Packet Delay: Packet delay PDV is the difference in end-to-end one-way delay between selected packets in a flow with any lost packets being ignored. 2) Packet Header An IP packet consists of a header section and a data section. The data section is the size of data that is desired to be transfer from one host to another where the packet header is always remained attached with the in either of the two protocols, IPv4 and IPv6. The header structure of IPv4 remains same and only the size and the padding value differs according to the header length. The header length is the four bit binary the starts from decimal 5 to 15 that makes the variation on the header size ranges from minimum 20 bytes to 60 bytes. The header structure of IPv6 have some changes with respect to some fields values. The size of the IPv6 header always remains same as the the header length is always equal to 40 bytes. Thus, the performance of IPv6 only differs due to the amount of data sent over the network whereas the performance of IPv4 can get variation due to its changing header size. 3) Routing Protocol A routing protocol specifies how routers communicate with each other, distributing information that enables them to select routes between any two nodes on a computer network. Routing algorithms determine the specific choice of route. Each router has a priori knowledge only of networks attached to it directly. A routing protocol shares this information first among immediate neighbors, and then throughout the network. This way, routers gain knowledge of the topology of the network. There are various routing protocols that can be used according to the required environment. Among which we here will use the OSPF and OSPFv3 routing Protocol which is Dynamic 24
- 38. Routing Protocol. There are other various routing Protocols that can be used and which can differ the performance of overall network. 4) Dual Stack Mode Dual Stack mode is the transition mechanism that enables both IPv4 and IPv6 to be configured in a same interface from where the communication between IPv4 and IPv6 is possible. This is because the hosts with different IP can get communicate between each other using this transition mechanism. However the problem with Dual Stack is that it gives more priority to IPv4 packets rather than the IPv6 packets which as a result makes the variation in the transferring of packets. 2.4 Related Literature Review As we were researching in the domain of our project we got to read different related works and documents which somehow relates to our domain and we too developed our ideas on the basis of these researched documents. Here are number of studies related to IPv4 and IPv6 transition mechanisms have been studied in the past. This section covers review of studies relating to the performance evaluation of various transition mechanisms, which will be using as part of secondary resources in data gathering. The following are the five studies: 1) Study – 1 : IPv4 vs. IPv6 on various Operating Systems using Jumbo Frames First of all we review the research document on “Performance Analysis of IPv4 vs. IPv6 on various Operating Systems using Jumbo Frames” [49]. The purpose of this study is to evaluate the performance of Jumbo frames on a network environment employing six operating systems from two different distributions. These operating systems are Microsoft Windows Server 2008, Microsoft Windows Server 2003 and Microsoft Windows 7 Professional and from the Linux distributions, Linux Fedora, Ubuntu and OpenSUSE. In this study, two transmission protocols were employed namely, TCP and the UDP. Two Internet protocols were also engaged in these performance experiments,IPv6 and IPv4. There were five main performance metrics extracted from the data collected in this experimental study namely the throughput, delay, jitter, the CPU utilizations on the software routers and the packets dropped rate. The Jumbo frame sizes involved ranging from 1518 Bytes to 9014 Bytes. The findings of this study concluded that for traffic employing TCP as transport protocol, Microsoft Windows Server 2008 and Microsoft Windows 7 yielded the highest throughput on both IPv6 and IPv4 and also Linux OpenSUSE on IPv4 only. When UDP was employed as transmission protocol, all of the operating systems yielded similar throughput values. This project developed us the idea that using a jumbo frames on Microsoft Products will provide highest throughput, jitter and lower delay compared linux products where as the concept of jumbo frames were out of our research domain. 2) Study – 2 : IPv4 and IPv6 transition mechanisms on various operating systems As we were moving ahead we landed on the research document of “Performance evaluation of IP version 4 and IP version 6 transition mechanisms on various operating systems” [50]. The purpose of this research is to evaluate performance of two tunneling mechanisms (Configured Tunnel and 6to4 tunneling mechanisms) operate on four 25
- 39. selected operating systems (Windows Server 2003, Windows Server 2008, Ubuntu 9.10, and Fedora Core 11). This performance measurement research examined on two types of transmission protocols namely UDP and TCP. The result of this research focused on four metrics such as throughput, delay, jitter, and CPU utilization. The experiments conducted using different payload sizes, ranging from 64 bytes to 1536 bytes. Results of this experimental research indicated that, Configured Tunnel and 6to4 perform differently on Windows Server 2003, Windows Server 2008, Ubuntu 9.10, and Fedora 11. By using TCP as transport protocol, Configured Tunnel on Fedora 11 produced the highest throughput. However, it also produced a very high delay as compared to Ubuntu 9.10, Windows Server 2003, and Windows Server 2008.On the other hand, after measuring UDP traffic, the results indicated that 6to4 on Ubuntu 9.10 produced the highest throughput with the lowest delay, which designate as the best choice for video and voice traffics. But again from this research we gain the concept of different packet sizes that can be used in the networks where as the concept of tunneling mechanism were way out of our research domain. 3) Study – 3 : IPv6 vs. IPv4 under a Dual-Stack Environment In this paper done by Uk-Nam Law, Man-Chiu Lai, Wee Lum Tan and Wing Cheong Lau(), they present comprehensive empirical measurements of the IPv6 network performance from an end-users perspective [51]. First of all they particularly have chooses about 2000 dual stack host worldwide and send the probing traffic to each of the host which acts as the test bed for their research domain. They quantify the performance differences of using IPv6 vs. IPv4, in terms of various network metrics like network connectivity, hop count, RTT, throughput, operating systems dependencies as well as the address configuration latency. They have also investigated the performance impact of using IPv6 tunneling brokers instead of native IPv6 services. Whenever possible, They also compare their measurement results with previously published ones to reflect on the progress of IPv6 deployment/performance improvements in the past few years. They have designed and implemented an active measurement methodology to evaluate the performance of IPv6 against IPv4 from an end-user’s perspective. Our measurements are conducted between our dual-stack testbed and 2,014 other dual- stack sites in the world. They used both ICMP and TCP traffic to measure the IPv6 network performance. In addition to that, they have also evaluated the latency performance of IPv6 address provisioning mechanisms. Finally, they have also investigated the performance of tunneled-IPv6 connections through the services of 3 tunnel brokers; AARNet, Euro6IX and FreeNet6. In general, Their measurement results indicate that the IPv6 network is able to provide stable network connectivity for IPv6 end-hosts. Due to the relatively light traffic load and abundant bandwidth in the IPv6 backbone, the IPv6 throughput is easily superior to that of IPv4. They have also seen that the tunneled-IPv6 services can achieve performance similar to that of native-IPv6 services. On the other hand, there is still considerable room for improvement in terms of reducing the IPv6 path RTT through the deployment of more IPv6 nodes in the backbone in order to increase the link connectivity of the IPv6 networks around the world. Furthermore, Their results also 26
- 40. show the need for an improvement in the IPv6 performance of Windows-based clients, as compared to Unix-based clients. This is necessary in order to reduce the dependence of the IPv6 performance on the type of operating systems used by the IPv6 end-hosts. 4) Study – 4 : IPv4 and IPv6 Routing Protocols on Wired, Wireless and Hybrid Networks A research on “Performance Evaluation of IPv4 and IPv6 Routing Protocols on Wired, Wireless and Hybrid Networks” [52] where they basically used a sample network of an network configured by both Ipv4 and IPv6 in different routing protocols such as RIP & OSPF. Here they primarily developed three type of scenario wired, wireless and Hybrid scenario. Each of the scenario is divided into three networks and each networks are connected to routers. For storing the packets, a router uses the buffer and the size of the buffer is set to 150000.The switch is used as layer 2 device. If a node on one network wants to communicate with a node on another network, the packet is first sent to layer 2 device. It first checks into the same network and then forwards to the router. The router searches its routing table and sends the packets to the correct destination. In our wireless scenario, every node in the network act as a router for forwarding the packets. If a node is within the transmission range, node directly sends the packets, but if it is out of the transmission range, node relies on the intermediate node for forwarding the packets. The omni-directional antenna model is used due to the fact that it works in all directions. Their radiation cone is 360 degrees in all directions. Simulation is carried out in 50 nodes using CBR as traffic. A number of packets sent by each node are 7500 with the size of 512 bytes. In mixed scenario consists of a wireless and a wired domain. The simulation was performed with 30 wireless nodes and 20 wired nodes. For our hybrid network environment, they have an access point located at the center of the simulation area. Every communication between wired and wireless nodes goes through the access point. The station association type is dynamic. The access point is connected to the hub (layer 2 device). If a node on wired network wants to send the packet to the wireless node, the packet is first sent to the access point. With the use of ad hoc routing protocol, the access point sends the packet to its correct destination. Similarly, the packets from wireless nodes send the packets towards their assigned access points and then the access point sends it to the wired domain. They have evaluated the performance of different routing protocols for IPv4 and IPv6 over wired, wireless and the hybrid network. Some reasons for packet loss that they observed that the size of the buffer, radio range, router load. From the results it has been observed that out of all protocols the performance of AODV (IPv4) is best. It has the maximum throughput and packet delivery ratio with minimum delay and jitter. The paper compares different routing protocols in terms of throughput, jitter, end-to- end delay and PDR which helps in designing the new protocol that can perform better. In the future, they want to extend our work to test routing protocols with different packet sizes and used the header compression technique to reduce the size of Ipv6 header for better performance 27
- 41. 5) Study – 5 : Different Routing Protocols in IPv4 and IPv6 Networks on the basis of Packet Sizes A research alike similar to our project entitled “Performance Evaluation of Different Routing Protocols in IPv4 and IPv6 Networks on the basis of Packet Sizes” [53] where the performance is evaluated for different routing protocols like RIP, RIPng, OSPFv2 and OSPFv3 for IPv4 and IPv6 networks over Mobile Adhoc Networks. Simulations are carried out on Exata Cyber 1.1 Simulator. The performance of networks is measured on the basis of following parameters: throughput, end-to-end delay, jitter and packet delivery ratio with varying packet sizes of 256, 512, 1024 and 2058 bytes. Thus they use the Simulator named as Exata Cyber 1.1 where there are 100 of nodes in the network and the traffic rate is of 1 packet per seconds and the simulation is done for 100 seconds in wireless channel. From the results it has been observed that as the packet sizes increases the overall performance of the network increases. Due to small size of packet the number of packets increased on the source node whereas as the of packet increases the number of packets decreased and the control overheads also decreases. Out of the four protocols the performance of RIPng is best among all the protocols. It is having the maximum throughput and packet delivery ratio with minimum delay and jitter. OSPF for IPv4 networks is not performing well in this case. In future they will evaluate all these protocols on wired and infrastructure based networks as well as also want to test BGP protocol over such networks. 2.6 Development of Conceptual Framework of the study So as we review through our related works mentioned above we assumed that the Performance of Ipv6 networks is obviously better than IPv4 network using any types of routing protocols in any operating system. This research we too tends to test and verify the same condition which we have assumed. Since in the review of our related works the performance analysis is done on the basis of throughput, delays, jitter, bandwidth and so on and different types of simulating softwares are used too. But in our condition we tends to analyze the performance of IPv4 and IPv6 networks on the basis of Packet Delay. Here as we have mentioned above that there exists two types of Packet delays i.e. One-way delay and Round trip time delay. Not only this the term gets confused with the term jitter and latency. If we tends to find the instantaneous packet variation in one way delay then it is called jitter where as if we only analyze the variation in times of packets to reach destination in one- way then it is called Latency. So in our project we will be using the round trip time of the packets i.e. the total time taken by the packets to reach to destination and came back. First of all we will design a simple networks with IPv4 and IPv6 Protocols implied as individually as well as in dual stack. The designed networks will be configured with OSPF routing protocol and ICMP with used as primary form of packet. And we will be pinging the destination and plotting the individual RTT time of each packets with versus to time(in milliseconds) showing the fluctuation. We will vary the size of packets as 512 bytes, 1024 bytes and 2048 bytes where the number of packets that are used will be always constant in each condition. Not only this we too will too plot the minimum, average, maximum RTT and Mean Deviation of the total packets and finally comparing our results and drawing out the 28
- 42. conclusion. Last but the not the least we will point out our project limitation and future enhancements. 29
- 43. CHAPTER – 3 : METHODOLOGY 3.1 Introduction This chapter will cover the methodology employed in this study, the data collection method and the hypotheses that this study will answer in the conclusion of this document. Initially when questions arise, there are different ways of finding answers. In this case, research is conducted in order to answer the questions that triggered this study. Because research is a way of thinking, it needs a method. Method is a logical and orderly course of action for accomplishing the goal. Although a methodology does not define precise methods. 3.2 Hypothesis Here are a number of aspects of network environment that toil together in order to send packets successfully from source to destination. These will all be involved in this study such as operating systems that currently used in a network environments, protocols used for transporting packets from source to destination and different packet sizes that used in real network environment on both the two Internet protocols (IPv4 & IPv6). The main hypothesis of this study is: “Performance of IPv6 on the basis of Packet Delay will better than IPv4 in OSPF routing Protocol under the same condition.” There is also another hypotheses that will be tested in this study and that is: “IPv6 yields better performance on Single Stack Mode rather than that of on Dual Stack Mode under the same condition.” 3.3 Research Methods for study Quantitative method was adopted for this study of network performance measurement. This method mainly concentrates on measurement and statistical data for the objectives that the research focused on. Data gathered in this research is quantitative data, which collected from the experiment conducted in the networking laboratory environment. The findings of this research are the outcomes of the evaluation of data collected from the experiment. Basically there are four types of quantitative studies, which include telephone survey, experiment, co- relational study, and quantitative content analysis. This research will only focus on experimental quantitative research; due to the primary data is totally dependence on the experimental results. The outcome of this research is to find out the performance differences on the basis of packet delay between IPv4 and IPv6 Networks on OSPF routing protocols. Next section will be introducing the data collection method. 30
- 44. 3.4 Data Collection Tools and Methods As mentioned earlier, the Qualitative method is very systematic and the data collection instrument adopted for this study requires following certain processes that define the principle of this study. Firstly, the boundaries of this research is to study the performance of Ipv4 and IPv6 networks mechanisms on the basis of Packet Delay using OSPF routing Protocol that help understanding and adopting a suitable mechanisms for implementation during the migration period from IPv4 to IPv6. The information gathering method that was used in this study was principally dependent on two approaches, reviewing of all the literature gathered and the experimental data. All of the literature that was collected were from books, IEEE conference proceedings, Journals and reputable Internet websites. In the first part of the data collection phase, relevant literature was found to support this work. This literature was reviewed in order to gain further understanding about the topic studied. Emerging from this review was an enhanced knowledge of what had been studied in this arena before. Gaps in the literatures were also identified, which then guided the research conducted. The primary data collection method used in this study was experimental. The main objective was to study the performance of the network on the basis of packet delay in OSPF routing protocols. In order to a gain better understanding, the variable packet sizes were tested with the same dependent variables which is number of packets. However, included in this test were the only one transmission protocols that is UDP because we are using ICMP packets for our research,and the two main Internet Protocols IPv4 and IPv6 as well as we configured Dual stack network too. The results extracted from the data collected in these experiments helped in drawing conclusions for this study to prove whether the pre-defined hypotheses were true or false. The second part of the data collection phase was conducted in a controlled computer laboratory environment. Here we don't use any types of performance measuring software and we only collect our data from the ping results of the packets. While we use Wireshark for determining the header size of ping packets. Since we are using Ubuntu Mate 16.04 LTS in our end system, we can directly export our ping result to CSV format using terminal. Thus obtained result are further filtered and only the RTT time are included in CSV. Thus filtered CSV were then imported to a custom programmed analysis software made from python on the top of Pandas, Numpy and Matplotlib. This custom built programmer provided us the output in the form of graph. These graphs were then used as the main source for the data analysis phase. 31
- 45. CHAPTER – 4 : EXPERIMENTAL DESIGN The data collection instrument employed by this study, as explained earlier, is experimenting in a controlled computer laboratory. The primary focus of this chapter is to explain in detail the equipment employed and the entire experimental setup. The aim of this experimental research is to focus on the evaluation of packet delay in IPv4 and IPv6 network mechanisms running over Ubuntu Mate 16.04 LTS on OSPF routing Protocol. 4.1 Hardware Specifications In order to be consistent and produce accurate data from this study, all of the hardware used in all of the experiments was kept identical. Following in Table 4-1 below outlines the type and specifications of the hardware involved. Hardware Specifications Processor Intel® Core(TM)2 CPU Memory 2GiB System Memory PCI Network Card RTL8101/2/6E PCI Express Fast/Gigabit EthernetController Motherboard MSI Motherboard Chipset G41M-P33 Combo (MS-7592) Table – 1 : Hardware Specifications In addition to the hardware shown in Table above, Cat5e crossover and Straight through cable was used to connect all the computers together. Due to limitation of hardware resources, each computer was not able to have either two Gigabit NIC card or two Fast Ethernet NIC card. To minimize network bandwidth to 100Mbps, a five ports Fast Ethernet switch used for interconnection between sender computer and the router. Crossover Ethernet cables used for the connection between router and router, and Straight through cable is used for the connection between router and switch as well as Switch and receiver. Nevertheless DB9 console cable is used to configure each routers. 4.2 Software Specifications As mentioned in section 3.4, only one operating systems is involved in this study which is Ubuntu Mate 16.04 LTS where we use the OS terminal to generate the traffics for the experiments. Apart from the operating systems, we use python programming language, Pandas, Matplotlib, Numpy, Putty, and Wireshark. Following is a list of all software involved in this study. • Ubuntu Mate 16.04 LTS • Python 3.5.2 • Pandas 0.20.3 • Matplotlib 2.0.2 32
- 46. • Numpy 1.11.0 • Putty • Wireshark 4.3 Network Design 4.3.1 Virtual Network Design The design of the test-bed for this study involved three computers. One computer was the sender, the another computer is the receiver and another computer is configured to be server. The infrastructure was designed to simulate a wide area network. The simulation consisted of two private networks connected by two routers representing public network. Figure on below exemplifies the infrastructure design in more detail. Figure – 10 : Virtual Network Design The three computers were connected by three Cat5e Straight through cables, where as all three routers are connected using two cross over cables and this link sent a Gigabit of data from sender to receiver. The Figure 4-1 above also shows the four different network setups. The all of four internal networks were connected and the middle router acts as the source to external network. The sender and receiver were configured with the Ubuntu Mate 16.04 where as the server is configured with Ubuntu Server 16.04. This configuration was kept constant throughout the whole experimental phase. 33
- 47. 4.3.2 Actual Network Design Figure – 11 : Actual Network Design 4.3.3 IP Addressing Scheme 4.3.3.1 IPv4 Addressing Since we are doing our project in a private network so we have randomly assumed a private ip address of 172.18.36.0 which is of Class – B address with the subnet mask of 255.255.255.0 resulting /24 prefix. 255 . 255 . 255 . 0 11111111.1111111.11111111.00000000 First of all we have to subnet the ip address according to our network design. Since we have 3 routers used each having two interfaces which results total four subnet to be made. So we borrow two bit from the host bit of the subnet which will give us four required number of subnetworks i.e. 22 = 4. 11111111.11111111.11111111.11000000 After borrowing there remains only 6 bits on the side of host bit which results 26 = 64 hosts per network including Network IP and Broadcast IP. Removing these both we land with only 62 ip addresses to hosts per networks. Here is our resulting subnet network range : 172.18.36.0 – 172.18.36.63/26 172.18.36.64 – 172.18.36.127/26 172.18.36.128 – 172.18.36.191/26 172.18.36.192 – 172.18.36.255/26 34
- 48. and the default subnet changes from 255.255.255.0 to 255.255.255.192 resulting prefix to /26. 11111111.11111111.11111111.11000000 255 . 255 . 255 . 192 In the diagram we have divided our network in two parts that is Side-1 and Side-2 which consist one router and one switch at each. The middle router is called the main router and is independent to each side of our network. Figure – 12 : Dividing the network in side-1, side-2 and Main Router Going through the diagram only two of the routers are connected to switches due to which our network is expandable up to 62 hosts per network although we are using only one host in our project at each side and we assign our last two subnets to each side i.e. Network for Side-1 is 172.18.36.128 and Network for Side-2 is 172.18.36.192. Since our network is expandable there will be no any misuse of any IP addresses. Now as for the main router, its interface is connected to the router of each side. If we give our remaining subnets to each side of the router interface then only two IP address from each subnet will be used resulting other 120 IP address to be unused i.e. 60 IP address per networks. For the ipv4 address it is said that we cannot waste the IP address but we can subnets according to our needs i.e. Host IP address cannot be assigned to any other networks where as we can use the subnet while extending our network. So for eradicating this problem we use the concept of Variable Length Subnet Mask which states that we can further subnet the network that has been already subnetted. Using this concept we further subnet the network range of 172.18.36.0/26. observing the network design we need only two IP addresses assigned to router interfaces. Here we borrow four more bit from host bits to network bits resulting 16 subnets i.e. 24 = 16 networks and four number of host per network and two number of usable host per network. 11111111.11111111.11111111.11111100 255 . 255 . 255 . 252 35
- 49. Here the subnet mask changes from 255.255.255.192 to 255.255.255.252 with the /30 prefix. The list of sub network are : 172.18.36.0 – 172.18.36.3/30 172.18.36.4 – 172.18.36.7/30 172.18.36.8 – 172.18.36.11/30 172.18.36.12 – 172.18.36.15/30 172.18.36.16 – 172.18.36.19/30 172.18.36.20 – 172.18.36.23/30 172.18.36.24 – 172.18.36.27/30 172.18.36.28 – 172.18.36.31/30 172.18.36.32 – 172.18.36.35/30 172.18.36.36 – 172.18.36.39/30 172.18.36.40 – 172.18.36.43/30 172.18.36.44 – 172.18.36.47/30 172.18.36.48 – 172.18.36.51/30 172.18.36.52 – 172.18.36.55/30 172.18.36.56 – 172.18.36.59/30 172.18.36.60 – 172.18.36.63/30 from the list of sub network we assign the first two IP address on each side of the networks that is interface connecting to side-1 is given 192.18.36.0/30 and interface connecting to side-2 is given 192.18.36.4/30 Figure – 13 : Assigning IPv4 Addresses 36
- 50. 4.3.3.2 IPv6 addressing So as for the ipv6 addressing we randomly took the ipv6 address with the prefix of 2001:db8:abcd::/48. Since looking at our network design we need four ipv6 address so we change our default address prefix to /64 where the resulting ipv6 address are : 2001:db8:abcd:1::/64 2001:db8:abcd:2::/64 2001:db8:abcd:3::/64 2001:db8:abcd:4::/64 Figure – 14 : Assigning IPv6 Addresses From the diagram, in the main router, we assign the first two ipv6 address to interface connecting to each side that is 2001:db8:abcd:1::/64 to the interface connecting to Side-1 and 2001:db8:abcd:2::/64 to the interface connecting to Side-2. Since only two of the ipaddress from the pool are used in each networks on each interface of router resulting 264 - 2 number of ipv6 address that remains unused on each side. As for the side, we assign 2001:db8:abcd:3::/64 address pool to side-1 and 2001:db8:abcd:4::/64 address pool to Side-2. 4.3.4 OSPF Configurations 4.3.4.1 OSPF Configuration for IPv4 Addresses Before configuring the OSPF in IPv4 Address we first need to assign the IP addresses to each of the interfaces to the router. After assigning the IP addresses we then enable the OSPF in the router by assigning the process ID for it router(config)# router ospf processid where process_id range from 1 to 65535 37
- 51. Then we add the IPv4 networks individually with their network IP addresses and wildcard mask followed by the area number. Here area number defines the autonomous system for the protocol. router(config)# network ip_address wildcard_mask area area_number Figure – 15 : OSPFv2 Configuration For verifying the OSPF protocol configuration we use the command for showing IP route and OSPF neighbor router# show ip route Figure – 16 : OSPFv2 Route Discovery router# show ip ospf neighbor Figure – 17 : OSPFv2 neighbor Discovery 4.3.4.1 OSPF configuration for Ipv6 Addresses Before assigning IPv6 address we have to first enable the ipv6 unicast routing to the router interface. router(config)# ipv6 unicast-routting Then after that we can assign ipv6 addresses to each of the router interfaces. Since the IPv6 uses OSPFv3 so we have to provide an loopback addresses of the router which helps for the thighbone discovery. router(config)# interface loopback loopback_interface_number 38
- 52. router(config-if)# ip address unique_ip_address subnet_mask After this we have to set the IP address of loopback as the router id for OSPF router(config)# router ospf 1 router(config)# router id ip_address_of_loopback Now we have to enable OSPF in each interfaces router(config-if)# router ospf process_id area area_id Figure – 18 : OSPFv3 Configuration Finally we can verify our connection using the commands router# show ipv6 route Figure – 19 : OSPFv3 Route Discovery router# show ipv6 ospf neighbor 39
- 53. Figure – 20 : OSPFv3 Thighbone Discovery 4.4 Testing Testing is an important part of network design and deployment. It is carried to explore the network functionality or to identify problems. It is usually performed before deployment so as to minimize the risks of real world errors and problems. This ensures implementation of the network to be smooth. Network testing in Packet Tracer is achieved through ping, access of services like web, ftp and email over both IPv4 and IPv6. 4.4.1 Ping Testing Figure - 21 : IPv4 communication between two sides Figure - 22 : IPv6 communication between two sides 40
- 54. 4.4.2 HTTP Server Testing Figure – 23 : HTTP server test in Ipv4 Figure demonstrates web page access on a client browser in the network over IPv4. Both client from side 1 and side 2 can access HTTP server. Figure – 24 : HTTP server test in IPv6 Figure demonstrates web page access on a client browser in the network over IPv6. Both client from side 1 and side 2 can access HTTP server. 41
- 55. 4.4.3 FTP Server Testing Figure – 25 : FTP access test in IPv4 Figure demonstrates ftp access from client on the command line interface in the network over IPv4. Both client from side 1 and side 2 can access FTP server. Figure - 26 : FTP access test in IPv6. Figure demonstrates ftp access from client on the command line interface in the network over IPv6. Both client from side 1 and side 2 can access FTP server. 42
- 56. 4.4.4 E-Mail Testing 4.4.4.1 E-Mail Testing over IPv4 Figure – 27 : Email Compose from Admin to client in IPv4 Figure shows Admin compose email for user of side 1 over IPv4 network. Let’s see if user receives it or not. Figure – 28 : Email send result from Admin to client in IPv4 Figure shows admin sends email to user of side 1 network and it successes over IPv4 network and user received it. Figure – 29 : Email reply result in client in IPv4 Figure shows user of side 1 sends mail over IPv4 and let’s see if it success or not. 43
- 57. Figure – 30 : Email receive in client in Ipv4 Figure demonstrates user’s mail over IPv4 network received successfully by admin. 4.4.4.2 E-Mail Testing over IPv6 Figure – 31 : Email Send in Ipv6 from Admin Figure – 32 : Send Success from Admin 44
- 58. Figure – 33 : Email receive at Client Figure – 34 : Reply from user to admin Figure – 35 : User rely mail at admin Figure shows user sends back mail to admin over IPv6. 45
- 59. 4.5 Project Time line Figure – 39 : Overall Project Timeline 46
- 60. 4.6 Project Grant Chart Figure – 40 : Project Grant Chart 47
- 61. CHAPTER – 5 : DATA COLLECTION AND ANALYSIS In this chapter the analysis of the data obtained as a result of the experiments is presented. This chapter is necessary to understand the network performance of the packets in IPv4 and IPv6 networks in an OSPF routing Protocol where each time the size of packets is altered but the number of packets is always constant. 5.1 Data Collection Process Data collection process is the process describing how we are able to collect our data for the research analysis in the controlled laboratory and Quantitative method was adopted for this study of network performance measurement. This method mainly concentrates on measurement and statistical data for the objectives that the research focused on. For our project we are using only ICMP packets that is used to ping from one end to another end. So we use the ping command where the size of packets are altered as 512 bytes, 1024 bytes and 2048 bytes where at each condition we will be sending 25 number of packets. Thus the ping result can be directly exported to CSV format. Figure – 36 : Ping process information Now after we get the CSV data of each of the condition we uses the python script for developing the graphs from the data. A sample graph using which we will be doing our analysis is given below : 48
- 62. Figure – 37 : Plotting Each individual Packet RTT forming graph Example In the above image is the fluctuation graph for each of the packets of IPv4 and IPv6 of size 512 bytes. Here the each graph is plotted with versus to the time with respect to the Sequence of packets. Also there is a legend for the graph at top right of the graph. Figure – 38 : Plotting total RTT of Packets in Each Condition forming Bar graph The above figure is too used for the result analysis for our project. The above figure is plotted on the basis of ping data result where the Minimum RTT, Maximum RTT , Average RTT and Mean Deviation of each ping is plotted. The graph is the ping result of 512 bytes of packet data which consist of legend at top middle of the graph. 5.2 Plotting the RTT of each packet in each condition Here we will be plotting the RTT of each packets forming a line graph of the ICMP packets of 512, 1028 and 2048 bytes where the number of packets is always constant. Figure below presents the Packets Delay results of experiments conducted on Ubuntu operating system 49
- 63. implemented on a network employing IPv6 and IPv4 network using UDP as the transmission protocol. Figure – 41 : Plotting Each individual Packet RTT forming graph at 512 Bytes Figure – 42 : Plotting Each individual Packet RTT forming graph at 1024 Bytes 50
- 64. Figure – 43 : Plotting Each individual Packet RTT forming graph at 1024 Bytes The following list is the analysis of the Packet Delay results for all of networks that is in dual stack and Single stack on UDP presented in Figure 5-1-1 above: 1) While comparing the IPv4 packet RTT in between single stack and Dual stack, the performance of the IPv4 packets in dual stack is comparatively better rather than in single stack mode. When packet size is 512 bytes, there is minimum difference in delay between the packets. As the size of packets increases the mode unstable the network becomes as there exist a sudden increase and decrease in Delays. 2) On the other hand, while comparing the IPv6 packet RTT in between single stack and Dual stack, the performance of the IPv6 packets in Single stack is comparatively better in Single stack mode rather than in Dual stack mode. When packet size is 512 bytes, there is minimum difference in delay between the packets. As the size of packets increases the more delay is observed in the IPV6 packets in Dual Stack Mode. 3) Last but not least, while comparing the IPv4 and IPv6 packets in terms of packet delay in both dual stack and single stack mode, we got the result that the IPv4 packets in Dual Stack mode has minimum and stable delay rather than in other condition of IPv4 and IPv6 networks. 5.3 Graphing the total RTT of packet in each condition Here we plot the total RTT of packet forming a bar graph of the ICMP packets of 512, 1028 and 2048 bytes where the number of packets is always constant. Table below followed by bargraph presents the total Packets Delay results of experiments conducted on Ubuntu operating system implemented on a network employing IPv6 and IPv4 network using ICMP i.e. UDP as the transmission protocol. The below table represents the RTT of whole packets of size 512 bytes. 51
- 65. Protocol Types Round trip time(In Milliseconds) Minimum RTT Average RTT Maximum RTT Mean Deviation IPv4 Packets(Dual Stack) 1.781 1.798 1.822 0.044 IPv6 Packets(Dual Stack) 1.818 1.845 1.898 0.056 IPv4 Packets(Single Stack) 1.769 1.801 1.828 0.033 IPv6 Packets(Single Stack) 1.818 1.846 1.870 0.048 Table – 2 : Table for total RTT of Packets in each condition when 512 bytes Figure – 44 : Plotting total RTT of Packets in Each Condition when 512 bytes The below table represents the RTT of whole packets of size 1024 bytes. Protocol Types Round trip time(In Milliseconds) Minimum RTT Average RTT Maximum RTT Mean Deviation IPv4 Packets(Dual Stack) 2.157 2.175 2.195 0.062 IPv6 Packets(Dual Stack) 2.210 2.230 2.250 0.059 IPv4 Packets(Single Stack) 2.117 2.171 2.217 0.066 IPv6 Packets(Single Stack) 2.203 2.217 2.239 0.066 52
- 66. Table – 3 : Table for total RTT of Packets in Each Condition when 1024 bytes Figure – 45 : Plotting total RTT of Packets in Each Condition when 1024 bytes The below table represents the RTT of whole packets of size 2048 bytes. Protocol Types Round trip time(In Milliseconds) Minimum RTT Average RTT Maximum RTT Mean Deviation IPv4 Packets(Dual Stack) 2.561 2.588 2.618 0.071 IPv6 Packets(Dual Stack) 2.618 2.637 2.657 0.074 IPv4 Packets(Single Stack) 2.561 2.59 2.682 0.069 IPv6 Packets(Single Stack) 2.604 2.632 2.668 0.073 Table – 4 : Table for total RTT of Packets in Each Condition when 1024 bytes 53
- 67. Figure – 46 : Plotting total RTT of Packets in Each Condition when 2048 bytes The following list is the analysis of the Packet Delay results for all of networks that is in dual stack and Single stack on UDP on the basis of RTT presented in Figure 5-1-1 above: 1. From the table 2 and the figure 44, we can see that the average RTT of IPv4 packets in dual stack is better than all of others where as the mean deviation of IPv4 Packets in single stack is less than that of others. 2. From the table 3 and the figure 45, we can see that the average RTT of IPv4 packets in single stack is better than all of others where as the mean deviation of IPv6 Packets in dual stack is better than that of others. 3. From the table 4 and the figure 46, we can see that the average RTT of IPv4 packets in single stack is better than all of others where as the mean deviation of IPv4 Packets in single stack is better than that of others. 4. As we compare the total RTT of IPv4 and IPv6 in each condition we found that the Delay is more in IPv6 regarding all condition. 54
- 68. CHAPTER – 6 : DISCUSSION In this chapter we discusses the findings from the results of the experiment our project. The scope of this research is to evaluate performance differences between IPv4 and IPv6 Networks based on Packet Delay in both Single and Dual Stack Mode. As for the research we select the two condition where one is comparing individual network packets with respect to each other where the size of packet varies and another is that comparing the experiment on the basis of type of network i.e. dual stack mode and single stack mode. To conduct this study, ping packets of variable size were selected. And we use the simple Linux terminal for generating the traffic between the end system. After the data collection phase, one main metric was extracted from the collected data for analysis which is packet delay in RTT. 25 number of packets were employed in the system by varying the its size as 512 bytes, 1024 bytes and 2048 bytes. In the following sections the findings obtained from the data analysis in chapter five are discussed. 6.1 Plotting the individual RTT of Packets After we plot the RTT of each packets with vary in their size, it is observed that the packet delay of IPv4 packets in both Dual and Single Stack mode is less than that of IPv6 Networks in Dual and Single stack mode. This happens because of the following reasons : 6.1.1 Variable Header Size The main reason for the of the packet delay to be less in IPv4 is because of its header. As we know that the size of packet header of IPv4 ranges from 20 bytes to 60 bytes but the size of packet header of IPv6 is always fixed to 40 bytes. So during transmission of packets between the network, the router and switch always process only the Packet header wile the payload data is only processed by the end devices. As we can see that the time taken for processing the 20 bytes of header is obviously less than that of 40 bytes of header. If we tends to increase the header size of IPv4 packets to 40 bytes then the RTT of each packets will be obviously be greater than that of RTT of IPv6 Packets under the same condition. 6.1.2 Priority and Processing Delay The anther reason for the packet delay to be less in IPv4 is due to of processing mechanism of router. Here the router initially assumes the incoming packets to be of IPv4 and after receiving it, it starts processing the packet as it is of IPv4. The actual identification of packets (whether of IPv4 or IPv6) happens during the process of reading its header. If the packets happens to be of Ipv4 than it immediately forwards the packets where as if it happens to be of IPv6 than it consumes more time for the identification and forwarding which can delays the actual transmission of IPv6 Packets. 55
- 69. 6.2 Plotting the average RTT of packets in dual stack and single stack mode After we plot the average RTT of packets with respect to the network mode and size of packets, we obtain the following table where the difference between average RTT of IPv4 and IPv6 in Single and Dual Mode Respectively is given in Different Packet Size : 512 bytes 1024 bytes 2048 bytes Dual Stack 0.047 0.055 0.049 Single stack 0.045 0.046 0.043 Table – 5 : Difference in Total Average RTT in both Network i.e. Avg RTT of Ipv6 – Avg RTT of IPv4 As from the above table we can found that 1. While comparing the packets of IPv4 and IPv6 in dual stack mode where the packet size is 512 bytes, the delay of IPv6 exceeds by 0.047 ms from IPv4 packets where as if we compare both of the networks delay individually the delay gets minimized to 0.045. 2. Again when comparing the packets of IPv4 and IPv6 in dual stack mode where the packet size is 1024 bytes, the delay of IPv6 exceeds by 0.055 ms from IPv4 packets where as if we compare both of the networks delay individually the delay gets minimized to 0.046. 3. Further more While comparing the packets of IPv4 and IPv6 in dual stack mode where the packet size is 2048 bytes, the delay of IPv6 exceeds by 0.049 ms from IPv4 packets where as if we compare both of the networks delay individually the delay gets minimized to 0.043. So finally we found that the difference between average RTT of IPv4 and IPv6 in Single Stack mode is less than that of difference of average RTT in Dual Stack Mode resulting that there is less packet delay in Single stack of IPv6 than that of in Dual Stack yielding better performance. It is because of the priority and processing Delay of IPv6 Packets in Dual Stack mode. 56
- 70. CHAPTER – 7 : CONCLUSION This study was conducted based on the network performance of on the two main Internet protocols IPv6 and IPv4 based on Packet Delay on OSPF routing Protocol. As mentioned in the previous section, results extracted from the data collected from the experiments conducted were based on the ping response from one end system to another end system. There were three Cisco routers, two Cisco switch as and three end systems engaged in this study where the end system OS that were used are Ubuntu Mate 16.04 LTS and Ubuntu Server 16.04 LTS. According to the literature analysis in Chapter Two, this area had not been studied or explored prior to this study. After having completed gathering data via conducting experiments and analyzing the collected data, this study can be summarized and concluded as follows: 1) Comparing IPv6 and IPv4 performance on Ping results, IPv4 performances were better than IPv6 but actually the performance of IPv6 is better due to the conditions discussed in Chapter 6. 2) Also the Delay of IPv6 Packet is less in Single stack mode than that of the delay of IPv6 packet in Dual Stack. In Chapter 3 section 3.2 we have outlined a number of hypotheses for this study. Experiments were conducted in order to collect data, and this data was analyses, all of which helped in agreeing to the following conclusions: The Main Hypothesis : “Performance of IPv6 on the basis of Packet Delay will better than IPv4 in OSPF routing Protocol under the same condition.” The findings of this study concluded that this hypothesis is true and our hypothesis is accpeted under the condition when the packet header size of IPv4 is extended equal to as the packet header size of IPv6 which is 40 Bytes. “IPv6 yields better performance on Single Stack Mode rather than that of on Dual Stack Mode under the same condition.” The findings of this study concluded that this hypothesis is true and our hypothesis is accpeted because the difference between average RTT of IPv4 and Ipv6 in Single Stack mode is less than that of difference of average RTT in Dual Stack Mode. 7.1 Limitations Prime focus of this project is to improve network performance using IPv6 over IPv4. Here are some of the limitations of our project which are pointed below : 1. The prior limitation of our project is that we have done this experiment in a controlled environment of the computer lab not in the real field scenario as well as the size of the 57
- 71. our network is small due to which we are unable to get the exact real scenario results in large scale. 2. Another limitations of our project is that the hardware that were used in our project are financially affordable and are of same kinds due to which we are unable to do our analysis in different types of hardware in different environmental conditions. 3. One of the main limitations of our project is that the reliability of our project as we have only used only our parameter during our project. Reliability of our project has a direct proportion on the numbers of parameter we have used for acquiring our result. The parameter used to measure the performance of IPv4 and IPv6 was Packet Delay. The only one parameter used might not be trusted by the organization which can be more efficiently conceived using more number of parameters. 4. Results may vary while extending the network. The performance might get increased or decreased on the extended network which cannot be guaranteed on the basis of the result gained from the network we built. 7.2 Future Enhancement Every project has a place for betterment. The more the depth of the project, the more will be its improvement. Similarly this project also has its areas of future development. The number of hardwares used can also be extended using the more number of devices and also can integrate in enterprise network. 1. As per the goal of the project, we can enlarge our domain using various aspects such as increasing the numbers of parameters used and the extending the network. We can further use more parameters like Jitter, Bandwidth, latency etc. 2. In future we can perform the analysis in bigger and larger networks in the real scenario but not under the controlled laboratory environment. 3. Not only this in future we may be able to perform the analysis in different types of devices from the different vendors available in the market. 4. As for the dual stack we cam compare the different transitions mechanism from IPv4 to IPv6 or vice versa under different environment. 58
- 72. REFERENCES [1] Sailan, Hassan, and Patel, “A comparative review of IPv4 and IPv6 for research test bed,” in 2009 International Conference on Electrical Engineering and Informatics, Aug. 2009. [2] Govil, Govil, Kaur, and Kaur, “An examination of IPv4 and IPv6 networks : Constraints and various transition mechanisms,” in Southeastcon, 2008. IEEE International Conference on Electrical Engineering and Informatics, April. 2008. [3] T. Dunn, “The IPv6 Transition,” in IEEE Internet Computing, Vol.6, No.3, pp.11-13, May/June 2002. [4] “What is a Computer Network? - Types & Definition - Video & Lesson Transcript,” Study.com. [Online]. Available: http://study.com/academy/lesson/what-is-a-computer- network-types-definition-quiz.html. [5] “IP (Internet Protocol) Definition.” [Online]. Available: https://techterms.com/definition/ip. [6] “IPv4 Definition.” [Online]. Available: https://techterms.com/definition/ipv4.. [7] “What is Internet Protocol Version 6 (IPv6)? - Definition from Techopedia,” Techopedia.com. [Online]. Available: https://www.techopedia.com/definition/5368/internet-protocol-version-6-ipv6. [8] “OSPFv2.” [Online]. Available: https://www.ietf.org/rfc/rfc2328.txt. . [9] “Quality of Service (QoS) - Cisco.” [Online]. Available: https://www.cisco.com/c/en/us/products/ios-nx-os-software/quality-of-service- qos/index.html. [10] “What is IP Packet Delay Variation (IPDV), also called ‘jitter’?,” RIPE Network Coordination Centre. [Online]. Available: https://www.ripe.net/analyse/archived- projects/ttm/test-traffic-measurements/what-is-ip-packet-delay-variation-ipdv-also- called-jitter. [11] N. Unuth, “The Internet Protocol (IP) Explained,” Lifewire. [Online]. Available: https://www.lifewire.com/internet-protocol-explained-3426713. [12] J. Postel, “Internet Protocol.” [Online]. Available: https://tools.ietf.org/html/rfc791#page-9. [13] “Iv4P Packet Header.” [Online]. Available: http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.html. [14] “Understanding IPv4 Addressing - Technical Documentation - Support - Juniper Networks.” [Online]. Available: https://www.juniper.net/documentation/en_US/junos/topics/concept/interface-security- logical-property-ipv4-addressing-understanding.html. 59
- 73. [15] “Types of Routing Protocols (3.1.4) > Cisco Networking Academy’s Introduction to Routing Dynamically.” [Online]. Available: http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=7. [16] “Classless Vs Classful - 24528 - The Cisco Learning Network.” [Online]. Available: https://learningnetwork.cisco.com/docs/DOC-24528. [17] “Classful vs Classless Routing Protocols | NetworkLessons.com.” [Online]. Available: https://networklessons.com/cisco/ccna-routing-switching-icnd1-100-105/classful-vs- classless-routing-protocols/. [18] “What is VLSM ? Explained with Examples.” [Online]. Available: http://www.orbit- computer-solutions.com/variable-length-subnet-mask-vlsm/. [19] “Ipv6 RFC.” [Online]. Available: https://www.ietf.org/rfc/rfc2460.txt. [20] “IPv6 Extension Headers Review and Considerations [IP Version 6 (IPv6)],” Cisco. [Online]. Available: http://www.cisco.com/en/US/technologies/tk648/tk872/technologies_white_paper0900aec d8054d37d.html. [21] “IPv6 Addressing,” IPv6.com, 22-Apr-2006. . [22] R. M. Hinden and S. E. Deering, “IP Version 6 Addressing Architecture.” [Online]. Available: https://tools.ietf.org/html/rfc4291. [23] T. Narten, S. Thomson, and T. Jinmei, “IPv6 Stateless Address Autoconfiguration.” [Online]. Available: https://tools.ietf.org/html/rfc4862#section-5.5.1. [24] “Advantages of IPv6 | IPv6 Now.” [Online]. Available: http://ipv6now.com.au/primers/IPv6Advantages.php. [25] “Routing protocols.” [Online]. Available: http://study-ccna.com/routing-protocols/. [26] J. Hawkinson and T. Bates, “Guidelines for creation, selection, and registration of an Autonomous System (AS).” [Online]. Available: https://tools.ietf.org/html/rfc1930. [27] “What is IGP (Interior Gateway Protocol)? - Definition from WhatIs.com,” SearchSecurity. [Online]. Available: http://searchsecurity.techtarget.com/definition/IGP. [28] “Types of Distance Vector Routing Protocols (3.2.2) > Cisco Networking Academy’s Introduction to Routing Dynamically.” [Online]. Available: http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=9. [29] “Link State Routing Protocols > Dynamic Routing Protocols.” [Online]. Available: http://www.ciscopress.com/articles/article.asp?p=24090&seqNum=4. [30] “What is Exterior Gateway Protocol (EGP)? - Definition from WhatIs.com.” [Online]. Available: http://whatis.techtarget.com/definition/Exterior-Gateway-Protocol-EGP. [31] A. Networks, “Open Shortest Path First OSPF Protocol Explained,” Auvik Networks, 04-Nov-2014. [Online]. Available: https://www.auvik.com/media/blog/ospf-protocol- explained/. [32] “OSPF (Open Shortest Path First) Definition.” [Online]. Available: https://techterms.com/definition/ospf. 60
- 74. [33] I. Price-Evans, “What is Open Shortest Path First (OSPF)?” [Online]. Available: https://www.metaswitch.com/resources/what-is-open-shortest-path-first-ospf. [34] “IP Routing: OSPF Configuration Guide, Cisco IOS Release 12.4T - Configuring OSPF [Cisco IOS Software Releases 12.4 T],” Cisco. [Online]. Available: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_ospf/configuration/12-4t/iro- 12-4t-book/iro-cfg.html. [35] “What Are OSPF Areas and Virtual Links?,” Cisco. [Online]. Available: https://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13703- 8.html. [36] “OSPFv2 vs OSPFv3 | NetworkLessons.com.” [Online]. Available: https://networklessons.com/ipv6/ospfv2-vs-ospfv3/. [37] “Internet Control Message Protocol (ICMP).” [Online]. Available: http://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.html. [38] J. Postel, “Internet Control Message Protocol.” [Online]. Available: https://tools.ietf.org/html/rfc792. [39] J. Postel, “Internet Control Message Protocol.” [Online]. Available: https://tools.ietf.org/html/rfc792. [40] A. Conta and M. Gupta, “Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification.” [Online]. Available: https://tools.ietf.org/html/rfc4443. [41] “ICMPv6 Functions, ICMPv6 Header Packet Format and Types of ICMPv6 messages.” [Online]. Available: http://www.omnisecu.com/tcpip/ipv6/icmpv6-functions-icmpv6- packet-format-and-icmpv6-message-types.php. [42] “Quality of Service (QoS),” Cisco. [Online]. Available: https://www.cisco.com/c/en/us/products/ios-nx-os-software/quality-of-service- qos/index.html. [43] “Quality of Service Networking - DocWiki.” [Online]. Available: http://docwiki.cisco.com/wiki/Quality_of_Service_Networking. [44] “The Basics Of QoS,” Network Computing, 15-Aug-2016. [Online]. Available: http://www.networkcomputing.com/networking/basics-qos/402199215. [45] “Quality of Service (QOS).” [Online]. Available: http://ecomputernotes.com/computernetworkingnotes/communication-networks/quality- of-service. [46] “What is latency? - Definition from WhatIs.com,” WhatIs.com. [Online]. Available: http://whatis.techtarget.com/definition/latency. [47] NerdsSupport, “What exactly is a packet delay?,” Nerds Support, 07-Nov-2013. [Online]. Available: https://nerdssupport.com/blog/what-exactly-is-a-packet-delay/. [48] “What is a Dual Stack Network? - Definition from Techopedia.” [Online]. Available: https://www.techopedia.com/definition/19025/dual-stack-network. 61
- 75. [49] Paula Raymond Lutui, “Performance Analysis of IPv4 vs. IPv6 on various Operating Systems using Jumbo Frames” in 2012 International Conference on Electrical Engineering and Informatics, Aug. 2012. [50] Sotharith Tauch, “Performance evaluation of IP version 4 and IP version 6 transition mechanisms on various operating systems” in 2010 International Conference on Electrical Engineering and Informatics, April. 2010. [51] Yuk-Nam Law, Man-Chiu Lai, Wee Lum Tan and Wing Cheong Lau, “Empirical Performance of IPv6 vs. IPv4 under a Dual-Stack Environment” in 2012 International Conference on Electrical Engineering and Informatics, Aug. 2012. [52] Sonal Telang Chandel, Sanjay Sharma, “Performance Evaluation of IPv4 and IPv6 Routing Protocols on Wired, Wireless and Hybrid Networks” in International Journal of Computer Networks and Applications (IJCNA), Volume 3, Issue 3, May – June (2016) [53] Dipti Chauhan, Sanjay Sharma, “Performance Evaluation of Different Routing Protocols in IPv4 and IPv6 Networks on the basis of Packet Sizes ” in International Conference on Information and Communication Technologies (ICICT), May – June (2016) 62
- 76. APPENDIX Configuration of Router -1 at Side -1 Building Configuration… Current Configuration: 1404 bytes ! ! Last Configuration change at 07:01:12 UTCWed Aug 30 2017 ! version 15.04 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname Side-2-Router ! boot-start-marker boot-end-marker ! ! ! no aaa new-model ! ! ! ! ! ! ! ! ! ! ! ip dhcp pool side-2 network 172.18.36.192 255.255.255.192 default-router 172.18.36.193 ! ! ! ip cef ipv6 unicast-routing 63
- 77. ipv6 cef multilink built-name authenticated ! cts loogng verbose ! ! liscence udi pid CISCO1921/K9 sn FGL21122370 ! ! ! redundancy ! ! ! ! ! ! interface Embedded-Servic-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 172.18.38.6 255.255.255.252 duplex auto speed auto ipv6 address 2001:DB8:ABCD:2::1/64 ipv6 ospf 1 area 0 interface GigabitEthernet0/1 ip address 172.18.38.193 255.255.255.192 duplex auto speed auto ipv6 address 2001:DB8:ABCD:4::1/64 ipv6 ospf 1 area 0 ! router ospf 1 network 172.18.36.4 0.0.0.3 area 1 network 172.18.36.192 0.0.0.63 area 1 ! ip forward-protocol nd 64
- 78. ! no ip http server no ip http secure-server ! ! ipv6 router ospf 1 router-id 3.3.3.3 ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec transport preferred none transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input none ! shedular allocate 20000 1000 ! end Configuration of Router – 2 of Side 2 Building Configuration… Current Configuration: 1404 bytes ! ! Last Configuration change at 07:01:12 UTCWed Aug 30 2017 ! version 15.04 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption 65
- 79. ! hostname Side-1-Router ! boot-start-marker boot-end-marker ! ! ! no aaa new-model ! ! ! ! ! ! ! ! ! ! ! ip dhcp pool side-1 network 172.18.36.128 255.255.255.192 default-router 172.18.36.129 ! ! ! ip cef ipv6 unicast-routing ipv6 cef multilink built-name authenticated ! cts loogng verbose ! ! liscence udi pid CISCO1921/K9 sn FGL21122370 ! ! ! redundancy ! ! 66
- 80. ! ! ! ! interface Embedded-Servic-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 ip address 172.18.38.2 255.255.255.252 duplex auto speed auto ipv6 address 2001:DB8:ABCD:3::1/64 ipv6 ospf 1 area 0 ! router ospf 1 network 172.18.36.0 0.0.0.3 area 1 network 172.18.36.128 0.0.0.63 area 1 ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ! ipv6 router ospf 1 router-id 2.2.2.2 ! ! ! ! control-plane ! ! ! line con 0 line aux 0 line 2 no activation-character no exec 67
- 81. transport preferred none transport output pad telnet rlogin lapb-ta mop udptn v120 ssh stopbits 1 line vty 0 4 login transport input none ! shedular allocate 20000 1000 ! end Configuration of Main Router Building Configuration… Current configuration 1455 bytes ! Version 15.3 Service timestanps debug dateline nsec Service timestanps log dateline nsec No service password –encryption ! Hostname Router ! Boot-start-maker Boot-end-marker ! Aqn-register-fnf ! ! no aaa new-model ! ! ! ! ! ! ! ! Ip cef Ipv6 unicast-routing 68
- 82. Ipv6 cef ! ! ! ! Multilink bundle-name authenticated ! ! ! ! ! ! ! License udi pid c881-k9 sn FGL203924IN ! ! ! ! ! ! ! License udi pid C881-k9 on FGL204924IN ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! Interface FastEthernet0 Swichport access vlan10 no ip address 69
- 83. ! Interface FastEthernet1 Switchport access vlan20 no ip address ! Interface FastEthernet2 no ip address ! Interface FastEthernet3 no ip address ! Interface FastEthernet4 no ip address shutdown speed auto ! Interface Vlan1 no ip address ! Interface Vlan10 ip address 172.18.36.1 255.255.255.252 ipv6 address 2001:db8:abcd:1::1/64 ipv6 ospf 1 area 0 ! Interface Vlan20 Ip address 172.18.36.5 255.255.255.252 Ipv6 address 2001:DB8:ABCD:2::1/64 Ipv6 ospf area 1 Ip address 172.18.36.5 255.255.255.252 Ipv6 address 2001:DB8:ABCD:2::1/64 Ipv6 ospf 1 area 1 ! Router ospf 1 Network 172.18.36.0 0.0.0.3 area 1 Network 172.18.36.4 0.0.0.3 area 1 ! ! ! Ipv6 router ospf 1 router-id 1.1.1.1 ! 70
- 84. ! !control-plane ! ! ! Mgcp behavior rsip-range tgcp-only Mgcp behavior comedia-role none Mgcp behavior comedia-check-media-src disable Mgcp behavior comedia-sdp-force disable ! Mgcp profile default ! ! ! ! ! Line con 0 No modem enable Line aux 0 Line vty 0 4 Login Transport input all ! Scheduler allocate 20000 1000 ! End Python Program For Plotting Each Packets RTT forming a line Graph import pandas as pd import csv import matplotlib.pyplot as plt plt.style.use('ggplot') df = pd.read_csv('IP_Comparison_2048_bytes.csv') a = df['Sequence of Packets'] b = df['IPv4 Packets (Dual Stack)'] c = df['IPv6 Packets (Dual Stack)'] d = df['IPv4 Packets (Single)'] e = df['IPv6 Packets (Single)'] plt.title('IPv4 & IPv6 Fluctuation Data (2048 Byte Packets)', fontsize=14) 71
- 85. plt.xlabel('Sequence of Packets') plt.ylabel('Time (in Millliseconds)') plt.plot(a,b, label='IPv4 Packets (Dual Stack)') plt.plot(a,c, label='IPv6 Packets (Dual Stack)') plt.plot(a,d, label='IPv4 Packets (Single)') plt.plot(a,e, label='IPv6 Packets (Single)') plt.legend() plt.show() Python Program for Plotting Average RTT of Packets forming a Bar Graph import matplotlib.pyplot as plt import numpy as np plt.style.use('ggplot') index = np.arange(4) packet_minRTT = (1.781,1.818,1.769,1.818) packet_avgRTT = (1.798,1.845,1.801,1.846) packet_maxRTT = (1.822,1.898,1.828,1.87) packet_mDev = (0.044,0.056,0.033,0.048) bar_width = 0.18 opacity = 0.5 ipv4_dual_stack = plt.bar(index, packet_minRTT, bar_width, alpha=opacity, color='b', label='Minimum RTT') ipv6_dual_stack = plt.bar(index + bar_width, packet_avgRTT, bar_width, alpha=opacity, color='r', label='Average RTT') ipv4_single_stack = plt.bar(index + bar_width + bar_width, packet_maxRTT, bar_width, alpha=opacity, color='y', label='Maximum RTT') ipv6_single_stack = plt.bar(index + bar_width + bar_width + bar_width, packet_mDev, bar_width, alpha=opacity, color='g', label='Mean Deviation') plt.xlabel('IP Packets') plt.ylabel('Time (in ms)') plt.title('IP Packets RTT Bargraph (512 Bytes)') plt.xticks(index + bar_width ,('IPv4 Dual Stack','IPv6 Dual Stack','IPv4 Single Stack','IPv6 Single Stack')) plt.legend() plt.tight_layout() plt.show() 72