|
Bugzilla – Full Text Bug Listing |
| Summary: | Incorrect RERR processing | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | John Abraham <john.abraham.in> |
| Component: | aodv | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | tomh |
| Priority: | P5 | ||
| Version: | pre-release | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | RERR | ||
+1 to commit. The combination of bug fixes to 1193 and 1194 produces a significant improvement in the manet-routing-example output. Example (time 199 in the manet-routing-example.csv output): Old: 199,0,0,10,AODV,7.5 (0 packets received) New: 199,20.48,40,10,AODV,7.5 (40 packets received) They also make the program run a lot faster. |
Created attachment 1170 [details] RERR When RERR is received at Node B from Node A about some unreachable destination Node C, this does not always mean Node C is not a neighbor with Node B. But Currently B checks if the unreachable destination is a neighbor and proceeds to Break Link processing 1. Let the neighbor adjacency management deal with removing C, by timing out and subsequently breaking the link, rather forcibly breaking the link when A says C is not reachable 2. Let InvalidateRoute deal with route invalidation (this is already the case).