Sorry. I have never installed any version of suse. I don't currently run any "serious" software on any 64-bit Linux distributions, although others have reported success.

Bottom line: There is no way for me to reproduce your problem (even if I had some clue as to the nature of your tcl script), so I can't see how I could help.

Do other tcl scripts work? Did you do the verification tests after completing the "make"?

Have you tried it with an official release of ns (rather than the release candidate that is indicated in your post)?

There is a users mailing list" http://www.gidforums.com/newreply.ph...reply&p=63366I

Maybe you can browse their archives for relevant posts. Or join the list and submit your question there.


Regards,

Dave

Thanks a lot mate....
however I ran some simulations and discovered that NAM works well....
I just wonder what those errors meant and if they will affect my work later...
Thanks anyway

Please I'm trying to view trace files in graphs format....
I believe the xgraph libs are responsible for that....
Do you know what command I should use?
Thanks.

regards,

Brenda
Edit/Delete Message

If you ran the allinone installation program and followed all instructions at the end of the installation script and if you ran ./validate from the ns directory and it reported everything OK, then your installation is good.
Oh, I just now saw what you were trying to when you got the tcl error. It doesn't work that way. From the ex directory you can run example.tcl from the command line (not from inside ns).

To see any kind of pretty graphical type of output, you use nam.

I draw your attention to the following, from http://www.linux.com/feature/55614:

"Windows-based simulators like Opnet and OMNeT, making a simulation scenario is as easy as dragging and dropping the required network components onto a workspace. In order to make a simulation scenario with ns-2, however, one has to learn OTcl in some detail, and that means the learning curve to use ns-2 can be quite steep
...
The built-in tutorials provide an in-depth understanding of networks, their different protocols, and layer functions. For research, you will have to tinker with the C++ files that work in the background, and that can be mind-boggling at times. However, user support via mailing lists is excellent. Posted questions are usually answered in 24 hours, and that is one of the reasons why I chose ns-2 instead of OMNeT.
...
I advise anyone planning to try ns-2 to have patience and be ready for a lot of experimentation and tinkering. ."


In other words, you will have to work for it.

The advice that I gave in some previous posts still stands: Start with a tutorial, like Marc Greis's: http://www.isi.edu/nsnam/ns/tutorial/index.html


I don't know of any shortcuts to getting results (let alone pretty results) from ns.

Regards,

Dave

I'm a fast learner and very good with programming languages...
I'm currently reading Marc Greis's tutorial and 3 other tutorials...
Thanks for the heads up...
Dave can I please ask you one last thing....
I'm trying to simulate a VoIP core network and carry out measurements based on VoIP QoS parameters...jitter, throughput, latency, e.t.c
I wanna connect 3-4 WAN models to a core network (both ATM and gigabit ethernet core, seperately) which consists of routers...
Can you pls give me an idea of how to go about this using NS-2...
what would my tcl scripts look like?
how many nodes do i need for each WAN and how can I interconnect the nodes within a WAN to depict a proper WAN model?
how can I use tcl scripts to configure a core network which consists of routers and manage traffic?
can you pls give me scripts that show traffic generation for VoIP networks?
Please I hope you can help or point me in the right direction.
I mailed ns user's list and for 2 days now, no reply on my query...
Thanks

Regards,

Brenda

I am not into ns all that much at this time. I responded to a number of requests on this list to try to help people get the program(s) installed and to get the installations validated, but that's about as far as I can go (for now).

I keep hoping that people with some specific experience will jump in to answer questions like yours with some practical examples.

Sorry.

Regards,

Dave

Thanks all the same...your help is greatly appreciated

Hello people

I'm newbie about installing ns-2, I read carefully all the threads posted by Dave (davekw7x) and I followd his instructions in order to install the ns-allinone-2.31 package unfortunately I could't succed, so I hope you can give me some tips about it.

I will try to describe the problem:

OS; CentOS v5 (Final) CentOS is based on the kernel and characteristics of the RedHat and Fedora Distributions

Kernel; 2.6.18-53.1.14.el5

Yum results:

gcc libraries:
gcc.i386 4.1.2-14.el5 installed
gcc-c++.i386 4.1.2-14.el5 installed
gcc-gfortran.i386 4.1.2-14.el5 installed
gcc-java.i386 4.1.2-14.el5 installed

