ns-3官方教程：从入门到实践

需积分: 10 69 浏览量更新于2024-07-20 收藏 588KB PDF 举报

"ns-3 是一个开源的网络模拟器，用于研究和教育目的，它提供了详细的网络模型，包括无线通信、互联网协议等。这个ns-3教程是官方文档的一部分，旨在帮助用户理解和使用该工具。教程覆盖了从安装到高级特性的方方面面，包括资源获取、环境设置、脚本编写、概念解析、网络拓扑构建、追踪系统以及数据收集等。" ns-3 教程主要包含以下几个方面： 1. **简介**：这部分介绍了ns-3是什么，它是为ns-2用户设计的，鼓励社区参与贡献，并解释了教程的组织结构。 2. **资源**：提到了获取ns-3相关资料的途径，如官方网站、版本控制系统Mercurial、构建工具Waf、开发环境的搭建以及套接字编程等基础知识。 3. **开始使用**：概述了ns-3的下载、构建、测试流程，以及如何运行第一个脚本，这些都是初学者入门的基础步骤。 4. **概念性概述**：这部分深入介绍了ns-3的关键抽象概念，通过一个简单的脚本示例展示了如何在ns-3中进行建模，还讲解了ns-3的源代码结构。 5. **微调**：包括了日志模块的使用、命令行参数的处理以及追踪系统的应用，这些功能有助于调试和分析模拟结果。 6. **构建网络拓扑**：详细阐述了如何构建总线网络和无线网络拓扑，讨论了模型、属性与现实之间的关系，这对于模拟复杂网络架构至关重要。 7. **追踪**：追踪是理解模拟行为的关键，教程提供了追踪系统的背景知识、概述、实例以及助手类的使用，帮助用户有效地分析和可视化模拟数据。 8. **数据收集**：解释了数据收集的重要性，提供了示例代码，引入了GnuplotHelper进行数据可视化，并列出了支持的追踪类型，还有文件处理助手，帮助用户管理和分析模拟生成的数据。 9. **并发和多线程**：这部分可能涉及如何在ns-3中实现并发和多线程，以便模拟多任务和分布式系统。通过这份ns-3教程，无论是网络研究人员还是学生，都能系统地学习和掌握ns-3网络模拟器的使用，从而进行深入的网络性能分析和实验。教程内容详实，涵盖了ns-3的各个方面，对于想要深入了解网络模拟的读者来说是一份宝贵的参考资料。

ns-3 Tutorial, Release ns-3.25

$ ./bake.py check

You should see something like the following,

> Python - OK

> GNU C++ compiler - OK

> Mercurial - OK

> CVS - OK

> GIT - OK

> Bazaar - OK

> Tar tool - OK

> Unzip tool - OK

> Unrar tool - is missing

> 7z data compression utility - OK

> XZ data compression utility - OK

> Make - OK

> cMake - OK

> patch tool - OK

> autoreconf tool - OK

> Path searched for tools: /usr/lib64/qt-3.3/bin /usr/lib64/ccache

/usr/local/bin /bin /usr/bin /usr/local/sbin /usr/sbin /sbin

/home/tomh/bin bin

In particular, download tools such as Mercurial, CVS, GIT, and Bazaar are our principal concerns at this point, since

they allow us to fetch the code. Please install missing tools at this stage, in the usual way for your system (if you are

able to), or contact your system administrator as needed to install these tools.

Next, try to download the software:

$ ./bake.py download

should yield something like:

>> Downloading gccxml-ns3 (target directory:gccxml) - OK

>> Searching for system dependency python-dev - OK

>> Searching for system dependency pygraphviz - OK

>> Searching for system dependency pygoocanvas - OK

>> Searching for system dependency setuptools - OK

>> Searching for system dependency g++ - OK

>> Searching for system dependency qt4 - OK

>> Downloading pygccxml - OK

>> Downloading netanim-3.107 - OK

>> Downloading pybindgen-0.17.0.post49+ng0e4e3bc (target directory:pybindgen) - OK

>> Downloading ns-3.25 - OK

The above suggests that ﬁve sources have been downloaded. Check the source directory now and type ls; one

should see:

$ ls

gccxml netanim-3.107 ns-3.25 pybindgen pygccxml pygccxml-1.0.0.zip

You are now ready to build the ns-3 distribution.

12 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3.25

3.3 Building ns-3

3.3.1 Building with build.py

When working from a released tarball, the ﬁrst time you build the ns-3 project you can build using a convenience

program found in the allinone directory. This program is called build.py. This program will get the project

conﬁgured for you in the most commonly useful way. However, please note that more advanced conﬁguration and

work with ns-3 will typically involve using the native ns-3 build system, Waf, to be introduced later in this tutorial.

If you downloaded using a tarball you should have a directory called something like ns-allinone-3.25 under

your ~/workspace directory. Type the following:

$ ./build.py --enable-examples --enable-tests

