SimulationConfiguration

From Nsnam
Revision as of 17:47, 2 November 2009 by Craigdo (Talk | contribs) (New page: In order to configura simulations across multiple, probably virtualized, machines a large amount of configuration must be performed in order to construct the component systems. For exampl...)

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

In order to configura simulations across multiple, probably virtualized, machines a large amount of configuration must be performed in order to construct the component systems. For example, boxes with appropriate software must be put together, and dozens or perhpas hundreds of taps, bridges etc. must be configured in order to construct a topology. The oppportunity for human error to creep in during this process renders it essentially manually unworkable for all but the simplest topologies.

This real-world configuration information needs to be imported into ns-3 and the various systems and devices need to be mapped to ns-3 constructs. For example, if a number of linux hosts are configured to participate in a wireless network using tap bridges, each ns-3 ghost node needs to know