A Discrete-Event Network Simulator

Using Python to Run ns-3

Python bindings allow the C++ code in ns-3 to be called from Python.

This chapter shows you how to create a Python script that can run ns-3 and also the process of creating Python bindings for a C++ ns-3 module.


The goal of Python bindings for ns-3 are two fold:

  1. Allow the programmer to write complete simulation scripts in Python (http://www.python.org);
  2. Prototype new models (e.g. routing protocols).

For the time being, the primary focus of the bindings is the first goal, but the second goal will eventually be supported as well. Python bindings for ns-3 are being developed using a new tool called PyBindGen (http://code.google.com/p/pybindgen).

An Example Python Script that Runs ns-3

Here is some example code that is written in Python and that runs ns-3, which is written in C++. This Python example can be found in examples/tutorial/first.py:

import ns.applications
import ns.core
import ns.internet
import ns.network
import ns.point_to_point

ns.core.LogComponentEnable("UdpEchoClientApplication", ns.core.LOG_LEVEL_INFO)
ns.core.LogComponentEnable("UdpEchoServerApplication", ns.core.LOG_LEVEL_INFO)

nodes = ns.network.NodeContainer()

pointToPoint = ns.point_to_point.PointToPointHelper()
pointToPoint.SetDeviceAttribute("DataRate", ns.core.StringValue("5Mbps"))
pointToPoint.SetChannelAttribute("Delay", ns.core.StringValue("2ms"))

devices = pointToPoint.Install(nodes)

stack = ns.internet.InternetStackHelper()

address = ns.internet.Ipv4AddressHelper()
address.SetBase(ns.network.Ipv4Address(""), ns.network.Ipv4Mask(""))

interfaces = address.Assign (devices);

echoServer = ns.applications.UdpEchoServerHelper(9)

serverApps = echoServer.Install(nodes.Get(1))

echoClient = ns.applications.UdpEchoClientHelper(interfaces.GetAddress(1), 9)
echoClient.SetAttribute("MaxPackets", ns.core.UintegerValue(1))
echoClient.SetAttribute("Interval", ns.core.TimeValue(ns.core.Seconds (1.0)))
echoClient.SetAttribute("PacketSize", ns.core.UintegerValue(1024))

clientApps = echoClient.Install(nodes.Get(0))


Running Python Scripts

waf contains some options that automatically update the python path to find the ns3 module. To run example programs, there are two ways to use waf to take care of this. One is to run a waf shell; e.g.:

$ ./waf shell
$ python examples/wireless/mixed-wireless.py

and the other is to use the –pyrun option to waf:

$ ./waf --pyrun examples/wireless/mixed-wireless.py

To run a python script under the C debugger:

$ ./waf shell
$ gdb --args python examples/wireless/mixed-wireless.py

To run your own Python script that calls ns-3 and that has this path, /path/to/your/example/my-script.py, do the following:

$ ./waf shell
$ python /path/to/your/example/my-script.py


Python bindings for ns-3 are a work in progress, and some limitations are known by developers. Some of these limitations (not all) are listed here.

Incomplete Coverage

First of all, keep in mind that not 100% of the API is supported in Python. Some of the reasons are:

  1. some of the APIs involve pointers, which require knowledge of what kind of memory passing semantics (who owns what memory). Such knowledge is not part of the function signatures, and is either documented or sometimes not even documented. Annotations are needed to bind those functions;
  2. Sometimes a unusual fundamental data type or C++ construct is used which is not yet supported by PyBindGen;
  3. GCC-XML does not report template based classes unless they are instantiated.

Most of the missing APIs can be wrapped, given enough time, patience, and expertise, and will likely be wrapped if bug reports are submitted. However, don’t file a bug report saying “bindings are incomplete”, because we do not have manpower to complete 100% of the bindings.

Conversion Constructors

Conversion constructors are not fully supported yet by PyBindGen, and they always act as explicit constructors when translating an API into Python. For example, in C++ you can do this:

Ipv4AddressHelper ipAddrs;
ipAddrs.SetBase ("", "");
ipAddrs.Assign (backboneDevices);

In Python, for the time being you have to do:

ipAddrs = ns3.Ipv4AddressHelper()
ipAddrs.SetBase(ns3.Ipv4Address(""), ns3.Ipv4Mask(""))


CommandLine::AddValue() works differently in Python than it does in ns-3. In Python, the first parameter is a string that represents the command-line option name. When the option is set, an attribute with the same name as the option name is set on the CommandLine() object. Example:


cmd = ns3.CommandLine()

cmd.NumNodesSide = None
cmd.AddValue("NumNodesSide", "Grid side number of nodes (total number of nodes will be this number squared)")



if cmd.NumNodesSide is None:
    num_nodes_side = NUM_NODES_SIDE_DEFAULT
    num_nodes_side = int(cmd.NumNodesSide)


Callback based tracing is not yet properly supported for Python, as new ns-3 API needs to be provided for this to be supported.

Pcap file writing is supported via the normal API.

Ascii tracing is supported since ns-3.4 via the normal C++ API translated to Python. However, ascii tracing requires the creation of an ostream object to pass into the ascii tracing methods. In Python, the C++ std::ofstream has been minimally wrapped to allow this. For example:

ascii = ns3.ofstream("wifi-ap.tr") # create the file
ascii.close() # close the file

There is one caveat: you must not allow the file object to be garbage collected while ns-3 is still using it. That means that the ‘ascii’ variable above must not be allowed to go out of scope or else the program will crash.

Cygwin limitation

Python bindings do not work on Cygwin. This is due to a gccxml bug.

You might get away with it by re-scanning API definitions from within the cygwin environment (./waf –python-scan). However the most likely solution will probably have to be that we disable python bindings in CygWin.

If you really care about Python bindings on Windows, try building with mingw and native python instead. Or else, to build without python bindings, disable python bindings in the configuration stage:

$ ./waf configure --disable-python

Working with Python Bindings

There are currently two kinds of Python bindings in ns-3:

  1. Monolithic bindings contain API definitions for all of the modules and can be found in a single directory, bindings/python.
  2. Modular bindings contain API definitions for a single module and can be found in each module’s bindings directory.

Python Bindings Workflow

The process by which Python bindings are handled is the following:

  1. Periodically a developer uses a GCC-XML (http://www.gccxml.org) based API scanning script, which saves the scanned API definition as bindings/python/ns3_module_*.py files or as Python files in each modules’ bindings directory. These files are kept under version control in the main ns-3 repository;
  2. Other developers clone the repository and use the already scanned API definitions;
  3. When configuring ns-3, pybindgen will be automatically downloaded if not already installed. Released ns-3 tarballs will ship a copy of pybindgen.

If something goes wrong with compiling Python bindings and you just want to ignore them and move on with C++, you can disable Python with:

$ ./waf --disable-python

Instructions for Handling New Files or Changed API’s

So you have been changing existing ns-3 APIs and Python bindings no longer compile? Do not despair, you can rescan the bindings to create new bindings that reflect the changes to the ns-3 API.

Depending on if you are using monolithic or modular bindings, see the discussions below to learn how to rescan your Python bindings.

Monolithic Python Bindings

Scanning the Monolithic Python Bindings

To scan the monolithic Python bindings do the following:

$ ./waf --python-scan

Organization of the Monolithic Python Bindings

The monolithic Python API definitions are organized as follows. For each ns-3 module <name>, the file bindings/python/ns3_module_<name>.py describes its API. Each of those files have 3 toplevel functions:

  1. def register_types(module)(): this function takes care of registering new types (e.g. C++ classes, enums) that are defined in tha module;
  2. def register_methods(module)(): this function calls, for each class <name>, another function register_methods_Ns3<name>(module). These latter functions add method definitions for each class;
  3. def register_functions(module)(): this function registers ns-3 functions that belong to that module.

Modular Python Bindings


Since ns 3.11, the modular bindings are being added, in parallel to the old monolithic bindings.

The new python bindings are generated into an ‘ns’ namespace, instead of ‘ns3’ for the old bindings. Example:

from ns.network import Node
n1 = Node()

With modular Python bindings:

  1. There is one separate Python extension module for each ns-3 module;
  2. Scanning API definitions (apidefs) is done on a per ns- module basis;
  3. Each module’s apidefs files are stored in a ‘bindings’ subdirectory of the module directory;

Scanning the Modular Python Bindings

To scan the modular Python bindings for the core module, for example, do the following:

$ ./waf --apiscan=core

To scan the modular Python bindings for all of the modules, do the following:

$ ./waf --apiscan=all

Creating a New Module

If you are adding a new module, Python bindings will continue to compile but will not cover the new module.

To cover a new module, you have to create a bindings/python/ns3_module_<name>.py file, similar to the what is described in the previous sections, and register it in the variable LOCAL_MODULES() in bindings/python/ns3modulegen.py

Adding Modular Bindings To A Existing Module

To add support for modular bindings to an existing ns-3 module, simply add the following line to its wscript build() function:


Organization of the Modular Python Bindings

The src/<module>/bindings directory may contain the following files, some of them optional:

  • callbacks_list.py: this is a scanned file, DO NOT TOUCH. Contains a list of Callback<...> template instances found in the scanned headers;
  • modulegen__gcc_LP64.py: this is a scanned file, DO NOT TOUCH. Scanned API definitions for the GCC, LP64 architecture (64-bit)
  • modulegen__gcc_ILP32.py: this is a scanned file, DO NOT TOUCH. Scanned API definitions for the GCC, ILP32 architecture (32-bit)
  • modulegen_customizations.py: you may optionally add this file in order to customize the pybindgen code generation
  • scan-header.h: you may optionally add this file to customize what header file is scanned for the module. Basically this file is scanned instead of ns3/<module>-module.h. Typically, the first statement is #include “ns3/<module>-module.h”, plus some other stuff to force template instantiations;
  • module_helpers.cc: you may add additional files, such as this, to be linked to python extension module, but they have to be registered in the wscript. Look at src/core/wscript for an example of how to do so;
  • <module>.py: if this file exists, it becomes the “frontend” python module for the ns3 module, and the extension module (.so file) becomes _<module>.so instead of <module>.so. The <module>.py file has to import all symbols from the module _<module> (this is more tricky than it sounds, see src/core/bindings/core.py for an example), and then can add some additional pure-python definitions.

More Information for Developers

If you are a developer and need more information on ns-3‘s Python bindings, please see the Python Bindings wiki page.