Routers R1-3 will (in the next section) participate in dynamic routing using RIPv2 (Routing Information Protocol version 2). Clients C1 and C2 do not participate in RIPv2; instead they have a default route set to their respective router. The clients run Ubuntu Linux. Figure 19, “Interior Routing Network Topology” shows the addressing (the entire network is numbered out of the 192.168.x.x range of private addresses) and the interface device (“eth0” etc.) on each link.
Each switch here is labelled with a name, which is not particularly used for Ethernet at all, but is used more for management purposes. In particular, VirtualBox will create and manage the switches as needed.
This laboratory uses Virtual LANs (VLANs)
in the middle part of the network. An interface such as
eth0.10 means VLAN 10 on the
eth0 interface, and is presented as a separate
interface, which can have its own address, etc. When configuring
interfaces inside the Vyatta shell, you would refer to this
particular virtual interface as “interface ethernet eth0 vif
10”. The VLAN is created automatically, no special commands are
required.[82]
Complete the following tasks:
Consult the relevant parts of the Vyatta Command
Reference; you will find them in the Lab
Resources/Vyatta/Documentation folder, colour-coded
so you can easily find the most relevant ones. You will be
well advised to make good use of Tab completion.
Configure the basic system for the routers; hostname, accounts (change the default passwords) and interface configuration. Do not enable access via SSH or HTTP, although you are welcome to try it later.
You will also need to configure the interfaces on the clients C1 and C2. Because any configuration will perish upon boot, you can just use ifconfig and route to set up the network interfaces. Refer back to the earlier lab on Basic Interface Management where these commands were practiced.
Configure static routes for all routers. Use
traceroute -n — the -n
enables numeric output, preventing lengthy
DNS timeouts — that you can reach all
networks from all others. If traceroute is
not available try mtr instead. Take a
screenshot of your routing table and testing on all
machines. You should verify that you can get from any
interface in the network to any other interface.
Remove all static routes on R1-3 after you have verified all your work and recorded suitable evidence; you can remove them easily using the configuration command delete protocols static and then commiting your configuration. Once you have the static routes removed, start working on your RIPv2 configuration.
If you only complete up to here (getting Static Routing completed and tested), then you are eligible for partial marks.