Because we are working with examples and tests in this tutorial, and because they are not built by default in ns-3, the

arguments for build.py tells it to build them for us. The program also defaults to building all available modules. Later,

you can build ns-3 without examples and tests, or eliminate the modules that are not necessary for your work, if you

wish.

You will see lots of typical compiler output messages displayed as the build script builds the various pieces you

downloaded. Eventually you should see the following:

Waf: Leaving directory `/path/to/workspace/ns-allinone-3.25/ns-3.25/build'

'build' finished successfully (6m25.032s)

Modules built:

antenna aodv applications

bridge buildings config-store

core csma csma-layout

dsdv dsr energy

fd-net-device flow-monitor internet

internet-apps lr-wpan lte

mesh mobility mpi

netanim (no Python) network nix-vector-routing

olsr openflow (no Python) point-to-point

point-to-point-layout propagation sixlowpan

spectrum stats tap-bridge

test (no Python) topology-read traffic-control

uan virtual-net-device visualizer

wave wifi wimax

Modules not built (see ns-3 tutorial for explanation): brite click

Leaving directory ‘./ns-3.25’

Regarding the portion about modules not built:

Modules not built (see ns-3 tutorial for explanation):

brite click

This just means that some ns-3 modules that have dependencies on outside libraries may not have been built, or that

the conﬁguration speciﬁcally asked not to build them. It does not mean that the simulator did not build successfully or

that it will provide wrong results for the modules listed as being built.

3.3.2 Building with bake

If you used bake above to fetch source code from project repositories, you may continue to use it to build ns-3. Type

3.3. Building ns-3 13

ns-3 Tutorial, Release ns-3.25

$ ./bake.py build

and you should see something like:

>> Building gccxml-ns3 - OK

>> Building pygccxml - OK

>> Building netanim-3.107 - OK

>> Building pybindgen-0.17.0.post49+ng0e4e3bc - OK

>> Building ns-3.25 - OK

Hint: you can also perform both steps, download and build, by calling ‘bake.py deploy’.

If there happens to be a failure, please have a look at what the following command tells you; it may give a hint as to a

missing dependency:

$ ./bake.py show

This will list out the various dependencies of the packages you are trying to build.

3.3.3 Building with Waf

Up to this point, we have used either the build.py script, or the bake tool, to get started with building ns-3. These tools

are useful for building ns-3 and supporting libraries, and they call into the ns-3 directory to call the Waf build tool to

do the actual building. Most users quickly transition to using Waf directly to conﬁgure and build ns-3. So, to proceed,

please change your working directory to the ns-3 directory that you have initially built.

It’s not strictly required at this point, but it will be valuable to take a slight detour and look at how to make changes

to the conﬁguration of the project. Probably the most useful conﬁguration change you can make will be to build the

optimized version of the code. By default you have conﬁgured your project to build the debug version. Let’s tell the

project to make an optimized build. To explain to Waf that it should do optimized builds that include the examples and

tests, you will need to execute the following commands:

$ ./waf clean

$ ./waf --build-profile=optimized --enable-examples --enable-tests configure

This runs Waf out of the local directory (which is provided as a convenience for you). The ﬁrst command to clean out

the previous build is not typically strictly necessary but is good practice (but see Build Proﬁles, below); it will remove

the previously built libraries and object ﬁles found in directory build/. When the project is reconﬁgured and the

build system checks for various dependencies, you should see output that looks similar to the following:

Setting top to : .

Setting out to : build

Checking for 'gcc' (c compiler) : /usr/bin/gcc

Checking for cc version : 4.2.1

Checking for 'g++' (c++ compiler) : /usr/bin/g++

Checking boost includes : 1_46_1

Checking boost libs : ok

Checking for boost linkage : ok

Checking for click location : not found

Checking for program pkg-config : /sw/bin/pkg-config

Checking for 'gtk+-2.0' >= 2.12 : yes

Checking for 'libxml-2.0' >= 2.7 : yes

Checking for type uint128_t : not found

Checking for type __uint128_t : yes

Checking high precision implementation : 128-bit integer (default)

Checking for header stdint.h : yes

Checking for header inttypes.h : yes

Checking for header sys/inttypes.h : not found

14 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3.25

Checking for header sys/types.h : yes

Checking for header sys/stat.h : yes

Checking for header dirent.h : yes

Checking for header stdlib.h : yes

Checking for header signal.h : yes

Checking for header pthread.h : yes

Checking for header stdint.h : yes

Checking for header inttypes.h : yes

Checking for header sys/inttypes.h : not found

Checking for library rt : not found

Checking for header netpacket/packet.h : not found

Checking for header sys/ioctl.h : yes

Checking for header net/if.h : not found

Checking for header net/ethernet.h : yes

Checking for header linux/if_tun.h : not found

Checking for header netpacket/packet.h : not found

Checking for NSC location : not found

Checking for 'mpic++' : yes

Checking for 'sqlite3' : yes

Checking for header linux/if_tun.h : not found

Checking for program sudo : /usr/bin/sudo

Checking for program valgrind : /sw/bin/valgrind

Checking for 'gsl' : yes

Checking for compilation flag -Wno-error=deprecated-d... support : ok

Checking for compilation flag -fstrict-aliasing... support : ok

Checking for compilation flag -Wstrict-aliasing... support : ok

Checking for program doxygen : /usr/local/bin/doxygen

---- Summary of optional NS-3 features:

Build profile : debug

Build directory : build

Python Bindings : enabled

BRITE Integration : not enabled (BRITE not enabled (see option --with-brite))

NS-3 Click Integration : not enabled (nsclick not enabled (see option --with-nsclick))

GtkConfigStore : enabled

XmlIo : enabled

Threading Primitives : enabled

Real Time Simulator : enabled (librt is not available)

Emulated Net Device : enabled (<netpacket/packet.h> include not detected)

File descriptor NetDevice : enabled

Tap FdNetDevice : not enabled (needs linux/if_tun.h)

Emulation FdNetDevice : not enabled (needs netpacket/packet.h)

PlanetLab FdNetDevice : not enabled (PlanetLab operating system not detected (see option --force-planetlab))

Network Simulation Cradle : not enabled (NSC not found (see option --with-nsc))

MPI Support : enabled

NS-3 OpenFlow Integration : not enabled (Required boost libraries not found, missing: system, signals, filesystem)

SQlite stats data output : enabled

Tap Bridge : not enabled (<linux/if_tun.h> include not detected)

PyViz visualizer : enabled

Use sudo to set suid bit : not enabled (option --enable-sudo not selected)

Build tests : enabled

Build examples : enabled

GNU Scientific Library (GSL) : enabled

'configure' finished successfully (1.944s)

Note the last part of the above output. Some ns-3 options are not enabled by default or require support from the

3.3. Building ns-3 15

ns-3 Tutorial, Release ns-3.25

underlying system to work properly. For instance, to enable XmlTo, the library libxml-2.0 must be found on the

system. If this library were not found, the corresponding ns-3 feature would not be enabled and a message would be

displayed. Note further that there is a feature to use the program sudo to set the suid bit of certain programs. This is

not enabled by default and so this feature is reported as “not enabled.”

Now go ahead and switch back to the debug build that includes the examples and tests.

$ ./waf clean

$ ./waf --build-profile=debug --enable-examples --enable-tests configure

The build system is now conﬁgured and you can build the debug versions of the ns-3 programs by simply typing

$ ./waf

Okay, sorry, I made you build the ns-3 part of the system twice, but now you know how to change the conﬁguration

and build optimized code.

A command exists for checking which proﬁle is currently active for an already conﬁgured project:

$ ./waf –check-proﬁle Waf: Entering directory ‘/path/to/ns-3-allinone/ns-3.25/build’ Build proﬁle: debug

The build.py script discussed above supports also the --enable-examples and enable-tests arguments, but

in general, does not directly support other waf options; for example, this will not work:

$ ./build.py --disable-python

will result in

build.py: error: no such option: --disable-python

However, the special operator -- can be used to pass additional options through to waf, so instead of the above, the

following will work:

$ ./build.py -- --disable-python

as it generates the underlying command ./waf configure --disable-python.

Here are a few more introductory tips about Waf.

Conﬁgure vs. Build

Some Waf commands are only meaningful during the conﬁgure phase and some commands are valid in the build

phase. For example, if you wanted to use the emulation features of ns-3, you might want to enable setting the suid

bit using sudo as described above. This turns out to be a conﬁguration-time command, and so you could reconﬁgure

using the following command that also includes the examples and tests.

$ ./waf configure --enable-sudo --enable-examples --enable-tests

If you do this, Waf will have run sudo to change the socket creator programs of the emulation code to run as root.

There are many other conﬁgure- and build-time options available in Waf. To explore these options, type:

$ ./waf --help

We’ll use some of the testing-related commands in the next section.

Build Proﬁles

We already saw how you can conﬁgure Waf for debug or optimized builds:

16 Chapter 3. Getting Started

剩余124页未读，继续阅读

lmfreeking

粉丝: 16
资源: 8

ns-3官方教程：从入门到实践

ns-3 教程+手册（tutorial+manual）

ns-3-tutorial.pdf

2013-ns-3-tutorial-Walid-Younes.pdf

ns-3_中文教程（tutorial 翻译）.zip_NS3中文教程_NS3使用教程_ns-3_ns3-tutorial中文_n

ns-3-model-library.pdf.zip_jumpi97_ns-3_tutorial

ns-wireless-tutorial

ns-3-manual、model-library、tutorial

FNCS-Tutorial:构建和运行 FNCS、ns-3、GridLAB-D 和 MATPOWER 的分步指南

ns3-tutorial

2013-NS3-visualization-tutorial.pdf

最新资源