Bug 585 – NAV bug

Bug 585 - NAV bug


Summary:	NAV bug

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	wifi
Version:	ns-3.4
Hardware:	All All

Importance:	P5 normal
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-06-08 08:37 UTC by Kirill V. Andreev
Modified:	2009-06-19 03:04 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
propsed fix (390 bytes, patch) 2009-06-08 08:37 UTC, Kirill V. Andreev	Details \| Diff
Correct patch, sorry for previous :) (839 bytes, patch) 2009-06-08 08:40 UTC, Kirill V. Andreev	Details \| Diff
Show Obsolete (1) 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 V. Andreev 2009-06-08 08:37:59 UTC

Created attachment 459 [details]
propsed fix

NAV must not be set to itself (see setting and resetting NAV of 802.11 -2007).
I have only removed setting NAV to itself, but now I think, that it is not reasonable to pass any information to DcfManager, because I do not know, what shall we do when frame exchange terminates earlier (for example, what shall we do if there is no data goes after CTS?) that it was declared (Standart says, that we may pass one more frame of the sae queue, but I do not know how exactly we shall implement this, because I did not work with frame exchange sequences, except CTS/RTS), So the patch below only solves a problem with NAV.

Comment 1 Kirill V. Andreev 2009-06-08 08:40:59 UTC

Created attachment 460 [details]
Correct patch, sorry for previous :)

This is a correct patch

Comment 2 Mathieu Lacage 2009-06-08 09:15:02 UTC

why don't you want to pass information to DcfManager anymore ?

Comment 3 Kirill V. Andreev 2009-06-08 10:00:58 UTC

Now chapter 9.9.1.4 is not implemented at all, so, passing information to DcfManager is unneded now. The second problem - how to determine the ond of frame exchange sequence and its failure

Comment 4 Mathieu Lacage 2009-06-09 03:23:53 UTC

(In reply to comment #3)
> Now chapter 9.9.1.4 is not implemented at all, so, passing information to
> DcfManager is unneded now. The second problem - how to determine the ond of
> frame exchange sequence and its failure

I am sorry but I cannot parse this sentence: can you rephrase what you mean here ?

Comment 5 Kirill V. Andreev 2009-06-16 12:29:15 UTC

Sorry for late reply.
I think, that chapter 9.9.1.4 is not implemented at all at the moment, so there is no reason to pass information about remaining NAV to DcfManager. Also I have now idea about catching situations, when frame exchange sequence was interrupted (due to collision, for example)

Comment 6 Mathieu Lacage 2009-06-19 03:04:42 UTC

changeset 19c0844361f3