[Click] ns2 traces - ToNSTrace patch

[Eddie Kohler]

Hi Michael,

This looks neat!  I'll apply shortly.  One quick question about element 
naming.  Is ToNSTrace the right name for this element?  I would have thought 
that an element named ToNSTrace would generate *its own*, ns-compatible trace 
file, allowing a regular Click configuration (user-level driver, not ns 
driver) to generate an NS-compatible trace file.  What do you think?  Maybe 
this element should be called ToSimTrace, by analogy with ToSimDevice etc.? 
What are your thoughts?

Eddie


Michael Voorhaen wrote:
> Hi Eddie,
> 
> In attachment are some patches for click and nsclick to add tracing from click 
> to ns2 compatible traces. Example tcl files are also attached to show how the 
> element (ToNSTrace) can be used (tonstrace.click, tonstrace.tcl). A ns2 trace 
> file called tonstrace.tr is generated.
> 
> The patch files:
> tonstrace.click.patch (the patch for click_cvs)
> tonstrace.nsclick.patch (the patch for nsclick: ns-2.29 + nsclick patch 
> already applied)
> tonstrace.ns-2.29.patch (an updated version of ns-2.29.patch)
> 
> The last patch also includes a small fix for ns-2.29/tcl/lib/ns-clicknode.tcl 
> that makes sure that the node is also added to the channel object in ns2. 
> This fixes a segmentation fault related to wireless scenarios where the 
> GridKeeper object is not used.
> 
> Regards,
> Michael