Bug 462 - [feature request] NSC support of Ascii traciing
[feature request] NSC support of Ascii traciing
Product: nsc
Classification: Unclassified
Component: core
PC Linux
: P5 normal
Assigned To: ns-bugs
Depends on:
  Show dependency treegraph
Reported: 2009-01-08 20:00 EST by Yoshihiko
Modified: 2012-03-27 14:20 EDT (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Yoshihiko 2009-01-08 20:00:19 EST
1) tcp-nsc-lfn.cc modified follows

--- examples/tcp-nsc-lfn.cc	2008-12-05 11:09:02.000000000 +0900
+++ scratch/tcp-nsc-lfn.cc	2009-01-08 17:40:42.000000000 +0900
@@ -135,7 +135,7 @@
   // This tells ns-3 to generate pcap traces.
-  PointToPointHelper::EnablePcapAll ("tcp-nsc-lfn");
+  PointToPointHelper::EnableAsciiAll (std::cout);
   Simulator::Stop (Seconds(900));
   Simulator::Run ();

2) run tcp-nsc-lfn.cc then print follows

r 5.5385 /NodeList/0/DeviceList/0/$ns3::PointToPointNetDevice/Rx ns3::PppHeader (Point-to-Point Protocol: IP (0x0021)) ns3::Ipv4Header (tos 0x0 ttl 64 id 31 protocol 6 offset 0 flags [none] length: 1500 > Payload (size=1480)
Comment 1 Mathieu Lacage 2009-06-22 07:01:04 EDT
There is no way to make this work I think. The data is in the packet, but we can't display it because the TCP layer did not tell us about it.

Maybe the nsc glue could hack this. Re-assigning to nsc.
Comment 2 Mathieu Lacage 2009-11-23 09:21:12 EST
Pinging nsc guys again: florian, sam, what do you think ?
Comment 3 Sam Jansen 2009-11-24 17:33:33 EST
I don't remember all the details available. If we know the packet has NSC info in it, then we can parse out the TCP header (I did something similar for ns-2 some time ago).

I can have a look at this next week. I agree it would certainly be desirable to have this work.