next up previous
Next: 5. Advanced Usage Up: IMUNES manual Previous: 3. User Interface Layout


4. Quick Intro

4.1 Simple Network Scenario

In this section we will show how to build, configure and simulate the following simple network topology:

Personal computers (office-pc1 and office-pc2) from the network are connected to the LAN switch (office-switch) which is connected to the router (office-router). The server (office-host) from the network is directly connected to the router (office-router). Personal computers from the first network have route only to the network The server from the second network has the default route. Quagga routing is enabled on the router in order to be able to serve and receive dynamic route updates.

4.1.1 Building a simple network

After running IMUNES on FreeBSD with some kind of X11 window manager (see Section 3), we will build previously described network using tools from the toolbox (see Section 3.1). Adding and deleting network elements

To draw a node click on the corresponding node tool and then click on the work space to place it. To connect nodes click on the Link tool, then click and hold on the source node and go to the destination node.

Now draw a router, a host, a LAN switch and two PCs. Using the Link tool connect the LAN switch to the router and then connect each PC to the LAN switch. Connect the host directly to the router. The created network topology should look like the one in Figure 4.1.

Figure 4.1: Simple network topology

Image simple_topology

When nodes are connected with the Link tool (the direction does not matter), the source node, the destination node and the link get preconfigured parameters automatically. When a node or a link is selected, some of the configured parameters are shown on the left side of the statusbar placed at the bottom of the window (Figure 4.2).

Figure 4.2: Node parameters in the statusbar

Image statusbar1

Some of the parameters can be visible on the canvas: interface names (link layer: e0, e1, e2 and network layer: eth0, eth1), IPv4/IPv6 addresses of network layer elements (PC, host, router), node names (n0, n1, n2, n3, n4) and link labels (e.g bandwidth).

You can manipulate with the visibility of nodes and links parameters from the View menu (Figure 4.3). In this simple scenario we do not want for IPv6 addresses to be visible, so we will turn the Show IPv6 Addresses option off.

Figure 4.3: Show or hide nodes and links parameters

Image view_menu1

To delete the network element select it using the Select tool and then use the Delete keyboard button. You can also delete it by making a right click on it and making a left click on the Delete label in the popped up menu. The node deletion is automatically followed by the deletion of associated links. Rearranging network elements

You can change position of the network element (node or link) and/or the node name. To move both the network element and its name select the network element with the Select tool and drag it to the designated position. To move only the node name select it with the Select tool and drag it to the designated position.

Using the Select tool you can also move around a group of connected nodes which can be selected using the Ctrl keyboard button in addition to the left click. To select the whole network topology use Select All option from the Edit menu.

For automatic rearranging of all network elements or rearranging the selected group of network elements use Rearrange and Rearrange All options from the Tools menu. To stop the rearranging process click with the Select tool.

4.1.2 Configuring a simple network

Although preconfigured parameters of network elements are usually sufficient to start a simulation (automatically provided IPv4/IPv6 addresses, the default static route on the PC and the host and routing model and protocols parameters on the router as well), in this scenario we will set up our own parameters.

To open the network element configuration window:

Figure 4.4: Configure a network element

Image configure_label

Network elements configuration parameters can be also changed through the topology tree. To show the topology tree turn on the Show Topology Tree option from the View menu. The tree with a list of network topology elements (nodes and links) will be shown on the right side of the window (Figure 4.5). To open the network element configuration window make a double click or use the Enter keyboard button on node, interface or link label in the topology tree.

Figure 4.5: Changing configuration parameters through the topology tree

Image topology_tree

Depending on the type of a network element, there are four types of configuration windows: Hub/LAN switch configuration window

The hub/LAN switch configuration window, as well as the configuration windows of other node types, contains a node name field. Besides that it contains only link layer interface parameters.

We will change the LAN switch name and data packet scheduling method (from preconfigured First In First Out (FIFO) data packet scheduling method to Weighted Fair Queuing (WFQ) method).

Change the node name to office-switch. To change data packet scheduling method select the link layer interface e0 from the list of interfaces, choose WFQ option from the Queue menu and click on the Apply button (Figure 4.6).