tcl:
tcl.i386 8.4.13-3.fc6 installed
tcl-devel.i386 8.4.13-3.fc6 installed
tclx.i386 8.4.0-5.fc6 installed

tk:
tk.i386 8.4.13-5.el5_1.1 installed

NS Version: ns-allinone-2.31

After I perform "./install" as a root, I have the following message at the end of the failed installation:

/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c: In function ‘TkDebugBorder’:
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1391: error: ‘TkWindow’ has no member named ‘dispPtr’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1394: error: ‘TkDisplay’ has no member named ‘borderTable’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1394: error: ‘TkDisplay’ has no member named ‘borderTable’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1400: error: ‘TkBorder’ has no member named ‘nextPtr’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1403: error: ‘TkBorder’ has no member named ‘resourceRefCount’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk3d.c:1405: error: ‘TkBorder’ has no member named ‘objRefCount’
make: *** [tk3d.o] Error 1
tk8.4.14 make failed! Exiting ...
For problems with Tcl/Tk see www.scriptics.com

The resultant file is bigger.

I hope you can help me.

Best regards

Dennis Arturo

You appear to have an up-to-date installation that is the same as one of my platforms. (Same version ns, also.)


First of all, I wouldn't do anything as root unless I absolutely had to. I doubt that this is a problem here, but I just don't do such things. In any case the ns install script doesn't write anything outside of the directory tree where you start, so it isn't necessary to be root.

Secondly: Start fresh. delete all the previous stuff in the ns-allinone-2.31 directory tree. (I assume that ns-allinone-2.31.tar.gz is in your home directory.)

