Bug 1194 – Incorrect RERR processing

Bug 1194 - Incorrect RERR processing


Summary:	Incorrect RERR processing

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	aodv
Version:	pre-release
Hardware:	All All

Importance:	P5 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-06-22 18:07 UTC by John Abraham
Modified:	2011-07-08 06:30 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
RERR (1.04 KB, patch) 2011-06-22 18:07 UTC, John Abraham	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description John Abraham 2011-06-22 18:07:56 UTC

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).

Comment 1 Tom Henderson 2011-06-28 16:15:33 UTC

+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.