[Ns-bugs] [Bug 1299] New: EnableAsciiIpv4All tracing does not show transmitted and received packets

[code@nsnam.ece.gatech.edu]

https://www.nsnam.org/bugzilla/show_bug.cgi?id=1299

           Summary: EnableAsciiIpv4All tracing does not show transmitted
                    and received packets
           Product: ns-3
           Version: ns-3.12
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: internet
        AssignedTo: riley at ece.gatech.edu
        ReportedBy: santoshag at gmail.com
                CC: ns-bugs at isi.edu
   Estimated Hours: 0.0


Created attachment 1271
  --> https://www.nsnam.org/bugzilla/attachment.cgi?id=1271
first.cc example tutorial script with Ipv4 Ascii Tracing enabled

Overview:  ascii trace file generated using EnableAsciiIpv4 with
InternetStackHelper does not show transmitted or received packets but shows
dropped packets only if any.

Steps to Reproduce: As shown in the attachment script, one can generate ascii
tracing for Ipv4 interfaces with InternetStackHelper object. 
        InternetStackHelper stack;
        .....
    .....
        AsciiTraceHelper ascii;
    Ptr<OutputStreamWrapper> stream = ascii.CreateFileStream("ipv4_trace.tr");
    stack.EnableAsciiIpv4All(stream);

Actual Results: Trace file shows only dropped packet(marked as 'd') if any
Expected Results: SInce the simulation also had transmitted and received
packets, they should have been present in the trace file.

Build Date & Platform: Build Nov-16-2011 on Ubuntu OS 11

Additional Builds and Platforms: Seen on Fedora 

Additional Information: Tested with first.cc example tutorial file present in
ns-3.12 build. The trace file did not had anything since there are no dropped
packets in point-to-point link but the important point is, it did not even have
transmitted and received packets.

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