(If you did the previous ./install as root, then you may have to be root to do the "rm" thing but I'm not sure. Try it as your own "regular" self first.)

Then untar it again and cd into the ns-allinone-2.31 directory.

Execute the following command line:


This redirects all output, including error messages to a file named "install.log"

You can open another command window, navigate to the ns-allinone-2.31 directory and execute the following to see the progress:

(Ctrl-c in the "tail" window to terminate the "tail")

Now, if/when it bails out, you can examine the install.log and see where the first problems are found. About 813 lines down, you should see something like:


Does your "gcc" command line look like mine? Is it exactly the same?

Is there anything in this section (after the gcc command and before the lines that you posted) that indicates some error conditions? (Anything at all?) I had no compiler messages of any kind here.

If there are no clues, then:

Navigate to the tk8.4.14/unix directory. Look at config.log in that directory. Is there anything unusual there? Look at tkConfig-sh in that directory. Is there anything unusual there? (I wouldn't blame you if you don't know whether you would recognize anything "unusual." so you can just post the entire file if you get this far without any clues---mine has something like 93 lines.)

What resultant file are you talking about?


Regards,

Dave

Hello Dave

Thank you very much for your prompt answer. I performed your advice, I have the same problem but here are the details about it.

*Does your "gcc" command line look like mine? Is it exactly the same?*

Yes, is exactly the same.

After that and before the text that I post before, there are several errors and warnings like:

/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:83:23: error: X11/Xlib.h: No such file or directory
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:559: error: expected declaration specifiers or ‘...’ before ‘Window’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:559: error: ‘Window’ declared as function returning a function
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:559: warning: parameter names (without types) in function declaration
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:562: error: expected declaration specifiers or ‘...’ before ‘XEvent’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:571: error: expected specifier-qualifier-list before ‘Tk_ClassCreateProc’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:665: error: expected specifier-qualifier-list before ‘Bool’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:681: error: expected specifier-qualifier-list before ‘Bool’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:758: error: expected specifier-qualifier-list before ‘Display’
/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/../generic/tk.h:908: error: expected declaration specifiers or ‘...’ before ‘XPoint’

Well this is only an example of all the errors and warnings that appear.

Here is the file tkConfig-sh:

# tkConfig.sh --
#
# This shell script (for sh) is generated automatically by Tk's
# configure script. It will create shell variables for most of
# the configuration options discovered by the configure script.
# This script is intended to be included by the configure scripts
# for Tk extensions so that they don't have to figure this all
# out for themselves. This file does not duplicate information
# already provided by tclConfig.sh, so you may need to use that
# file in addition to this one.
#
# The information in this file is specific to a single platform.
#
# RCS: @(#) $Id: tkConfig.sh.in,v 1.8 2002/07/28 03:23:08 mdejong Exp $

# Tk's version number.
TK_VERSION='8.4'
TK_MAJOR_VERSION='8'
TK_MINOR_VERSION='4'
TK_PATCH_LEVEL='.14'

# -D flags for use with the C compiler.
TK_DEFS=' -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DSTATIC_BUILD=1 -DPEEK_XCLOSEIM=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DSTDC_HEADERS=1 -DHAVE_PW_GECOS=1 '

# Flag, 1: we built a shared lib, 0 we didn't
TK_SHARED_BUILD=0

# This indicates if Tk was build with debugging symbols
TK_DBGX=

# The name of the Tk library (may be either a .a file or a shared library):
TK_LIB_FILE='libtk8.4${TK_DBGX}.a'

# Additional libraries to use when linking Tk.
TK_LIBS='-lX11 -ldl -lieee -lm'

# Top-level directory in which Tcl's platform-independent files are
# installed.
TK_PREFIX='/home/Dennis/ns-allinone-2.31'

# Top-level directory in which Tcl's platform-specific files (e.g.
# executables) are installed.
TK_EXEC_PREFIX='/home/Dennis/ns-allinone-2.31'

# -I switch(es) to use to make all of the X11 include files accessible:
TK_XINCLUDES=''

# Linker switch(es) to use to link with the X11 library archive.
TK_XLIBSW='-lX11'

# -l flag to pass to the linker to pick up the Tcl library
TK_LIB_FLAG='-ltk8.4'

# String to pass to linker to pick up the Tk library from its
# build directory.
TK_BUILD_LIB_SPEC='-L/home/Dennis/ns-allinone-2.31/tk8.4.14/unix -ltk8.4'

# String to pass to linker to pick up the Tk library from its
# installed directory.
TK_LIB_SPEC='-L/home/Dennis/ns-allinone-2.31/lib -ltk8.4'

# Location of the top-level source directory from which Tk was built.
# This is the directory that contains a README file as well as
# subdirectories such as generic, unix, etc. If Tk was compiled in a
# different place than the directory containing the source files, this
# points to the location of the sources, not the location where Tk was
# compiled.
TK_SRC_DIR='/home/Dennis/ns-allinone-2.31/tk8.4.14'

# Needed if you want to make a 'fat' shared library library
# containing tk objects or link a different wish.
TK_CC_SEARCH_FLAGS='-Wl,-rpath,${LIB_RUNTIME_DIR}:NONE'
TK_LD_SEARCH_FLAGS='-Wl,-rpath,${LIB_RUNTIME_DIR}:NONE'

# The name of the Tk stub library (.a):
TK_STUB_LIB_FILE='libtkstub8.4.a'

# -l flag to pass to the linker to pick up the Tk stub library
TK_STUB_LIB_FLAG='-ltkstub8.4'

# String to pass to linker to pick up the Tk stub library from its
# build directory.
TK_BUILD_STUB_LIB_SPEC='-L/home/Dennis/ns-allinone-2.31/tk8.4.14/unix -ltkstub8.4'

# String to pass to linker to pick up the Tk stub library from its
# installed directory.
TK_STUB_LIB_SPEC='-L/home/Dennis/ns-allinone-2.31/lib -ltkstub8.4'

# Path to the Tk stub library in the build directory.
TK_BUILD_STUB_LIB_PATH='/home/Dennis/ns-allinone-2.31/tk8.4.14/unix/libtkstub8.4.a'

# Path to the Tk stub library in the install directory.
TK_STUB_LIB_PATH='/home/Dennis/ns-allinone-2.31/lib/libtkstub8.4.a'

I read in the NS2 page www.isi.edu that for Fedora and RedHat systems (I think also for CentOS), when:

"X11/Xlib.h: No such file or directory" appears, the development libraries of Xorg-X11 should be installed, furthermore, they recommend to use devel libraries in general. Could be the reason of this problem? I don't know exactly which are these libraries, but yum gives this:

xorg-x11-drv-i810-devel.i386 1.6.5-9.6.el5 base
xorg-x11-drv-via-devel.i386 0.2.1-9 base
xorg-x11-proto-devel.i386 7.1-9.el5.centos base
xorg-x11-xtrans-devel.i386 1.0.1-1.1.fc6 base

Thank you very much for your help.

Regards

Dennis Arturo

Yes.


The missing one is libX11-devel

Regards,

Dave