ns-3网络仿真教程：入门与概念解析

需积分: 15 20 浏览量更新于2024-07-14 收藏 548KB PDF 举报

"ns-3教程是一个详细的网络仿真实验指南，主要针对ns-3模拟器，涵盖了无线局域网的模拟。这份教程是ns-3项目的一部分，更新至ns-3-dev版本，旨在帮助用户理解和使用ns-3进行网络仿真。教程包括了介绍、资源、开始使用、概念概述、微调、构建拓扑、追踪和数据收集等多个部分，旨在为初学者和有经验的ns-2用户提供全面的支持。" 在深入探讨ns-3网络仿真实验的知识点之前，首先了解ns-3是一个开源的网络模拟软件，广泛用于研究和教育，尤其在无线通信和互联网协议的建模上。它提供了丰富的模型库，可以模拟从底层物理层到高层应用层的各种网络组件。 1. **关于ns-3**: ns-3是一个高度可定制的网络模拟器，它允许用户模拟各种网络场景，从简单的点对点连接到复杂的无线网络环境。它的核心设计目标是提供现实世界网络行为的准确模拟，同时保持代码的可读性和模块化。 2. **对于ns-2用户**: 如果你有ns-2的基础，这个教程将帮助你过渡到ns-3。尽管两者有许多相似之处，但ns-3在设计上进行了改进，以提高性能和可维护性。 3. **贡献**: ns-3是一个社区驱动的项目，鼓励用户参与开发、报告问题和贡献代码。 4. **教程组织**: 教程按照逐步学习的方式展开，从安装和配置，到编写和运行脚本，再到更高级的主题如网络拓扑的构建和数据收集。 5. **资源**: 教程提到了网络资源，包括项目网站、Git仓库（用于获取最新源码）、Waf构建系统、开发环境的设置以及套接字编程的基本知识。 6. **开始使用**: 介绍如何下载和构建ns-3，包括使用Git克隆仓库，通过Waf构建系统编译，以及运行测试来验证安装是否成功。 7. **概念概述**: 涵盖ns-3的关键抽象，例如关键网络组件和它们之间的交互，以及编写第一个ns-3脚本的基本步骤。 8. **微调**: 讲解如何利用日志模块进行调试，处理命令行参数以自定义模拟，以及使用追踪系统来监控模拟过程中的事件。 9. **构建拓扑**: 包括创建线性网络（bus network）和无线网络拓扑的步骤，以及模型、属性和实际网络行为之间的关系。 10. **追踪**: 解释了追踪系统的工作原理，提供了一个实际示例，并介绍了Trace Helper工具，用于简化追踪事件的设置。 11. **数据收集**: 阐述了收集模拟数据的重要性，给出了一个使用Gnuplot Helper进行数据可视化的例子，并列出了ns-3支持的不同类型的追踪输出。这个教程不仅适合新手入门，也适合有经验的网络研究人员和工程师，帮助他们深入理解网络行为并进行复杂网络实验。通过学习和实践，用户可以掌握ns-3的使用，从而在无线局域网和其他网络领域进行精确的模拟和分析。

ns-3 Tutorial, Release ns-3-dev

Cloning into 'bake'...

remote: Enumerating objects: 2086, done.

remote: Counting objects: 100% (2086/2086), done.

remote: Compressing objects: 100% (649/649), done.

remote: Total 2086 (delta 1404), reused 2078 (delta 1399)

Receiving objects: 100% (2086/2086), 2.68 MiB | 3.82 MiB/s, done.

Resolving deltas: 100% (1404/1404), done.

After the clone command completes, you should have a directory called bake, the contents of which should look

something like the following:

$ cd bake

$ ls

bake bakeconf.xml bake.py doc examples generate-binary.py test TODO

Notice that you have downloaded some Python scripts, a Python module called bake, and an XML conﬁguration ﬁle.

The next step will be to use those scripts to download and build the ns-3 distribution of your choice.

There are a few conﬁguration targets available:

1. ns-3.32: the module corresponding to the release; it will download components similar to the release tarball.

2. ns-3-dev: a similar module but using the development code tree

3. ns-allinone-3.32: the module that includes other optional features such as Click routing, Openﬂow for ns-3,

and the Network Simulation Cradle

4. ns-3-allinone: similar to the released version of the allinone module, but for development code.

The current development snapshot (unreleased) of ns-3 may be found at https://gitlab.com/nsnam/ns-3-dev.git. The

developers attempt to keep these repositories in consistent, working states but they are in a development area with

unreleased code present, so you may want to consider staying with an ofﬁcial release if you do not need newly-

introduced features.

You can ﬁnd the latest version of the code either by inspection of the repository list or by going to the “ns-3 Releases”

