[Ns-bugs] [Bug 556] DcfManager does not handle AckTimeout properly when there are multiple queues

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=556





--- Comment #17 from Mathieu Lacage <mathieu.lacage at sophia.inria.fr>  2009-06-08 07:17:48 EDT ---
(In reply to comment #15)
> (In reply to comment #14)
> > This is the only meaningful change: the assoc req is sent exactly 15us later
> > 
> > -02:00:00.000950 950us tsft 6.0 Mb/s 2437 MHz (0x00c0) -59dB signal -101dB
> > noise Assoc Request () [6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 Mbit]
> > +02:00:00.000965 965us tsft 6.0 Mb/s 2437 MHz (0x00c0) -59dB signal -101dB
> > noise Assoc Request () [6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 Mbit]
> > 
> 
> In both cases, we observe the same scenario: ":05" sends assoc req twice to
> ":03", first fails with ack timeout because ":03" is busy receiving another req
> from ":04", second is the one we see here. the difference between the two
> scenarios is 15.666us.
> 

Ok, this change is indeed compatible with the specification I believe: 15.666 =
9 (slot) + 2*1000 / 300000000 (round trip of 1000m if speed of light is
300000000m/s for max propagation delay) is the extra time which an ack timeout
lasts compared to the nav setting.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.