Bitbucket is a code hosting site with unlimited public and private repositories. We're also free for small teams!

Close
    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
http://www.nsnam.org

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
process.

Contributing to the ns-3 project is still a very informal
process because that process depends heavily on the background
of the people involved, the amount of time they can invest
and the type of model they want to work on.  

Despite this lack of a formal process, there are a number of 
steps which naturally stem from the open-source roots of the
project.  These steps are described in doc/contributing.txt

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; ./waf" the the directory which contains
this README file. The files built will be copied in the
build/debug or build/optimized.

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, it 
should be easy to run the sample programs with the
following command:

./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

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/ but we
include some of it in this release for ease of use.

This documentation includes:

  - a tutorial
 
  - a manual

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

  - an API documentation generated using doxygen: this is
    a reference manual, most likely not very well suited 
    as introductory text:
    http://www.nsnam.org/doxygen/index.html

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"

Recent activity

Mitch Watrous

Commits by Mitch Watrous were pushed to lalithsuresh/ns-3-gpsr

20221fb - Make mesh, dot11s, and flame modules create only one module
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

318bdcd - Scan modular bindings for the 'core' and 'network' modules
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

4ea22fe - Copy a bug fix from ns3modulescan.py into ns3modulescan-modular.py
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

fdb8897 - Document in the --bindings-type waf option that modular bindings are experimental
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

11a009e - Import type_annotations from ns3modulescan.py into ns3modulescan-modular.py.
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

826f200 - ./waf --apiscan creates the bindings dir if it doesn't exist
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

9ac9bd5 - Make ns3_python_bindings skip bindings with warning if apidefs dir not found
Gustavo J. A. M. Carneiro

Commits by Gustavo J. A. M. Carneiro were pushed to lalithsuresh/ns-3-gpsr

c7537e6 - Start of work on modular Python bindings, unstable
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.