Cast your vote
You can rate an item by clicking the amount of stars they wish to award to this item.
When enough users have cast their vote on this item, the average rating will also be shown.
Your vote was cast
Thank you for your feedback
Thank you for your feedback
KeywordBorder Gateway Protocol
Inter-Autonomous System Routing
Interior Gateway Protocols
Exterior Gateway Protocols
Open Short Path First
Enhanced Interior Gateway Routing Protocol
MetadataShow full item record
AbstractBorder Gateway Protocol is the protocol which makes the Internet work. It is used at the Service provider level which is between different Autonomous Systems (AS). An Autonomous System is a single organization which controls the administrative part of a network. Routing with in an Autonomous System is called as Intra-Autonomous routing and routing between different Autonomous Systems is called as Inter-Autonomous System routing. The routing protocols used within an Autonomous System are called Interior Gateway Protocols (IGP) and the protocols used between the Autonomous Systems are called Exterior Gateway Protocols. Routing Information Protocol (RIP), Open Short Path First (OSPF) and Enhanced Interior Gateway Routing Protocol (EIGRP) are the examples for IGP protocols and Border Gateway Protocol (BGP) is the example for EGP protocols. Every routing protocol use some metric to calculate the best path to transfer the routing information. BGP rather than using a particular metric, it uses BGP attributes to select the best path. Once it selects the best path, then it starts sending the updates in the network. Every router implementing BGP in the network, configures this best path in its Routing Information Base. Only one best route is selected and forwarded to the whole network.  Due to the tremendous increase in the size of the internet and its users, the convergence time during link failure in the protocol is very high.
Showing items related by title, author, creator and subject.
Routing Protocols for MANETsMuchintala, Priyanka Reddy; Hash, Larry; Advisor (2016-08)This technology case study focuses on the routing protocols used in mobile ad-hoc networks. For any wireless ad-hoc network, routing is the main concept. Proactive and reactive routing protocols are two such approaches. The ever changing properties like asymmetric links, low transmission power and topology have always been a challenge for the routing protocols. Under such circumstances, the proactive and reactive routing protocols have proved to be inefficient. Each of these approaches has its own disadvantages. To overcome these disadvantages, hybrid routing protocol has been designed. This paper will provide an overview of all the three above mentioned protocols namely proactive routing protocol, reactive routing protocol and hybrid routing protocol with an example each. A comparison between the three routing protocols is also provided in this paper.
A Technology Case Study on Integrating Open Stack with SDN for Internet Connectivity using BGPGonuguntla, Raja Bhushan Rao; Hash, Larry; Advisor (2016-12)There were many developments in Internet usage, which resulted in significant increase in Internet routing. With existing networking infrastructure, it is difficult to meet these requirements and causing more cost and less performance. Since network devices are hardware modules, processing them requires more power and more memory. However, if network protocols are developed using software modules, flexibility can be achieved in various programming applications and reduces dependency on hardware. The concept of using networking protocols as a software module can be explained using “Software Defined Networking (SDN).” With SDN, existing infrastructure can be integrated with various applications and centralized control protocols can be developed. One of the key components of SDN is integrating with Cloud Computing, where many applications can be built, which can be used for on-demand services. Integrating cloud computing with SDN will create dynamic networks and reduces infrastructure costs. In this paper, a case was considered for providing better internet connectivity by building public & private networks using Open source cloud technology (OpenStack) and existing distribution environments. For connectivity, BGP was used as routing protocol as it is known to be well- suited for such environments. Both public and private networks were integrated with SDN for centralized control. OpenStack was used to build various network topologies using different plugins through SDN controller. This method allowed to develop SDN controller with global view of OpenStack networks. The same controller was connected to distributed layers using Open Flow protocol. Since, both OpenStack and distributed networks were attached to SDN controller, centralized control of network protocols could be achieved. This model of centralized networks could be very useful in reducing costs and improving network efficiency, especially in large scale deployments.
Creating a mesh sensor network using Raspberry Pi and XBee radio modulesForcella, Michael (2017-05)A mesh network is a type of network topology in which one or more nodes are capable of relaying data within the network. The data is relayed by the router nodes, which send the messages via one or more 'hops' until it reaches its intended destination. Mesh networks can be applied in situations where the structure or shape of the network does not permit every node to be within range of its final destination. One such application is that of environmental sensing. When creating a large network of sensors, however, we are often limited by the cost of such sensors. This thesis presents a low-cost mesh network framework, to which any number of different sensors can be attached. The hardware configuration is detailed in such a way that anyone with a modest understanding of technology will be able to reproduce it. The software setup required by the user has also been minimized and clearly documented. Details specific to the user's setup can be entered into a configuration file and the majority of software scripts are scheduled to run automatically via Linux Cron jobs. I conclude by outlining several potential modifications to the framework, including further automation of the software setup, inclusion of additional hardware, and alternate methods for downloading data from the network.