ns-3官方教程：从入门到精通

需积分: 10 32 浏览量更新于2024-07-19 收藏 589KB PDF 举报

"ns-3-tutorial.pdf 是一份官方的ns-3教程，适用于初学者，涵盖ns-3的安装、模块介绍、示例程序等内容，是学习ns-3仿真平台的重要参考资料。" ns-3是一个开源的网络模拟器，主要用于研究和教育目的，它允许用户在软件中构建和模拟各种网络协议和应用。这份ns-3教程包含了以下关键知识点： 1. **关于ns-3**: ns-3是一个高度可配置、模块化的网络模拟框架，用于模拟互联网协议和网络算法。它支持IPv4和IPv6，以及各种无线通信模型，如Wi-Fi、蜂窝网络等。 2. **ns-2用户转换**: 对于熟悉ns-2的用户，ns-3提供了一些相似的概念和API，但也有许多改进和增强，例如更好的C++封装、更精确的物理层模型等。 3. **贡献指南**: 教程中介绍了如何参与到ns-3项目中，包括代码贡献、报告问题和参与社区讨论等。 4. **教程组织结构**: 教程分为多个部分，从入门资源到高级特性，逐步引导学习者理解并掌握ns-3。 5. **资源获取**: 提供了获取ns-3源码、使用Mercurial版本控制工具、Waf构建系统以及设置开发环境的方法。 6. **开始使用ns-3**: 包括下载、编译ns-3，运行测试以确保安装正确，并介绍如何执行脚本进行模拟。 7. **概念概述**: 强调了ns-3的关键抽象，如网络节点、接口、协议，以及通过一个简单的脚本介绍网络模拟的基本概念。 8. **微调与定制**: 阐述了如何使用日志模块进行调试，如何通过命令行参数自定义模拟，以及利用追踪系统分析模拟结果。 9. **构建网络拓扑**: 教程涵盖了构建总线网络和无线网络拓扑的方法，还讲解了模型、属性和现实之间的关系。 10. **追踪系统**: 深入介绍追踪系统的背景、工作原理，通过实际例子展示如何使用追踪功能，并提供了Trace Helper工具。 11. **数据收集与分析**: 强调了收集和分析模拟数据的重要性，提供了使用GnuplotHelper进行可视化以及支持的追踪类型。 12. **其他工具和助手**: 如FileHelper，帮助用户更方便地处理模拟过程中的文件操作。这个教程旨在帮助初学者快速上手ns-3，通过实践和理解，逐步深入网络模拟的世界。对于想要研究网络协议、性能评估或进行学术研究的人来说，这是一个非常宝贵的资源。

ns-3 Tutorial, Release ns-3.27

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

>> Searching for system dependency setuptools - OK

>> Searching for system dependency pygoocanvas - OK

>> Searching for system dependency pygraphviz - OK

>> Searching for system dependency python-dev - OK

>> Searching for system dependency libxml2-dev - OK

>> Searching for system dependency clang-dev - OK

>> Downloading click-ns-3.25 - OK

>> Downloading BRITE - OK

>> Searching for system dependency qt4 - OK

>> Downloading nsc-0.5.3 - OK

>> Searching for system dependency g++ - OK

>> Downloading castxml - OK

>> Downloading openflow-ns-3.25 - OK

>> Downloading netanim-3.108 - OK

>> Downloading pygccxml-1.9.1 - OK

>> Downloading pygccxml - OK

>> Downloading pybindgen-ns3.27-castxml (target directory:pybindgen) - OK

>> Downloading ns-3.27 - OK

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

should see:

$ ls

BRITE netanim-3.108 openflow-ns-3.25 pygccxml-1.9.1

castxml ns-3.27 pybindgen v1.9.1.tar.gz

click-ns-3.25 nsc-0.5.3 pygccxml

12 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3.27

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

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.27 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.27/ns-3.27/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

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. Building ns-3 13

ns-3 Tutorial, Release ns-3.27

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

$ ./bake.py build

and you should see something like:

>> Building BRITE - OK

>> Building nsc-0.5.3 - OK

>> Building click-ns-3.25 - OK

...

>> Building ns-3.27 - OK

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

There may be failures to build all components, but the build will proceed anyway if the component is optional. For

example, a common issue at the moment is that castxml may not build via the bake build tool on all platforms; in this

case, the line will show:

>> Building castxml - Problem

> Problem: Optional dependency, module "castxml" failed

This may reduce the functionality of the final build.

However, bake will continue since "castxml" is not an essential dependency.

For more information call bake with -v or -vvv, for full verbose mode.

However, castxml is only needed if one wants to generate updated Python bindings, and most users do not need to do

so (or to do so until they are more involved with ns-3 changes), so such warnings might be safely ignored for now.

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 configure --build-profile=optimized --enable-examples --enable-tests

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:

14 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3.27

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

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

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

Build directory : build

Build examples : enabled

Build tests : enabled

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

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

File descriptor NetDevice : enabled

GNU Scientific Library (GSL) : enabled

3.3. Building ns-3 15

ns-3 Tutorial, Release ns-3.27

GtkConfigStore : enabled

MPI Support : enabled

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

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

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

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

PyViz visualizer : enabled

Python Bindings : enabled

Real Time Simulator : enabled (librt is not available)

SQlite stats data output : enabled

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

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

Threading Primitives : enabled

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

XmlIo : 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

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.” Finally, to reprint this summary of which

optional features are enabled, use the --check-config option to waf.

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

$ ./waf clean

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

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-profile

Waf: Entering directory \`/path/to/ns-3-allinone/ns-3.27/build'

Build profile: 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.

16 Chapter 3. Getting Started

剩余124页未读，继续阅读

胡安先生

粉丝: 3
资源: 1

ns-3官方教程：从入门到精通

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

ns-3-tutorial

ug871-vivado-high-level-synthesis-tutorial.pdf

protoc *.proto --python_out=.

ns3可视化工具pyviz安装

ns3-tutorial

请给我一份ISE的官方文档

MySQL具体学习资料

有没有ns3学习笔记链接

有可以自学的kali linuk的教程推荐吗

最新资源