SimulationConfiguration: Difference between revisions
No edit summary |
|||
| Line 3: | Line 3: | ||
== Simulation Configuration == | == Simulation Configuration == | ||
In order to | In order to configure 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 | 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 which host it is pretending to be and which device on that host it should be bridging to a wifi net device. | ||
---- | ---- | ||
[[User:Craigdo|Craigdo]] 17:49, 2 November 2009 (UTC) | [[User:Craigdo|Craigdo]] 17:49, 2 November 2009 (UTC) | ||
Revision as of 17:49, 2 November 2009
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
Simulation Configuration
In order to configure 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 which host it is pretending to be and which device on that host it should be bridging to a wifi net device.
Craigdo 17:49, 2 November 2009 (UTC)