scenario and traffic file generation

[SS]

Hi Knudfl Sir,

Does it make a difference if we create a scenario/traffic files in NS-2.35 installation for unpatched OLSR or on NS-2.35 with OLSR protocol installed on it?

Thanks 

[knudfl]

Hi.

No "ns-2.35" is required for creation of a scenario/traffic files.

Needed for movement file :  /usr/local/bin/setdest

Or use bonnmotion http://sys.cs.uos.de/bonnmotion/

or sumo ( 0r any tool for creating a movement file.)

Needed for a traffic file : E.g. the file `cbrgen.tcl´ in any location.

Example location : /home/name/ns2/setdest/cmu-scen-gen/cbrgen.tcl

... and a reliable ns command, e.g. /usr/local/bin/ns235-olsr

Besides that, ns-2.35/ isn't required for anything after the creation of ns, setdest, etc. commands.

'make install' will usually copy those to /usr/local/bin/.

( I have had about 200 ns-2.xx, all deleted after copying "ns-name" to /usr/local/bin/.)

See ns2-INFO.txt

[shell s]

Thanks a lot sir for your insights...

Means, once we have successful running NS installation, irrespective of any particular routing protocol installation, we can create scenario/traffic file any way.....even with any copy of ns available in  "/usr/local/bin/ns-any-name" and later scenario/traffic files could be used to run simulation with any routing protocol in MANET.

--
You received this message because you are subscribed to the Google Groups "Network Simulator 2 (NS2)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-users+u...@googlegroups.com.
To post to this group, send email to ns-u...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-users.
For more options, visit https://groups.google.com/d/optout.

[knudfl]

You can "create scenario/traffic files" like said in my previous post.

The executable 'setdest' is an extra application, usually not patched by adding extra protocols.

... But you will easily experience, if the movement file isn't created.

Not all "ns-any_name" can be used with cbrgen.tcl, AFAIK. ( An OLSR patched ns is probably OK.)

I always keep a clean /usr/local/bin/"ns-orig", e.g. `ns235-orig´.

There is no limit for the numbers of installed ns2, so why not save a clean not-patched executable ?

See ns2-INFO.txt .

[cherifi...@gmail.com]