Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Optimized Link State Routing Protocol
open-in-new
<h2 id="features-specific-to-olsr">Features specific to OLSR</h2> <p>Link-state routing protocols such as <a href="/facts/Open_Shortest_Path_First/PACpGUHb">Open Shortest Path First</a> (OSPF) and <a href="/facts/Intermediate_System_to_Intermediate_System/zaNkSwhW">Intermediate System to Intermediate System</a> (IS-IS) elect a <i>designated router</i> on every link to perform flooding of topology information. In wireless ad hoc networks, there is different notion of a link, packets can and do go out the same interface; hence, a different approach is needed in order to optimize the flooding process. Using Hello messages the OLSR protocol at each node discovers 2-hop neighbor information and performs a distributed election of a set of <i><a href="/facts/Multipoint_relay/G5M3pvQK">multipoint relays</a></i> (MPRs). Nodes select MPRs such that there exists a path to each of its 2-hop neighbors via a node selected as an MPR. These MPR nodes then source and forward TC messages that contain the MPR selectors. This functioning of MPRs makes OLSR unique from other link state routing protocols in a few different ways: The forwarding path for TC messages is not shared among all nodes but varies depending on the source, only a subset of nodes source link state information, not all links of a node are advertised but only those that represent MPR selections. </p><p>Since link-state routing requires the topology database to be synchronized across the network, OSPF and IS-IS perform topology flooding using a reliable algorithm. Such an algorithm is very difficult to design for ad hoc wireless networks, so OLSR doesn't bother with reliability; it simply floods topology data often enough to make sure that the database does not remain unsynchronized for extended periods of time. </p> <h3>Multipoint relays</h3> <p>Multipoint relays (MPRs) relay messages between nodes. They also have the main role in <a href="/facts/Routing/Ml6MVCaC">routing</a> and selecting the proper route from any source to any desired destination node. </p><p>MPRs advertise link-state information for their MPR selectors (a node selected as a MPR) periodically in their control messages. MPRs are also used to form a route from a given node to any destination in route calculation. Each node periodically broadcasts a Hello message for the link sensing, neighbor detection and MPR selection processes.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p> <h2 id="benefits">Benefits</h2> <p>Being a proactive protocol, routes to all destinations within the network are known and maintained before use. Having the routes available within the standard routing table can be useful for some systems and network applications as there is no route discovery delay associated with finding a new route. </p><p>The routing overhead generated, while generally greater than that of a reactive protocol, does not increase with the number of routes being created. </p><p>Default and network routes can be injected into the system by <i>Host and Network Association</i> (HNA) messages allowing for connection to the internet or other networks within the OLSR <a href="/facts/MANET/Gwb3FlAD">MANET</a> cloud. Network routes are something reactive protocols do not currently execute well. </p><p>Timeout values and validity information is contained within the messages conveying information allowing for differing timer values to be used at differing nodes. </p> <h2 id="criticisms">Criticisms</h2> <p>The original definition of OLSR does not include any provisions for sensing of link quality; it simply assumes that a link is up if a number of hello packets have been received recently. This assumes that links are bi-modal (either working or failed), which is not necessarily the case on wireless networks, where links often exhibit intermediate rates of packet loss. Implementations such as the open source OLSRd (commonly used on <a href="/facts/Linux/9FvCKSTq">Linux</a>-based mesh routers) have been extended (as of v. 0.4.8) with link quality sensing. </p><p>Being a proactive protocol, OLSR uses power and network resources in order to propagate data about possibly unused routes. While this is not a problem for wired access points, and laptops, it makes OLSR unsuitable for sensor networks that try to sleep most of the time. For small scale wired access points with low <a href="/facts/Central_processing_unit/Jxp1bqMV">CPU</a> power, the open source <a href="https://web.archive.org/web/20150408143413/http://www.olsr.org/">OLSRd</a> project showed that large scale mesh networks can run with OLSRd on thousands of nodes with very little CPU power on 200 <a href="/facts/Megahertz/6Wshj5qm">MHz</a> embedded devices. </p><p>Being a link-state protocol, OLSR requires a reasonably large amount of <a href="/facts/Bandwidth_(computing)/lY6Tb4gX">bandwidth</a> and CPU power to compute optimal paths in the network. In the typical networks where OLSR is used (which rarely exceed a few hundreds of nodes), this does not appear to be a problem. </p><p>By only using MPRs to flood topology information, OLSR removes some of the redundancy of the flooding process, which may be a problem in networks with moderate to large packet loss rates<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> – however the MPR mechanism is self-pruning (which means that in case of packet losses, some nodes that would not have retransmitted a packet, may do so). </p> <h2 id="messages">Messages</h2> <p>OLSR makes use of "Hello" messages to find its one hop neighbors and its two hop neighbors through their responses. The sender can then select its multipoint relays (MPR) based on the one hop node that offers the best routes to the two hop nodes. Each node has also an MPR selector set, which enumerates nodes that have selected it as an MPR node. OLSR uses topology control (TC) messages along with MPR forwarding to disseminate neighbor information throughout the network. <i>Host and network association</i> (HNA) messages are used by OLSR to disseminate network route advertisements in the same way TC messages advertise host routes. </p> <h3>Hello</h3> <h3>Topology control (TC)</h3> <h2 id="other-approaches">Other approaches</h2> <p>The problem of routing in ad hoc wireless networks is actively being researched, and OLSR is but one of several proposed solutions. To many, it is not clear whether a whole new protocol is needed, or whether <a href="/facts/OSPF/PACpGUHb">OSPF</a> could be extended with support for wireless interfaces.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p><p>In bandwidth- and power-starved environments, it is interesting to keep the network silent when there is no traffic to be routed. Reactive routing protocols do not maintain routes, but build them on demand. As link-state protocols require database synchronisation, such protocols typically use the distance vector approach, as in <a href="/facts/AODV/DlMz6E7b">AODV</a> and <a href="/facts/DSDV/6jJbA3FW">DSDV</a>, or more ad hoc approaches that do not necessarily build optimal paths, such as <a href="/facts/Dynamic_Source_Routing/8a21TDLA">Dynamic Source Routing</a>. </p><p>For more information see the <a href="/facts/List_of_ad_hoc_routing_protocols/JgXy5kV9">list of ad hoc routing protocols</a>. </p> <h2 id="olsr-version-2">OLSR version 2</h2> <p>OLSRv2 was published by the IETF in April 2014 as a standards-track protocol.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> It maintains many of the key features of the original including MPR selection and dissemination. Key differences are the flexibility and modular design using shared components: packet format packetbb, and neighborhood discovery protocol NHDP. These components are being designed to be common among next generation IETF MANET protocols. Differences in the handling of multiple address and interface enabled nodes is also present between OLSR and OLSRv2. </p> <h2 id="implementations">Implementations</h2> <ul><li><a href="https://web.archive.org/web/20150408143413/http://www.olsr.org/">OLSR.ORG</a> – Downloadable code for OLSR on Linux, Windows, Mac OS X, FreeBSD, NetBSD and <a href="/facts/OpenBSD/xmPS9tek">OpenBSD</a> systems. Features a great deal of documentation, including an informative survey of related work.</li> <li><a href="http://cs.itd.nrl.navy.mil/work/olsr/index.php">NRL-OLSR</a> – Open source code of NRL-OLSR. Works on Windows, MacOS, Linux, and various embedded PDA systems such as Arm/Zaurus and PocketPC as well as simulation environments <a href="/facts/Ns_(simulator)/cSnWYPal">ns2</a> and OPNET., <a href="http://cs.itd.nrl.navy.mil/focus/">http://cs.itd.nrl.navy.mil/focus/</a></li> <li><a href="http://sourceforge.net/projects/wmolsr/">SOURCEFORGE.NET-OLSR</a> – Created by MOVIQUITY and based on studies within the project Workpad, it offers a code in C# to deploy a MANET (Ad Hoc, Meshnet) with protocol OLSR. Developed for WM 6, Win XP and can be adapted to other platforms using .Net Framework and Compact. <a href="http://sourceforge.net/projects/wmolsr/">http://sourceforge.net/projects/wmolsr/</a></li></ul> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/B.A.T.M.A.N./A5HjKNaa">B.A.T.M.A.N.</a>, Better Approach To Mobile Adhoc Networking</li> <li><a href="/facts/IEEE_802.1aq/xslEBCKB">IEEE 802.1aq</a></li> <li><a href="/facts/TRILL/7lHM52Xe">TRILL</a>, Transparent Interconnection of Lots of Links</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="https://web.archive.org/web/20130112003204/http://www.ietf.org/">IETF Home Page</a> The Internet Engineering Task Force standards body</li> <li><a href="http://olsr.funkfeuer.at">olsr.funkfeuer.at</a> currently advancing the olsr.org implementation to improve scalability</li> <li><a href="https://web.archive.org/web/20040912075427/http://hipercom.inria.fr/olsr/">Optimized Link State Routing</a>, which includes this <a href="https://web.archive.org/web/20051013011753/http://hipercom.inria.fr/olsr/mpr-flooding.html">Flash Demo</a>.</li> <li><a href="http://pyramid.metrix.net/">Pyramid Linux</a> – an embedded distro for <a href="http://metrix.net/">embedded x86 boards</a> with OLSR, web interface, etc. Primarily used in Community Networks.</li> <li><a href="http://cs.itd.nrl.navy.mil/focus/">NRL's Networks and Communication Systems Branch</a> – includes project information and open source networking tools and software developed by the U.S. Naval Research Lab.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Thomas Heide Clausen; Philippe Jacquet (October 2003). Optimized Link State Routing Protocol (OLSR). IETF. doi:10.17487/RFC3626. RFC 3626. Retrieved 22 October 2024. <a href="https://datatracker.ietf.org/doc/html/rfc3626" target="_blank">https://datatracker.ietf.org/doc/html/rfc3626</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Performance Comparison of Wireless Mobile AdHoc Network Routing - Arun Kumar, Lokanatha C. Reddy, Prakash S. Hiremath [clarification needed] <a href="/wiki/Wikipedia:Please_clarify" target="_blank">/wiki/Wikipedia:Please_clarify</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>M. Abolhasan; B. Hagelstein; J. C.-P. Wang (2009). Real-world performance of current proactive multi-hop mesh protocols. 15th Asia-Pacific Conference on Communications. <a href="http://ro.uow.edu.au/infopapers/736/" target="_blank">http://ro.uow.edu.au/infopapers/736/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Madhavi Chandra; Abhay Roy (March 2010). Extensions to OSPF to Support Mobile Ad Hoc Networking. IETF. doi:10.17487/RFC5820. RFC 5820. Retrieved 22 October 2024. <a href="https://datatracker.ietf.org/doc/html/rfc5820" target="_blank">https://datatracker.ietf.org/doc/html/rfc5820</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Richard Ogier; Phil Spagnolo (August 2009). Mobile Ad Hoc Network (MANET) Extension of OSPF Using Connected Dominating Set (CDS) Flooding. IETF. doi:10.17487/RFC5614. RFC 5614. Retrieved 22 October 2024. <a href="https://datatracker.ietf.org/doc/html/rfc5614" target="_blank">https://datatracker.ietf.org/doc/html/rfc5614</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Thomas Heide Clausen; Christopher Dearlove; Philippe Jacquet; Ulrich Herberg (April 2014). The Optimized Link State Routing Protocol Version 2. IETF. doi:10.17487/RFC7181. RFC 7181. Retrieved 22 October 2024. <a href="https://datatracker.ietf.org/doc/html/rfc7181" target="_blank">https://datatracker.ietf.org/doc/html/rfc7181</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> </ol>