installing diff. versions of NS2 in the same machine?how to make the modification?

shojaru · 05-22-2009, 12:47 AM

I want to simulate some network topology in NS2. I found different types of patches and files for different purpose. so, can I install all the different versions I need, on the same machine, and run them as I need ; I mean, maybe one patch for voice simulation or the other for MPEG video transmission?
also, can I modify my existing ns2.33 by just copying the Modified mac folder of ns2.28 ( which I received by email from a friend ) ? what command should I use for the modification to take place?

knudfl · 05-26-2009, 01:35 PM

It would be possible to have more than one version
of ns2. Just keep them in different locations in
/home/"username"/dir-1/ns2 .... dir-2/ns2/ , and
use all-in-one versions.
Then they will all have a unique PATH, and 'ns'
is to be used as './ns' inside that version,
thus not being disturbed by the other versions.
.....
Modifying ns-2.33, suggest : set up a new unpacked
ns-allinone-2.33 in /home/"username"/, and use that
for the experiments with additional software.
.....

hhgh · 03-15-2012, 10:24 PM

Hi knudfl,

I have installed two versions of NS2 (ns2.28 and ns2.35) in two different directories on Linux CentOS 6, as followings.

Firstly installed, ns2.35: /usr/local/ns-allinone-2.35/
Secondly installed, ns2.28: /usr/local/ns228/ns-allinone-2.28/

How can I put the unique PATH for two versions?
Apparently; for me it is not unique. Because, when I run ./ns inside the (/ns2.28) directory, it is using/invoking the NAM version 1.15 which belongs to ns2.35 instead of using NAM version 1.11.

Thank you in advance,

knudfl · 03-16-2012, 06:44 AM

Post #3.

1) None of your installed versions of ns-allinone can be added to a *PATH,
when you have more than one version.
And : Adding any ns2 *PATH to .bashrc : Not required on Linux.
The binary 'ns' is hard coded to know the location of the libraries.

2) Use a better nam than version 1.15 : The identical 1.14 works better.
The only change that was intended for 1.15 : Can now compile with tcl8.5.
Also : Nam is a separate application. Any nam can be used for any ns2.

A static nam 1.14
32bits https://docs.google.com/open?id=0B7S...k4NGI5NzliM2Ux
64bits https://docs.google.com/open?id=0B7S...NiYjY0ODE1YmQw
Unpack nam-1.14-<arch>.tar.gz, and copy 'nam' to /usr/local/bin/
This nam requires no ns2 libraries: Will even work on an OS with no ns2, no tcl !

All binaries 'ns' can be also be copied to /usr/local/bin/ : One named ns.
And, examples : ns228 (ns228.orig) ns228+<patch-name> ns235, etc.

P.S. : The default build location is /home/<name>/<ns2> :
All ns2 commands should be run as unprivileged user. No 'root'.
'root' is for administrative tasks only.

.