project report on routing protocols
TRANSCRIPT
-
8/22/2019 Project report on routing protocols
1/14
COMPARISON OF ROUTING
PROTOCOLS
Aproject report
submitted as part of six week industrial training in
partial fulfillment of the requirement for the award of the Degree
of
Bachelor of Technology
in
Computer Science and Engineering
atNational Aviation Company of India Ltd. (NACIL)
under the guidance of
Mr. Vijay Kumar
Deputy Manager (IT)
Submitted by:
Department of Computer Science and Engineering
AMITY SCHOOL OF ENGINEERING AND TECHNOLOGYGuru Gobind Singh Indraprastha University, Dwarka
2010-2014
-
8/22/2019 Project report on routing protocols
2/14
2
CERTIFICATE
This is to certify that this report entitled COMPARISON OF ROUTING
PROTOCOLS comprehends the authentic work of industrial training w.e.f. 24
th
JUNE2013 to 2nd
AUGUST 2013 at :National Aviation Company of India Ltd. - IndianAirlines(NACIL-I),Air India, Safdarjung, New Delhi-110003, accomplished by:
Name: Bhawna Garg Enrollment Number: 04010402710
Name: Vishrant Ratra Enrollment Number: 03510402710
This training partially fulfills their Bachelor of Technology course requirement after third
Year at Amity School of Engineering and Technology, an institution affiliated to GuruGobind Singh Indraprastha University, Delhi.
SIGNATURE OF PROJECT INCHARGE:
NAME:
DESIGNATION:
NAME & SEAL OF THE COMPANY
-
8/22/2019 Project report on routing protocols
3/14
3
ACKNOWLEDGEMENT
The project work in this report is an outcome of continual work and draws intellectualsupport from various sources. Obligations thus incurred in completing the work have been
many. It is therefore almost impossible to express adequately the debts owed to manypersons who have been contributing to bring about this project.
We take the opportunity to thank Mukesh Kumar, Sr. Manager (S/M) and Mr. Vijay KumarDy Manager (DC), Department of IT, for giving me an opportunity to work here and for
their invaluable guidance to us. I am also thankful to the Air India team for their help
where required.
Finally, I would like to thank all the people who, directly or indirectly helped me in
completing this project.
Date: 17-06-13 to 02-08-13
Place: National Aviation Company of India Ltd. - Indian Airlines (NACIL-I), Safdarjung,New Delhi-110003.
------------ ------------ -------------(Bhawna Garg) (Purvai Marwaha) (Vishrant Ratra)
-
8/22/2019 Project report on routing protocols
4/14
4
ABSTRACT
-
8/22/2019 Project report on routing protocols
5/14
5
INDEX
Acknowledgement
Certificate
Table of figuresObjectiveAbstract
Part-I: Introduction
1. Router2. Routing Protocols3. DVMRP4. DV5. Network Throughput
Part II: System Analysis
1. Platform-Unix(Ubuntu)2.
Network Simulator3. Nam Utility
4. AwkPart III: Conclusion
ConclusionPart IV: Appendix
-
8/22/2019 Project report on routing protocols
6/14
6
LIST OF FIGURES
-
8/22/2019 Project report on routing protocols
7/14
7
-
8/22/2019 Project report on routing protocols
8/14
8
OBJECTIVE
Part-I : Introduction
-
8/22/2019 Project report on routing protocols
9/14
9
1. Router
Router is an Intermediate System (IS) which operates at the network layer of the OSIreference model. Routers may be used to connect two or more IP networks, or an IP
network to an internet connection.
A router consists of a computer with at least two network interface cards supporting the IP
protocol. The router receives packets from each interface via a network interface and
forwards the received packets to an appropriate output network interface. Received packets
have all link layer protocol headers removed, and transmitted packets have a new linkprotocol header added prior to transmission.
The router uses the information held in the network layer header(i.e. IP header) to decide
whether to forward each received packet, and which network interface to use to send thepacket. Most packets are forwarded based on the packet's IP destination address, along withrouting information held within the router in a routing table. Before a packet is forwarded,
the processor checks the Maximum Transfer Unit (MTU) of the specified interface. Packets
larger than the interface's MTU must be fragmented by the router into two or more smaller
packets. If a packet is received which has the Don't Fragment (DF) bit set in the packetheader, the packet is not fragmented, but instead discarded. In this case, an ICMP error
message is returned to the sender (i.e. to the original packet's IP source address) informing
it of the interface's MTU size. This forms the basis forPath MTU discovery (PMTU).
The routing and filter tables resemble similar tables in link layer bridges and switches.
Except, that instead of specifying link hardware addresses (MAC addresses), the routertable specify network(IP addresses). The routing table lists known IP destination addresses
with the appropriate network interface to be used to reach that destination. A default entry
may be specified to be used for all addresses not explicitly defined in the table. A filter
table may also be used to ensure that unwanted packets are discarded. The filter may beused to deny access to particular protocols or to prevent unauthorized access from remote
computers by discarding packets to specified destination addresses.
A router forwards packets from one IP network to another IP network. Like other systems,
it determines the IP network from the logical AND of an IP address with the associated
subnetwork address mask. One exception to this rule is when a router receives an IP packet
to a network broadcast address. In this case, the router discards the packet. Forwardingbroadcast packet can lead to severe storms of packets, and if uncontrolled could lead to
network overload.
A router introduces delay (latency) as it processes the packets it receives. The total delay
observed is the sum of many components including:
Time taken to process the frame by the data link protocol Time taken to select the correct output link (i.e. filtering and routing)
http://www.erg.abdn.ac.uk/users/gorry/course/intro-pages/es-is.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/nic.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/nic.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-address.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/mtu.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/mac.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-address.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-address.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/mac.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/mtu.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-address.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip-packet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/nic.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/nic.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/ip.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/intro-pages/es-is.html -
8/22/2019 Project report on routing protocols
10/14
10
Queuing delay at the output link (when the link is busy) Other activities which consume processor resources (computing routing tables,
network management, generation of logging information)
The router queue of packets waiting to be sent also introduces a potential cause of packet
loss. Since the router has a finite amount of buffer memory to hold the queue, a routerwhich receives packets at too high a rate may experience a full queue. In this case, therouter ahs no other option than to simply discard excess packets. If required, these may
later be retransmitted by a transport protocol.
Fig.11. Architecture of a router
Routers are often used to connect together networks which use different types of links (forinstance an HDLC link connecting a WAN to a local Ethernet LAN). The optimum (and
maximum) packet lengths (i.e. the maximum transmission unit (MTU)) is different for
different types of network. A router may therefore uses IP to provide segmentation ofpackets into a suitable size for transmission on a network.
Associated protocols perform network error reporting (ICMP), communication betweenrouters (to determine appropriate routes to each destination) and remote monitoring of the
router operation (network management).
http://www.erg.abdn.ac.uk/users/gorry/course/dl-pages/hdlc.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/enet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/intro-pages/lan.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/mtu.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/icmp.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/inet-pages/mtu.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/intro-pages/lan.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/lan-pages/enet.htmlhttp://www.erg.abdn.ac.uk/users/gorry/course/dl-pages/hdlc.html -
8/22/2019 Project report on routing protocols
11/14
11
Fig.12. Packets routed by routers to their destinations
-
8/22/2019 Project report on routing protocols
12/14
12
Part-II: System Analysis
http://en.wikipedia.org/wiki/Image:Indian_Logo.gif -
8/22/2019 Project report on routing protocols
13/14
13
-
8/22/2019 Project report on routing protocols
14/14
14