This site uses cookies. By continuing to use this site you agree to our use of cookies. To find out more, see our Privacy and Cookies policy.
Paper The following article is Open access

Performance of Routing Protocol OLSR and BATMAN in Multi-hop and Mesh Ad Hoc Network on Raspberry Pi

, , , and

Published under licence by IOP Publishing Ltd
, , Citation Wardi et al 2020 IOP Conf. Ser.: Mater. Sci. Eng. 875 012046 DOI 10.1088/1757-899X/875/1/012046

1757-899X/875/1/012046

Abstract

Ad hoc network is a network where each node can act as a terminal and also as a router. Ad hoc technology does not require infrastructure that controls communication systems centrally. Therefore, each node on the ad hoc network can manage itself. This study aims to design nodes that can be used for communication on wireless ad hoc networks then compare the networks performance on OLSR and BATMAN routing protocols. There are four performance parameters used, namely Throughput, Round Trip Delay (RTD), Packet Delivery Ratio (PDR), and Convergence Time. The topology used includes P2P communication and multi-hop communication. Network performance testing is done both for P2P and multi-hop communication on MESH networks. Convergence Time Testing is done only for multi-hop communication to find out the time needed by the protocol to repair the path when a path fail occurs. The test results show that OLSR gives a better average value of throughput compared to BATMAN. Whereas RTD shows that the BATMAN routing protocol is better compared to OLSR. Both protocols, OLSR and BATMAN, successfully received all data packets sent by the source node on P2P communications. Failure to send data packets occurs in multi-hop communication as indicated by a PDR value of 98% for the OLSR protocol and 95% for the BATMAN protocol.

Export citation and abstract BibTeX RIS

Content from this work may be used under the terms of the Creative Commons Attribution 3.0 licence. Any further distribution of this work must maintain attribution to the author(s) and the title of the work, journal citation and DOI.

Please wait… references are loading.
10.1088/1757-899X/875/1/012046