doc/manual/source/tcp.rst
changeset 7145 a925e518220b
parent 7024 4392d52b3536
child 7147 71adbc0422a5
equal deleted inserted replaced
7144:9c60c34c6527 7145:a925e518220b
   193     ./waf --run tcp-nsc-lfn
   193     ./waf --run tcp-nsc-lfn
   194 
   194 
   195 These examples will deposit some ``.pcap`` files in your directory,
   195 These examples will deposit some ``.pcap`` files in your directory,
   196 which can be examined by tcpdump or wireshark.
   196 which can be examined by tcpdump or wireshark.
   197 
   197 
   198 Let's look at the ``examples/tcp-nsc-zoo.cc`` file for some typical
   198 Let's look at the ``examples/tcp/tcp-nsc-zoo.cc`` file for some typical
   199 usage. How does it differ from using native |ns3| TCP? There is one main
   199 usage. How does it differ from using native |ns3| TCP? There is one main
   200 configuration line, when using NSC and the |ns3| helper API, that needs to be
   200 configuration line, when using NSC and the |ns3| helper API, that needs to be
   201 set:::
   201 set:::
   202 
   202 
   203   InternetStackHelper internetStack;
   203   InternetStackHelper internetStack;
   231 NSC TCP shares the same configuration attributes that are common across TCP
   231 NSC TCP shares the same configuration attributes that are common across TCP
   232 sockets, as described above and documented in `Doxygen
   232 sockets, as described above and documented in `Doxygen
   233 <http://www.nsnam.org/doxygen/classns3_1_1_tcp_socket.html>`_
   233 <http://www.nsnam.org/doxygen/classns3_1_1_tcp_socket.html>`_
   234 
   234 
   235 Additionally, NSC TCP exports a lot of configuration variables into the 
   235 Additionally, NSC TCP exports a lot of configuration variables into the 
   236 |ns3| :ref:`Attributes` system, via a `sysctl <http://en.wikipedia.org/wiki/Sysctl>`_-like interface. In the ``examples/tcp-nsc-zoo`` example, you
   236 |ns3| :ref:`Attributes` system, via a `sysctl <http://en.wikipedia.org/wiki/Sysctl>`_-like interface. In the ``examples/tcp/tcp-nsc-zoo`` example, you
   237 can see the following configuration:::
   237 can see the following configuration:::
   238 
   238 
   239 
   239 
   240   // this disables TCP SACK, wscale and timestamps on node 1 (the attributes 
   240   // this disables TCP SACK, wscale and timestamps on node 1 (the attributes 
   241     represent sysctl-values).
   241     represent sysctl-values).