interface-topo.php

to define a topology with a graphical interface. This page allows you to define a basic topology in a easy way: access points linked to a simple core. You won't be able to define all the possible topologies with this tool! In each step, the configuration options are looked and respected. Seven steps are applied:

1. Access points and clients. Define the number of access points and the number of clients connected to each access point.
2. Link definition. The clients with access points links are on a local network. For this reason you will define only the access-point to core routers links. You must choose the farest access point from the core, and then fill the data (latency, loss, duplication). On a second part you must choose another couple of routers and fill the data again. This system is useful because normally, you will know the access point to access point data, and not the access point to core router data.
3. Throughput limit. You can specify throughput limits from the local networks on each access point or from the links in the core.
4. Core topology. To choose between a star or a ring topology to rely all the core routers.
5. Cross traffic. If there are enough machines, a graphical representation of the topology is given and then you can add cross traffic generators by clicking on an interface name.
6. Other options. To choose the QoS option, IP version and packet size. These three options are not fully implemented on eWAN nowadays.
7. End. To save your configuration file or use it directly on the current session.

Three links are shown on the final page:

1. Save the configuration file. Save the topology on your machine, not on the eWAN server.
2. Begin the deployment. Deploy with the defined topology
3. Back home