13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Prevent<strong>in</strong>g Replay Attacks for Secure Rout<strong>in</strong>g <strong>in</strong> Ad Hoc Networks 141the route pass<strong>in</strong>g through this tunnel will appear to be the shortest and thusgets selected. Consequently, attacker nodes at either ends of the tunnel can drop,delay or modify packets. We also identify a new type of replay attack that canoccur on the AODV protocol - the RREQ Flood<strong>in</strong>g attack. In this type, attackerscan generate extra route discoveries <strong>by</strong> tak<strong>in</strong>g advantage of the “expand<strong>in</strong>g r<strong>in</strong>g”propagation of RREQ’s <strong>in</strong> that not all nodes have the knowledge that the RREQhas been processed. If performed massively, these packets will result <strong>in</strong> a numberof unnecessary resource-consum<strong>in</strong>g route discoveries.Our technique is based on strengthen<strong>in</strong>g the neighbor authentication mechanism<strong>by</strong> a simple extension to the AODV protocol <strong>in</strong> order to determ<strong>in</strong>e if thesource nodes of RREQ packets are really <strong>in</strong> the neighborhood. By measur<strong>in</strong>g theRound Trip Time (RTT) between two nodes and compar<strong>in</strong>g the RTT value withan adaptive threshold, we can choose to discard or process the received RREQ.The threshold is calculated <strong>by</strong> requir<strong>in</strong>g special Hello packets be<strong>in</strong>g replied immediately<strong>in</strong>stead of periodically. Analysis of the technique <strong>in</strong>dicates that itachieves security with little overhead.The rest of the paper is organized as follows. Section 2 provides an overviewof attacks on the AODV protocol and describes the two types of replay attacks.Section 3 surveys related work <strong>in</strong> this area. Section 4 describes the proposedapproach. Section 5 gives a probabilistic analysis of the technique to provide anestimation of the overhead. Section 6 provides a discussion of the proposal andconclud<strong>in</strong>g remarks.2 Attacks on the AODV Protocol2.1 Overview of AODVBriefly, the AODV rout<strong>in</strong>g protocol works as follows [2]. A node broadcasts aRoute Request (RREQ) if it wants to communicate with another node and novalid route is found <strong>in</strong> its rout<strong>in</strong>g table. The RREQ has the latest sequencenumber of the orig<strong>in</strong>ator,an RREQ ID (or broadcast id) to mark that it hasnot been processed, and the latest sequence number of the dest<strong>in</strong>ation that theorig<strong>in</strong>ator has <strong>in</strong> its rout<strong>in</strong>g table. Each <strong>in</strong>termediate node <strong>in</strong>crements the hopcount field <strong>in</strong> RREQ <strong>by</strong> one and broadcasts this RREQ until the RREQ reachesthe dest<strong>in</strong>ation or a node that has a higher dest<strong>in</strong>ation sequence number than theone <strong>in</strong> the packet. Multiple replies (Route Replies - RREP’s) may be generatedand transmitted along the reverse path. Each <strong>in</strong>termediate node <strong>in</strong>crements thehop count <strong>in</strong> RREP and updates its rout<strong>in</strong>g table if the RREP has a highersequence number of the dest<strong>in</strong>ation or a shorter hop count. This cont<strong>in</strong>ues untilthe RREP arrives at the orig<strong>in</strong>ator.2.2 Known Attacks on AODVA variety of known attacks on the AODV protocol have been identified [4,7,11,12,15,16].

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!