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.

156 M. Just, E. Kranakis, and T. Wannode is BAD if it responds to probe messages dest<strong>in</strong>ed to itself but fails <strong>in</strong> forward<strong>in</strong>gprobe messages for others. A benign l<strong>in</strong>k failure may also be detected as BAD behaviorif it is not cleared <strong>by</strong> other mechanisms (e.g., route error <strong>in</strong> DSR). A node is consideredDOWN if 1) it is a neighbor node to the prob<strong>in</strong>g node and it doesn’t respond to probemessages; or 2) it is not a neighbor node and it doesn’t respond to probe messagesthrough all the known paths. A node is considered at the UNKNOWN state if on allknown paths from the prob<strong>in</strong>g node to the node, there exists at least one node <strong>in</strong> BADor DOWN state.3.2 AssumptionsProbe messages are <strong>in</strong>dist<strong>in</strong>guishable from normal packets. One limitation of the prob<strong>in</strong>gtechnique is that it can be easily defeated if probe messages can be dist<strong>in</strong>guishedfrom normal data packets. For example, a malicious node may forward probe messages,but drop all the other data packets, there<strong>by</strong> avoid<strong>in</strong>g detection. This assumption can berealized us<strong>in</strong>g end-to-end encryption of IP payload <strong>by</strong> pair-wise shared keys. S<strong>in</strong>ce amalicious node can understand only the IP header, it does not have the <strong>in</strong>formation ofupper layer protocols, such as TCP/UDP port numbers. By implement<strong>in</strong>g the prob<strong>in</strong>gtechnique above the network layer (e.g., based UDP), an adversary will not be able todist<strong>in</strong>guish a probe message from a other data packet (e.g., HTTP or SMTP packet).Some other options are: 1) piggyback<strong>in</strong>g a probe message on a normal data packetwhich requires acknowledgment, such as TCP SYN. The disadvantage is that such datapackets may not be available dur<strong>in</strong>g the time of prob<strong>in</strong>g. 2) assum<strong>in</strong>g that an adversarycannot modify the forward<strong>in</strong>g software of the compromised router. Therefore, theadversary can only make decisions based on IP addresses, which does not allow fordist<strong>in</strong>guish<strong>in</strong>g a probe message from a normal data packet.Multi-hop source rout<strong>in</strong>g protocols. The prob<strong>in</strong>g technique assumes a multi-hopsource rout<strong>in</strong>g protocol s<strong>in</strong>ce a prob<strong>in</strong>g node needs to specify the source route <strong>by</strong> whicha probe message takes to get to the dest<strong>in</strong>ation. This assumption is practical s<strong>in</strong>ce somerout<strong>in</strong>g protocols, such as Dynamical Source Rout<strong>in</strong>g (DSR) [16], are multi-hop sourcerout<strong>in</strong>g protocols.Bi-directional communication l<strong>in</strong>ks. We assume that all communication l<strong>in</strong>ks arebi-directional. This assumption is practical <strong>in</strong> some wireless networks, such as IEEE802.11 [1], where all l<strong>in</strong>ks have to be bi-directional for l<strong>in</strong>k layer acknowledgment towork.4 The Distributed Prob<strong>in</strong>g SchemeIn order to monitor the behavior of mobile nodes <strong>by</strong> the prob<strong>in</strong>g technique, we needto decide which node should probe and how far it should probe. Given a network withn nodes, there are several <strong>in</strong>terest<strong>in</strong>g possibilities: 1) there is only one prob<strong>in</strong>g nodeand it probes all the other nodes; 2) there are k prob<strong>in</strong>g nodes (1

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

Saved successfully!

Ooh no, something went wrong!