== How to build !OverSim with ReaSE support ==

1. Download, extract and compile [https://i72projekte.tm.uka.de/trac/ReaSE/downloads/29 ReaSE-OMNeT4-1.23-src.tar.gz] (in the following we assume you have installed OMNeT++ and !OverSim to ~/sim/):
{{{
  cd ~/sim
  tar xzvf /tmp/ReaSE-OMNeT4-1.23-src.tar.gz
  cd ReaSE
  make OVERSIM=true
}}}

2. Recompile !OverSim with ReaSE support
{{{
  cd ~/sim/OverSim-20101103
  make REASE=true
}}}

3. Edit {{{simulations/default.ini}}} in your !OverSim directory and modify the {{{ned-path}}} to contain the ReaSE directory.

4. Download, extract and install the GUI [https://i72projekte.tm.uka.de/trac/ReaSE/downloads/28 ReaSEGUI-OMNeT4-1.23.tar.gz]:
{{{
  cd ~/sim
  tar xzvf /tmp/ReaSEGUI-OMNeT4-1.23.tar.gz
  cd ~/sim/ReaseGUI/TGM
  make
}}}

5. Start the Java based ReaSEGUI to create new topologies (see [#HowtouseReaSEGUItogenerateatopologyforOverSim below] for additional information on this step):
{{{
  cd ~/sim/ReaSEGUI/ReaSEGUI/dist
  java -jar ReaSEGUI.jar
}}}

6. Copy the generated topology to the !OverSim directory:
{{{
  cp ~/sim/generatedTopologies/MyFirstTopology_servers.ned ~/sim/OverSim-20101103/src/underlay/reaseunderlay/topologies/MyFirstTopology/MyFirstTopology_servers.ned
}}}

7. Edit omnetpp.ini and create a new entry containing your topology:
{{{
  [Config MySimulation]
  network = oversim.underlay.reaseunderlay.topologies.MyFirstTopology.ReaSEUnderlayNetwork
  **.TerminalConnector.channelTypes = "oversim.underlay.reaseunderlay.topologies.MyFirstTopology.host2edge"
  **.TerminalConnector.channelTypesRx = "oversim.underlay.reaseunderlay.topologies.MyFirstTopology.edge2host"
}}}


== How to use ReaSEGUI to generate a topology for !OverSim ==

This section shows how to use ReaSEGUI to generate your own topologies.

=== Customize settings and generate a new topology ===

1. Press "{{{Select TGM Path}}}" on the "{{{Topology}}}" tab and select {{{~/sim/ReaSEGUI/TGM/tgm}}}.

2. Press "Save" and select a location to save your generation parameters.

3. Modify or deselect "AS-Level" parameters. The following parameters can be set:
   * Nodes: Number of autonomous systems generated.
   * Transit-Node-Thresh: Minimum node degree to be a transit AS.
   * Parameter P: PFP Growing Parameter.
   * Parameter Delta: PFP Growing Parameter.

4. Modify "Router-Level" parameters: The following parameters can be set:
   * Min Nodes: Minimum routers nodes per router topology.
   * Max Nodes: Maximum routers nodes per router topology.
   * Core Ratio: Percentage of core router nodes per router topology.
   * Core Cross Link Ratio: Percentage of core cross links.
   * Min Hosts per Edge: Minimum number of hosts per edge router.
   * Max Hosts per Edge: Maximum number of hosts per edge router.

   * ''IMPORTANT NOTE'': In order to use the generated topology with the ReaSEUnderlay "Router-Level" option must not be deselected.

   * ''NOTE'': If the minimum number of Hosts per Edge is not zero ReaSE must be installed and included in !OverSim to use the topology.

5. Choose name and path of the ned file by pressing "select". e.g. {{{~/sim/generatedTopologies/MyFirstTopology.ned}}}
   * ''NOTE'': The name of the ned file will also be the name of the topology.

6. Select the "!OverSim topology" option.

7. Press "Run" in the upper right corner of the tab. Wait a few seconds while the TGM is trying multiple times to generate the topology.


=== Modified bandwiths, latencies, server and router fractions ===

1. Switch to the "Server Settings" tab.

2. Press "Set Script Path" and select {{{~/sim/ReaSEGUI/UtilScripts/setServer.pl}}}.

3. Press "Save" and select a location to save your parameter settings.

4. Modify parameters or press "Default".

5. Press "Run" in the upper right corner of the tab.
   * ''NOTE'': The script writes the modified topology to a new file. e.g. {{{~/sim/generatedTopologies/MyFirstTopology_servers.ned}}}