Bug 1020 – Wrong usage of the originator sequence number in HWMP PREP

Bug 1020 - Wrong usage of the originator sequence number in HWMP PREP


Summary:	Wrong usage of the originator sequence number in HWMP PREP

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	devices
Version:	ns-3-dev
Hardware:	All All

Importance:	P4 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-10-28 00:50 UTC by Kirill Andreev
Modified:	2011-12-12 11:02 UTC (History)
CC List:	0 users

See Also:

Attachments
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 Kirill Andreev 2010-10-28 00:50:17 UTC

HanneloreSchi <m.porsch3000@web.de> wrote:

Hi,

I think I have found a functional bug in ns3 dot11s mesh code:
It occurs, that a PREP that comes directly from the requested STA is
rejected for its old SN, which is not logical.


In ReceivePrep():
prep.GetOriginatorSeqNumber () is used to obtain the Sequence number
of the STA that answered the previous PREQ.
But according to the 802.11s draft 11C.10.7 Path Reply (PREP) the
Originator SN is the SN of the STA that sent the PREQ. The Target SN
or Destination SN is the correct value of the requested SAT and so
prep.GetDestinationSeqNumber() should be used instead.


Could somebody confirm this and firmly file a bug?

Regards

Comment 1 Kirill Andreev 2011-12-12 11:02:01 UTC

Changeset 7631:ddd352da5c13