Skip to content

layer3_configuration

Thomas Holterbach edited this page Apr 3, 2022 · 7 revisions

Layer-3 configuration

The files l3_routers.txt and l3_links.txt describe the layer-3 topology. Besides the topology, additional parameters are set to different routers. We describe these two configuration files and their parameters in the following sections.

This file contains all the routers in the layer-3 topology. The following table shows an example of this configuration file.

 C1     C2                         C3                          C4
-------------------------------------------------------------------
ZURI	DNS           L2-DCN:miniinterneteth/d_host           linux
BASE	N/A           L2-DCN:miniinterneteth/d_host           vtysh
GENE	N/A           L2-DCS:miniinterneteth/d_host           linux
LUGA	N/A           routinator:miniinterneteth/d_routinator vtysh
MUNI	N/A           host:miniinterneteth/d_host             vtysh
LYON	MATRIX        host:miniinterneteth/d_host             vtysh
VIEN	MATRIX_TARGET host:miniinterneteth/d_host             vtysh
MILA	MEASUREMENT   host:miniinterneteth/d_host             vtysh

Below is the description of each column.

C1: Name of the router.
C2: Service associated to the router. Only one service can be associated to a given router. The possible services are the following:
    - MATRIX: where the pings used for the matrix are sent.
    - MATRIX_TARGET: the destination of the pings used for the matrix.
    - DNS: to which router the DNS container is connected to.
    - MEASUREMENT: to which router the MEASUREMENT container is connected to.
    - N/A: no service.
C3: Information about the host or layer-2 network connected to the corresponding router. Here are the following possible options (before the colon):
    - host: only one host is connected to the router.
    - L2-X: the router is connected to the l2-network X. Aside from the l2-network, there is also a single host connected to the router.
    - routinator: one host running routinator (for RPKI) is connected to the router.
    - krill: one host running krill (for RPKI) is connected to the router.
    This column also includes (after the colon) the docker image to use for the host that is connected to the router.
C4: Indicate wether the students can access the router container with bash or can only access the CLI. 

You can use C3 to plug-in any docker images you want (e.g., with a webserver or a VLC client).

In C4, vtysh means the students can only access the CLI of the router whereas anything else means the students can access the router container using bash (via the goto.sh script, using the keyword container instead of router). This is used to answer questions that require the linux commands (such as configuring 6in4 tunnels).

internal_links_config_full.txt (or internal_links_config_small.txt): This is the internal topology. The first two columns indicate which pair of routers are interconnected, the last two columns indicate the throughput and delay of the link, respectively.