web page and clicking on the latest release link. We’ll proceed in this tutorial example with ns-3.32.

We are now going to use the bake tool to pull down the various pieces of ns-3 you will be using. First, we’ll say a

word about running bake.

bake works by downloading source packages into a source directory, and installing libraries into a build directory. bake

can be run by referencing the binary, but if one chooses to run bake from outside of the directory it was downloaded

into, it is advisable to put bake into your path, such as follows (Linux bash shell example). First, change into the ‘bake’

directory, and then set the following environment variables:

$ export BAKE_HOME=`pwd`

$ export PATH=$PATH:$BAKE_HOME:$BAKE_HOME/build/bin

$ export PYTHONPATH=$PYTHONPATH:$BAKE_HOME:$BAKE_HOME/build/lib

This will put the bake.py program into the shell’s path, and will allow other programs to ﬁnd executables and libraries

created by bake. Although several bake use cases do not require setting PATH and PYTHONPATH as above, full

builds of ns-3-allinone (with the optional packages) typically do.

Step into the workspace directory and type the following into your shell:

$ ./bake.py configure -e ns-3.32

Next, we’ll ask bake to check whether we have enough tools to download various components. Type:

12 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3-dev

3.4.1 Building with build.py

Note: This build step is only available from a source archive release described above; not from downloading via git or

bake.

When working from a released tarball, a convenience script available as part of ns-3-allinone can orchestrate a

simple build of components. 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.32 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 compiler output messages displayed as the build script builds the various pieces you downloaded.

First, the script will attempt to build the netanim animator, then the pybindgen bindings generator, and ﬁnally ns-3.

Eventually you should see the following:

Waf: Leaving directory '/path/to/workspace/ns-allinone-3.32/ns-3.32/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 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 openflow

Leaving directory ./ns-3.32

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.

14 Chapter 3. Getting Started

ns-3 Tutorial, Release ns-3-dev

3.4.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 pybindgen-0.21.0 - OK

>> Building netanim-3.108 - OK

>> Building ns-3.32 - 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 recent portability issue has been that castxml may not build via the bake build tool on all platforms; in this

case, the line will show something like:

>> 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.4.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. An installation of Waf is bundled with the ns-3 source code. 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:

3.4. Building ns-3 15

ns-3 Tutorial, Release ns-3-dev

Setting top to : /home/ns3user/workspace/bake/source/ns-3-

,→dev

Setting out to : /home/ns3user/workspace/bake/source/ns-3-

,→dev/build

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

Checking for cc version : 7.3.0

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

Checking for compilation flag -march=native support : ok

Checking for compilation flag -Wl,--soname=foo support : ok

Checking for compilation flag -std=c++11 support : ok

Checking boost includes : headers not found, please

,→provide a --boost-includes argument (see help)

Checking boost includes : headers not found, please

,→provide a --boost-includes argument (see help)

Checking for program 'python' : /usr/bin/python

Checking for python version >= 2.3 : 2.7.15

python-config : /usr/bin/python-config

Asking python-config for pyembed '--cflags --libs --ldflags' flags : yes

Testing pyembed configuration : yes

Asking python-config for pyext '--cflags --libs --ldflags' flags : yes

Testing pyext configuration : yes

Checking for compilation flag -fvisibility=hidden support : ok

Checking for compilation flag -Wno-array-bounds support : ok

Checking for pybindgen location : ../pybindgen

,→(guessed)

Checking for python module 'pybindgen' : 0.21.0

Checking for pybindgen version : 0.21.0

Checking for code snippet : yes

Checking for types uint64_t and unsigned long equivalence : no

Checking for code snippet : no

Checking for types uint64_t and unsigned long long equivalence : yes

Checking for the apidefs that can be used for Python bindings : gcc-LP64

Checking for internal GCC cxxabi : complete

Checking for python module 'pygccxml' : not found

Checking for click location : not found

Checking for program 'pkg-config' : /usr/bin/pkg-

,→config

Checking for 'gtk+-3.0' : not found

Checking for 'libxml-2.0' : yes

checking for uint128_t : not found

checking for __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 : yes

Checking for header sys/ioctl.h : yes

(continues on next page)

16 Chapter 3. Getting Started

剩余136页未读，继续阅读

Goldstine

粉丝: 3
资源: 1

ns-3网络仿真教程：入门与概念解析

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

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

protoc *.proto --python_out=.

ns3可视化工具pyviz安装

ns3-tutorial

请给我一份ISE的官方文档

MySQL具体学习资料

有没有ns3学习笔记链接

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

zynq DDR/SD/Ethernet/USB/Uart/AD9516/SFP的脚本测试例程

最新资源