Beruflich Dokumente
Kultur Dokumente
MANET
Mobile ad hoc network
Mobile SelfSelf-configured on the fly No infrastructure Collection of hosts with wireless interface Physical constraint Quick deployment Economic concern Emergency (earthquake flood) (earthquake,
Nguyen Tuan Nam/WNC 2010 2
Problem
Communication range? Which path to take? Link changed frequently No dedicated server/router
Location awareness
Nguyen Tuan Nam/WNC 2010 4
Issues
C Correctness/Reliability / l bl Overhead
Fairness Selfishness Transmission range vs density Membership Security
Bandwidth Power
Simplest algorithm?
131.179.192.4
131.179.192.5
131.179.192.7
How?
Find a path Maintain paths
Nguyen Tuan Nam/WNC 2010 9
Route Request
Source needs to send packet to
destination Source initially discovers the route:
Send a broadcast RREQ RREQ is propagated to destination using flooding Recorded the node when RREQ goes through Destination knows the path
Nguyen Tuan Nam/WNC 2010 10
RREQ
7 knows the path, path but 2 still not!!! 2,3 1 2 3 2 2 2 need to send Data to 7 Will 7 always receive RREQ from 2 if graph connected? 2,3 5 How to avoid looping of RREQ? Will all neighbors receive RREQ? 4 2,3,5,6 2,3,4 6 2,3,5 Duplicate RREQ? 7
11
Route Reply
Destination needs to inform the source
Use the reverse path (RREP contains the newly discovered path) Initiate another RREQ back to the source Q
about the newly discovered path RREP How to send back the RREP?
12
7 7,6,5,3,2
13
2,3,5,6,7
15
Quiz
How long is the connection setup? To reduce the connection setup time,
should we attach the first data packet into the RREQ packet? Will the path work forever? How do we know when we need a new path?
16
RERR
Assume we f d a path (x1, x2, x3, x4, x5) found h( 2 3 ) x1 starts to use the path to transmit data to x5 If the link between x3 and x4 is broken How about the data packets arrived at x3?
Cant forward the data packets to x4 x3 need to notify the source x1. How? Send RERR packet back to x1
Drop Self-recover Self Send using alternate route in cache (salvaging) (salvaging) Gratuitous route repair: source piggybacks RERR in repair: source the next RREQ to clean up caches of other nodes
Nguyen Tuan Nam/WNC 2010 17
Quiz
How do we detect if the link between the
2 nodes is broken?
18
19
Quiz
How do we detect if the link between the
2 nodes is broken if there is no support from the data link layer?
20
Route Maintenance
If the source receives RERR it needs to
find a new route to the destination Re-send RREQ Re Everything repeat
21
Optimization
Before fl d RREQ f flooding Q Route cache:
Check if the destination is in the route cache Each node checks cache before sending RREQ RREQ packets are saved in the cache of each intermediate node Early return of RREP. Any problem? Eavesdrop RREQ to update local cache Eavesdrop RERR to update local cache Eavesdrop Data to send gratuitous RREP If packet can be routed via itself to gain a shorter route
Nguyen Tuan Nam/WNC 2010 22
Promiscuous mode:
Quiz
In the RREQ step, which network better:
Sparse network p Dense network
23