[Ns-developers] ns-3 nam support

[Jeremy]

Tom & Mathieu,

Based on the traces for nam in ns-2, I expect that making it possible for
iNSpect to handle these traces should be relatively minor. I doubt that any
extensions to the format would be very necessary even.

As far as I remember, the nam trace does not handle mobile nodes though. If
that is still correct, we would still need to figure out wireless. Maybe
simply extending nam to include wireless info (movement, etc) would be
enough.

Unfortunately, I personally wont be able to look into this specific issue
very deeply until next week. In the meantime, I will have someone start
looking into this (we have an iNSpect team again).

-Jeremy




On Mon, Aug 25, 2008 at 11:23 PM, Tom Henderson <tomh at tomh.org> wrote:

> Mathieu Lacage wrote:
>
>> hi,
>>
>> There were lots of question about nam support for ns-3 at the sigcomm
>> demo: tom managed to convince me to take a shot at this and see what we
>> could do. See http://code.nsnam.org/mathieu/ns-3-nam
>>
>> src/contrib/nam-helper.h is the API and it seems to work reasonably well
>> for point to point links.
>>
>
> About a month ago, Jeremy was asking about what trace file format that ns-3
> could settle upon for use by iNSpect.  I'm wondering whether nam format
> could be extended or tweaked slightly for use by both tools.
>
> Jeremy, what is the suitability of (possibly extended) nam trace formats
> for iNSpect?
>
> Tom
>



-- 
Curiosity didn't kill the cat, it taught it something it didn't know before.