|
Bugzilla – Full Text Bug Listing |
| Summary: | AODV originates new RREQ on each packet, when doesn't have valid route. | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Elena Buchatskaya <sunnmy> |
| Component: | aodv | Assignee: | Elena Buchatskaya <sunnmy> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs, tomh |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 940 | ||
| Attachments: |
test case
proposed patch |
||
Created attachment 954 [details]
proposed patch
changeset 5dbb70a41b85 |
Created attachment 953 [details] test case The problem is that AODV in DeferredRouteOutput does not check that route is already looking for and always sends new RREQ. In accordance with RFC 3561: "After broadcasting a RREQ, a node waits for a RREP (or other control message with current information regarding a route to the appropriate destination). If a route is not received within NET_TRAVERSAL_TIME milliseconds, the node MAY try again to discover a route by broadcasting another RREQ." Here is a test case, changing the example in src/routing/aodv.cc to use a UDP application instead of ICMP to generate more packets per second.