HOWTO use CORE to test ns-3 TCP

From Nsnam
Revision as of 17:48, 2 September 2014 by Tomh (Talk | contribs) (Created page with "{{TOC}} This is a use case for the parent page of HOWTO Use CORE to test ns-3 protocols == Use case summary == We want to test the operation of ns-3's TCP with the TCP ...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

This is a use case for the parent page of HOWTO Use CORE to test ns-3 protocols

Use case summary

We want to test the operation of ns-3's TCP with the TCP of other operating systems, for correctness and interoperability. We want the ns-3 TCP to operate as a client and a server (in different test runs).

A key consideration is what will be the application that will drive the TCP. Note that if there are any application-level semantics in the bit stream being exchanged, whatever is sitting on top of ns-3's TCP must be able to interoperate with whatever is sitting on top of the real node's TCP.

Iperf is a popular testing tool, but it has exactly these types of application-level semantics-- iperf will not interoperate with an ns-3 application. Fortunately, the ns-3 Direct Code Execution mode supports iperf, so we will describe that herein.

Another alternative (not written up here) would be to use Stevens's sock program as the real node's application, and either BulkSendApplication or PacketSink as the ns-3 application.

Prerequisites

We are aiming for the following configuration. (to be completed)

Retrieved from "https://www.nsnam.org/mediawiki/index.php?title=HOWTO_use_CORE_to_test_ns-3_TCP&oldid=8961"