Figure 4.6: LAN switch configuration window

Image LANswitch_config

Packet scheduling method is now applied and you can see new queuing discipline for interface e0 in the column Queue disc (Figure 4.7).

Figure 4.7: LAN switch configuration window with applied changes

Image LANswitch_config_applied

Repeat the same procedure for the other link layer interfaces. Changed configuration is already applied so you can close the configuration window with the Cancel button but you can also use the Apply and Close button. PC/host configuration window

The PC/host configuration window consists of three subwindows. Each of them is associated with one of the following tabs: Configuration, Interfaces and IPsec (Figure 4.8).

Figure 4.8: Tabs in the PC/hub configuration window

Image pc_config_tabs

Besides a node name field, PC/host configuration window contains routing parameters and custom configuration parameters (in the window associated with the Configuration tab), network interface parameters (in the window associated with the Interfaces tab) and IPsec parameters (in the window associated with the IPsec tab).

We will change the node name, network interface parameters and routing parameters.

Change the host node name to office-host and PC node names to office-pc1 and office-pc2. To change IPv4 address make a left click on the Interfaces tab, select interface eth0 from the list of interfaces, change the IPv4 address field and click on the Apply button (Figure 4.9). We will change the host IPv4 address field to (now it belongs to and PC IPv4 address fields to and (now they belong to network IP address fields require the CIDR notation, so the IPv4 address is followed by a slash and a network length.

Figure 4.9: Changing IPv4 address

Image pc_config_ipv4 Static routes

PC and host both use static routing. The preconfigured routing table contains only the default route. Every static route, as well as the default route, consists of:

  1. the destination network: an IP address which is followed by a slash and a network prefix and
  2. the next hop network interface IP address (which is an IP address without a slash and without a network prefix).

If the route syntax is wrong, that route will be silently ignored.

We will add the static route on office-pc1 and office-pc2 for the network through the gateway (Figure 4.10).

Figure 4.10: Adding the static route on the PC

Image pc_config_staticroutes

On office-host we will change default gateway address to (Figure 4.11).

Figure 4.11: Adding the static route on the PC

Image host_config_staticroutes

IPv6 addresses and default routes (placed below IPv4 addresses and routes) can be deleted.

To apply the changed configuration and close the configuration window click on the Apply and Close button. Router configuration window

The router configuration window, in addition to fields from PC/host configuration window, contains the part for choosing the routing model and protocols.

We will only change the node name and network interface parameters.

Change the node name to office-router and IPv4 addresses on both network interfaces: on the network interface eth0 and on the network interface eth1. Routing models and protocols

There are three possible routing models:

  1. the xorp model (eXtensible Open Router Platform)
  2. the quagga model
  3. the static model

In the case of xorp and quagga routing models there are options for enabling/disabling RIP, RIPng, OSPFv2 and OSPFv3. By default, all new quagga or xorp router instances will have both RIPv2 and RIPng enabled. The defaults can be changed with the Tools $\to$ Routing protocol defaults option from the menubar, which will be applied to all selected routers (if any) at the time of change, as well as to all the subsequentially created ones (see Section 5.3.5). In the case of static routing model router uses routes from the static routes field that has the same syntax as the static routes field in the PC/host configuration window.

We will leave the default router model - quagga with RIP and RIPng protocols enabled, OSPFv2 and OSPFv3 protocols are disabled (Figure 4.12).

Figure 4.12: Routing models and protocols

Image router_config_routingmodels Link configuration window

The link configuration window offers the possibility to configure the link bandwidth (between 0 and 109 bps), the propagation delay (between 0 and 107 $\mu$s), the probability of a bit error rate (between 0 and 10-12) and the probability of package duplication (between 0 and 50%). There are also display properties: the link width (line thickness between 1 and 8) and the link color (red, green, blue, yellow, magenta, cyan or black).

Figure 4.13: Link configuration window

Image link_config

Default values are as follows: the link which transmits packets without errors and without any possibility for the packet duplication with the unlimited link bandwidth and the zero propagation delay. The link width is set to value 2 and the link color is red.

We will leave default values on all links except on the link between office-switch and office-router (Figure 4.14). On that link we will set up the delay of 30 $\mu$s. Delay will be tested during the network simulation with the traceroute tool (see Section 4.1.3). Configured network topology

Configured network topology should look like the one in Figure 4.14.

Figure 4.14: Configured network topology

Image simple_topology_configured

4.1.3 Simulating a simple network Starting an experiment

After the network topology is completely built and properly configured, we will start an experiment with the Experiment $\to$ Execute option from the menubar and IMUNES will switch from the edit mode to the execute mode. In the process of starting an experiment, IMUNES creates and configures the virtual network. That will take a few seconds and all events during that process will be shown in the statusbar placed at the bottom of the window.

NOTE: Although you can draw network topology on any system that supports Tcl/Tk (Linux, FreeBSD, Windows, Mac OS X, Solaris), an experiment can only be started on FreeBSD operating system with root permissions (Figure 4.15 and Figure 4.16)!.

Figure 4.15: Starting an experiment in Windows

Image execute_windows

Figure 4.16: Starting an experiment in FreeBSD without root permissions
Image execute_not_root

In addition to configured parameters, each node will be set with the loop back interface, a router will have the kernel forwarding enabled, while on a host portmap and inetd will be started.

Information about the time spent instantiating the network topology is shown in the statusbar (Figure 4.17).

Figure 4.17: Message about the instantiation of the network topology

Image statusbar3

In the right corner of the statusbar you can also see that IMUNES now works in the execute mode. Options from the node and the link menu

To open the node menu in the execute mode use the right click on the node. Note that the menu in the execute mode is different from the menu in the edit mode. It offers the possibility to open the shell window (X terminal with a Unix shell), Wireshark network sniffer and Opera browser or to Stop / Start the network element. It is also possible to select the node connected to this node (Select adjacent) and to change node icon(Node icon).

Figure 4.18: Network-layer node menu in the execute mode

Image execute_menu

Note that both the node and the link menu in the execute menu offer the possibility to open the configuration window (Configure label).

From the node configuration window in the execute mode it is possible to change only the node name. Other node parameters such as link layer interface parameters, network interface parameters and routing parameters can be changed from shell window on each node. To change those parameters from the node configuration window stop the node (using the Stop label), change parameters and then again start the node (using the Start label).

On the other side, from the link configuration window in the execute mode it is possible to change the following link parameters: link bandwidth, the propagation delay, the probability of a bit error rate and the probability of package duplication. It is also possible to change display properties: the link width and the link color.

We will now check if the virtual network topology is properly configured. Open the shell window (e.g /bin/sh) on the network element (e.g office-pc1).

We will test delay on the link between office-switch and office-router, which is set to 30 $\mu$s using the traceroute tool: Terminating an experiment

To terminate an experiment and switch from the execute mode to the edit mode use the Experiment $\to$ Execute option from the menubar. During the termination process, IMUNES will terminate active services on each node and shut down all network elements (links and nodes with both virtual and physical interfaces). The termination is finished when the message about the successful cleanup shows up in the statusbar (Figure 4.24).

Figure 4.24: Message about the successful cleanup

Image statusbar4

4.2 Configuration files management

4.2.1 Saving a virtual network configuration

After the virtual network is successfully built, configured and tested, it can be saved with File $\to$ Save or File $\to$ Save As options from the menubar. The virtual network topology is saved in IMUNES network configuration file format (.imn).

Figure 4.25: File Save dialog

Image file_save

The structure of the configuration file is simple and suitable for changing with a text editor (see Appendix 8).

4.2.2 Opening a virtual network configuration

To open an existing IMUNES network configuration file use the File $\to$ Open option from the menubar and select it from the invoked File Open dialog.

Figure 4.26: File Open dialog

Image file_open

The other way to open an imn file is to start IMUNES with that file as an argument: imunes simple-topology.imn

next up previous
Next: 5. Advanced Usage Up: IMUNES manual Previous: 3. User Interface Layout
Denis Salopek 2015-04-08