|
Bugzilla – Full Text Bug Listing |
| Summary: | [feature request] NSC support of Ascii traciing | ||
|---|---|---|---|
| Product: | nsc | Reporter: | Yoshihiko <yoshiyaz> |
| Component: | core | Assignee: | ns-bugs <ns-bugs> |
| Status: | PATCH WANTED --- | ||
| Severity: | normal | CC: | sam.jansen, tomh |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Hardware: | PC | ||
| OS: | Linux | ||
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. Pinging nsc guys again: florian, sam, what do you think ? 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. |
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 10.0.0.2 > 10.0.0.1) Payload (size=1480)