[Ns-bugs] [Bug 564] New: Tags gone crazy, no clue about the issue

[code@nsnam.ece.gatech.edu]

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

           Summary: Tags gone crazy, no clue about the issue
           Product: ns-3
           Version: ns-3-dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P5
         Component: applications
        AssignedTo: ns-bugs at isi.edu
        ReportedBy: tommaso.pecorella at unifi.it
   Estimated Hours: 0.0


Created an attachment (id=436)
 --> (http://www.nsnam.org/bugzilla/attachment.cgi?id=436)
examples/stats application modified to show the "bug"

Ok, maybe I'm a total newbie, maybe I found a serious bug. In the first case
I'll get the shame on me.

Anyway, I was trying to modify the example/stats in order to show the packet
loss due to channel congestion, so I did the following things:
1) modified the sender application to send an unicast packet instead of a
broadcast,
2) changed the sender application to calculate the send interval according to a
fixed DataRate (more intuitive and ease the plotting),
3) changed the main simulation code to use an AP and a STA (I wanted to add
more STAs).

Add some more "patches" to the Receiver application in order to show is a
TimeTag is missing in action (you never know).

Result (with 1 AP and 2 STAs):
Sending packet at 1000000000ns to 192.168.0.1 -- Time Interval is: 8000000000ns
Sending packet at 1000000000ns to 192.168.0.1 -- Time Interval is: 8000000000ns
Sending packet at 9000000000ns to 192.168.0.1 -- Time Interval is: 8000000000ns
Sending packet at 9000000000ns to 192.168.0.1 -- Time Interval is: 8000000000ns
Sending packet at 17000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 17000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
** missing time tag **
Sending packet at 25000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 25000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 33000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 33000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
** missing time tag **
Sending packet at 41000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 41000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
** missing time tag **
Sending packet at 49000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
Sending packet at 49000000000ns to 192.168.0.1 -- Time Interval is:
8000000000ns
** missing time tag **

This is driving me crazy. How can an application's receive function be called
with a corrupted packet ? How can a tag go missing in action ?

Cheers


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