Optimized Link State Routing Protocol: Difference between revisions

Revision as of 20:23, 27 May 2013

Revision as of 09:20, 28 May 2013

Line 19:

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 [[Central processing unit|CPU]] power, the open source [http://www.olsr.org OLSRd] project showed that large scale mesh networks can run with OLSRd on thousands of nodes with very little CPU power on {{val|200|ul=MHz}} embedded devices.

Being a link-state protocol, OLSR requires a reasonably large amount of [[Bandwidth (computing)|bandwidth]] 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.

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<ref>{{cite journal|author=M. Abolhasan, B. Hagelstein, J. C.-P. Wang|title=Real-world performance of current proactive multi-hop mesh protocols|year=2009|url=http://ro.uow.edu.au/infopapers/736/}}</ref> – 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).