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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Prevent<strong>in</strong>g Replay Attacks for Secure Rout<strong>in</strong>g <strong>in</strong> Ad Hoc Networks 147Fig. 3. Measur<strong>in</strong>g RTTHello messages periodically to assure neighbors that the l<strong>in</strong>ks between them arestill alive. We use a slightly modified Hello message (RTT REQ) <strong>by</strong> <strong>in</strong>clud<strong>in</strong>ga flag to request for an immediate reply (RTT REP). By send<strong>in</strong>g such a specialHello after every n Hello’s, each node should get the RTT to each trustedneighbor <strong>by</strong> subtract<strong>in</strong>g the receiv<strong>in</strong>g time of RTT REP <strong>by</strong> the send<strong>in</strong>g time ofRTT REQ. Trusted neighbors are those neighbors that have passed verification.At the beg<strong>in</strong>n<strong>in</strong>g all neighbors are set as trusted because we assume there is noreplay due to the spontaneous nature of the ad-hoc network. The RTT thresholdis calculated <strong>by</strong> averag<strong>in</strong>g the RTT’s to all trusted neighbors and add<strong>in</strong>g amarg<strong>in</strong> depend<strong>in</strong>g on the str<strong>in</strong>gency of security. RTT REP messages also needto be slightly different to be dist<strong>in</strong>guished from other common Hello’s. To reduceoverhead, RTT Hello’s do not need to be encrypted or signed because neitherconfidentiality nor <strong>in</strong>tegrity is required (it is only with<strong>in</strong> one-hop range). But arandom number or time-stamp should be added to each RTT REQ to be embedded<strong>in</strong> the RTT REP to prevent fake replies.For the nodes that currently do not have any route to ma<strong>in</strong>ta<strong>in</strong> and thus arenot broadcast<strong>in</strong>g Hello’s, RTT Hello’s are required to ma<strong>in</strong>ta<strong>in</strong> RTT thresholdsfor themselves. S<strong>in</strong>ce RTT Hello’s have much longer <strong>in</strong>terval, the overhead willbe m<strong>in</strong>imum.5 AnalysisIn this section, we give a mathematical analysis of the overhead caused <strong>by</strong> neighborverification procedures. The overhead caused <strong>by</strong> RTT Hello is ignored s<strong>in</strong>cethey are just Hello packets that need immediate responses.Suppose <strong>in</strong> a network of N nodes, each node has neighbor change rate X,i.e., after a specific period of time, X percent new neighbors need to be verified.Also, we suppose dur<strong>in</strong>g this period of time M RREQ’s are processed.We can deem X as the probability of the verification be<strong>in</strong>g launched <strong>in</strong>one-hop range. If the average length of routes <strong>in</strong> the network is Y hops, thenaccord<strong>in</strong>g to B<strong>in</strong>omial distribution the probability of the verification be<strong>in</strong>g held<strong>in</strong> only one hop is:P 1 = ( )Y1 X 1 (1 − X) (Y −1) (1)The probability of i hops be<strong>in</strong>g verified is:P i = ( )Yi X i (1 − X) (Y −i) (2)where 0 ≤ i ≤ Y . Suppose the time consumed at each hop is t if no verificationis needed, 3t if the verification is applied (one RREQ(t) and one RTT(2t)), then

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

Saved successfully!

Ooh no, something went wrong!