ns3 repo for bufferbloat related code
Python C++ C Perl Matlab Shell
Latest commit 99cf143 May 22, 2014 Dave Täht Preturb is not a word. Peturb is a word.
While this speling error exists in the code there's no need
to compound it.
Failed to load latest commit information.
bindings/python fixes for Python 2.6 compatibility Mar 13, 2014
doc [doxygen] Clarify doxygen.conf PREDEFINED variable. Mar 10, 2014
examples RIPng implementation Mar 17, 2014
ns3 Add support for building with WAF May 7, 2007
src Preturb is not a word. Peturb is a word. May 22, 2014
utils [doxygen] Make introspected lists more visible, various other doxy Mar 10, 2014
waf-tools Bug 1682 - ./waf crashes on FC10 Jul 11, 2013
.hgignore hgignore LTE *Stats.txt Mar 25, 2014
AUTHORS add some more new authors Dec 16, 2013
CHANGES.html add to notes regarding null message parallel scheduler and new time u… Dec 16, 2013
LICENSE Final pre-release files Mar 30, 2007
Makefile Add Makefile wrapper for waf, to ease configuration in NetBeans, Ecli… Jul 23, 2013
README Fix outdated README information Dec 8, 2011
VERSION Version back to ns-3-dev Jan 27, 2010
codel-todo.org My todo list for the codel stuff Apr 25, 2014
test.py Strip NS3_BUILDDIR from Example path. Jan 11, 2014
testpy.supp Bug 781: Suppress the valgrind error: Invalid read size of 8 in TestS… Jan 13, 2010
utils.py Bug 1391 - .ns3rc does not allow comments as expected Apr 26, 2012
waf Upgrade to WAF 1.7.13. Oct 13, 2013
waf.bat add waf.bat for convenience (waf itself still has to be manually copi… Jun 18, 2007
wscript Repeat the build output directory and the build profile in the config… Jan 31, 2014
wutils.py bug 1869: append local build directory before recursing into modules Mar 13, 2014


    The Network Simulator, Version 3

Table of Contents:

1) An overview
2) Building ns-3
3) Running ns-3
4) Getting access to the ns-3 documentation
5) Working with the development version of ns-3

Note:  Much more substantial information about ns-3 can be found at

1) An Open Source project

ns-3 is a free open source project aiming to build a discrete-event
network simulator targeted for simulation research and education.   
This is a collaborative project; we hope that
the missing pieces of the models we have not yet implemented
will be contributed by the community in an open collaboration

The process of contributing to the ns-3 project varies with
the people involved, the amount of time they can invest
and the type of model they want to work on, but the current
process that the project tries to follow is described here:

This README excerpts some details from a more extensive
tutorial that is maintained at:

2) Building ns-3

The code for the framework and the default models provided
by ns-3 is built as a set of libraries. User simulations
are expected to be written as simple programs that make
use of these ns-3 libraries.

To build the set of default libraries and the example
programs included in this package, you need to use the
tool 'waf'. Detailed information on how use waf is 
included in the file doc/build.txt

However, the real quick and dirty way to get started is to
type the command
  ./waf configure --enable-examples
followed by
in the the directory which contains
this README file. The files built will be copied in the
build/ directory.

The current codebase is expected to build and run on the
set of platforms listed in the RELEASE_NOTES file.

Other platforms may or may not work: we welcome patches to 
improve the portability of the code to these other platforms. 

3) Running ns-3

On recent Linux systems, once you have built ns-3 (with examples
enabled), it should be easy to run the sample programs with the
following command, such as:

  ./waf --run simple-global-routing

That program should generate a simple-global-routing.tr text 
trace file and a set of simple-global-routing-xx-xx.pcap binary
pcap trace files, which can be read by tcpdump -tt -r filename.pcap
The program source can be found in the examples/routing directory.

4) Getting access to the ns-3 documentation

Once you have verified that your build of ns-3 works by running
the simple-point-to-point example as outlined in 4) above, it is
quite likely that you will want to get started on reading
some ns-3 documentation. 

All of that documentation should always be available from
the ns-3 website: http:://www.nsnam.org/documentation/.

This documentation includes:

  - a tutorial
  - a reference manual

  - models in the ns-3 model library

  - a wiki for user-contributed tips: http://www.nsnam.org/wiki/

  - API documentation generated using doxygen: this is
    a reference manual, most likely not very well suited 
    as introductory text:

5) Working with the development version of ns-3

If you want to download and use the development version 
of ns-3, you need to use the tool 'mercurial'. A quick and
dirty cheat sheet is included in doc/mercurial.txt but
reading through the mercurial tutorials included on the
mercurial website is usually a good idea if you are not
familiar with it.

If you have successfully installed mercurial, you can get
a copy of the development version with the following command:
"hg clone http://code.nsnam.org/ns-3-dev"