项目作者: signetlabdei

项目描述 :
QUIC implementation for ns-3
高级语言: C++
项目地址: git://github.com/signetlabdei/quic-ns-3.git
创建时间: 2019-02-15T08:27:25Z
项目社区:https://github.com/signetlabdei/quic-ns-3

开源协议:GNU General Public License v2.0

下载


QUIC implementation for ns-3

QUIC code base

This repository contains in the src/quic and src/applications the code for the implementation of the QUIC protocol for ns-3.

The implementation is described in this paper.

Please use the issue tracker for bugs/questions.

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

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.

The process of contributing to the ns-3 project varies with
the people involved, the amount of time they can invest
and the type of model they want to work on, but the current
process that the project tries to follow is described here:
http://www.nsnam.org/developers/contributing-code/

This README excerpts some details from a more extensive
tutorial that is maintained at:
http://www.nsnam.org/documentation/latest/

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

  1. ./waf configure --enable-examples

followed by

  1. ./waf

in the directory which contains this README file. The files
built will be copied in the build/ directory.

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.

Running ns-3

On recent Linux systems, once you have built ns-3 (with examples
enabled), it should be easy to run the sample programs with the
following command, such as:

  1. ./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
The program source can be found in the examples/routing directory.

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 3) 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/documentation/.

This documentation includes:

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 git. A quick and dirty cheat sheet is included
in the manual, but reading through the git
tutorials found in the Internet is usually a good idea if you are not
familiar with it.

If you have successfully installed git, you can get
a copy of the development version with the following command:

  1. git clone https://gitlab.com/nsnam/ns-3-dev.git

However, we recommend to follow the Gitlab guidelines for starters,
that includes creating a Gitlab account, forking the ns-3-dev project
under the new account’s name, and then cloning the forked repository.
You can find more information in the manual [link].

ca-setup-radio-bearer_1647802829312.pdf
ca-test-example-dl_1647802829391.pdf
ca-test-example-ul_1647802829612.pdf
ca-uplink-bsr_1647802829634.pdf
carrier-aggregation-impact_1647802829648.pdf
carrier-aggregation-mac-impact_1647802829692.pdf
fading_pedestrian_1647802829734.pdf
fading_urban_3kmph_1647802829773.pdf
fading_vehicular_1647802829801.pdf
helpers_1647802829830.pdf
lte-enb-rrc-states_1647802829853.pdf
lte-ffr-soft-2-spectrum-trace_1647802829858.pdf
lte-fr-hard-1-rem_1647802829878.pdf
lte-fr-hard-2-rem_1647802829909.pdf
lte-fr-hard-3-rem_1647802829974.pdf
lte-fr-soft-1-rem_1647802829997.pdf
lte-handover-algorithm_1647802830003.pdf
lte-handover-campaign-rem_1647802830020.pdf
lte-legacy-handover-algorithm_1647802830044.pdf
lte-phy-interference_1647802830048.pdf
lte-ue-rrc-states_1647802830065.pdf
mac-random-access-contention_1647802830069.pdf
mac-random-access-noncontention_1647802830072.pdf
miesm_scheme_1647802830183.pdf
nas-attach_1647802830187.pdf
rrc-connection-establishment_1647802830234.pdf
rrc-connection-reconfiguration-handover_1647802830237.pdf
rrc-connection-reconfiguration_1647802830254.pdf
lte-mcs-index_1647802830663.pdf
animation-dumbbell_1647802830752.pdf
NetAnim_3_105_1647802830763.pdf
NodeCountersChart_1647802830781.pdf
NodeCountersTable_1647802830807.pdf
PacketStatistics_1647802830825.pdf
PacketTimeline_1647802830872.pdf
Precision_1647802830887.pdf
RoutingTables_1647802830890.pdf
Trajectory_1647802830894.pdf
spectrum-channel-phy-interface_1647802830995.pdf
MCS_12_test_1647802829162.pdf
MCS_13_16_1647802829164.pdf
MCS_16_test_1647802829167.pdf
MCS_17_20_1647802829170.pdf
MCS_1_4_1647802829182.pdf
MCS_21_24_1647802829218.pdf
MCS_25_28_1647802829222.pdf
MCS_29_29_1647802829232.pdf
MCS_2_test_1647802829241.pdf
MCS_5_8_1647802829244.pdf
MCS_9_12_1647802829248.pdf
ca-downlink-bsr_1647802829258.pdf