By Juan Marcos Miguel

Session 15 Lab
4.1 Network A configuration
a. Configure an IPv4 address on the PCA interface.
b. Configure an IP address on the Router A (RA) interface connected to Network A.
c. Verify, using the ping command and the configured addresses, that there is
connectivity between the PCA and the RA (by pinging from both the PC and the
router). Take screenshots showing the result of pinging from PCA to RA, and the
result of pinging from RA to PCA.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

d. Check the configuration of eth1 in PCA and, if applicable, delete any addresses
that do not belong to the scenario (belonging to the default configuration).
e. Check the configuration of the interfaces on Router A. Turn off any interfaces
that are not in use in the scenario. For the interfaces that are in use, delete all the
addresses that do not belong to the scenario (they are in the default
configuration). Take screenshots showing the IP configuration of the interfaces in
PCA and the RA interfaces.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

f. Verify, using the ping command, that the communication between RA and PCA
is still working.

4.2. Network B configuration

g. Repeat the steps in 4.1 to configure Network B (PCC and Router B interface
attached to Network B). Take screenshots showing the IP configuration of the
interfaces on PCC and the interfaces of the RB.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

4.3. Network C Configuration

h. Configure IP addresses on the router interfaces used to interconnect the
routers (interfaces on Network C).
i. Verify that connectivity exists between the two routers by using the
router's ping command to ping from one router to the other (using the IP
addresses configured in Network C).

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Take screenshots showing the result of a ping from one router to the
interface address of the other router on Network C.

4.4. Forwarding Table Configuration

j. Configure on the two routers the necessary entries in their forwarding tables so
that each router can reach the networks that are not directly connected to it. Note
that, when configuring the addresses on the various interfaces, the entries for the
directly connected subnets have already been configured. Remember that you are
looking for the simplest configuration, which means that the forwarding tables
should have as few entries as possible. Refer to the router's guide [6] and manual
[7] to find out how to statically configure IP routes on the router.
k. Configure on each PC the necessary entries in its forwarding tables to be able to
reach networks that are not directly connected to it. To configure the forwarding
tables in Linux, refer to the Linux IP configuration help guide [2]. Take a screenshot
showing the forwarding table in PCC obtained by the 'ip' command. Also write the
forwarding table in the format used in class (Prefix, Outgoing Interface, Next Hop).

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Prefix Outgoing interface Next Hop

0.0.0.0/0 (default) eth1 (10.4.29.2) 10.4.29.1
10.4.29.0/28 eth1 (10.4.29.2) -
10.4.29.16/30 eth1 (10.4.29.2) 10.4.29.1
10.4.28.0/24 eth1 (10.4.29.2) 10.4.29.1

Display the forwarding table on Router B (RB) using the corresponding command
(see manual), and take a screenshot showing the obtained forwarding table. Also
write the forwarding table in the format used in class (Prefix, Outgoing Interface,
Next Hop).

Prefix Outgoing interface Next Hop

0.0.0.0/0 (default) eth0.2 (10.4.29.18) 10.4.29.17
10.4.29.0/28 eth0.1 (10.4.29.18) -
10.4.29.16/30 eth0.2 (10.4.29.2) 10.4.29.17
10.4.28.0/24 eth0.2 (10.4.29.2) 10.4.29.17

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

4.5. Checking connectivity and the routes followed by the traffic

l. Ping from PCA to the RA interface facing Network A. Then from PCA to the RA
interface facing Network C. Then from PCA to the RB interface facing Network C.
Then from PCA to the RB interface facing Network B. Then from PCA to the RB
interface facing Network B. Finally, from PCA to PCC. By doing these connectivity
tests systematically, if one of the steps fails, it is easier to determine where the
problem may be originating.
m. You can repeat the process from PCC.
n. Check the route that IP packets follow, using the traceroute -n command. By
default, traceroute attempts to do reverse resolution of the IP addresses it
discovers, i.e., it asks the DNS for the name corresponding to the addresses, so
that it outputs the command with names instead of addresses. The '-n' option
causes traceroute to directly present the IP addresses in the command output.
This is more appropriate in our case because the addresses in the scenario are not
registered in the DNS, and the reverse resolution attempt just leads to additional
delay while waiting for a response that does not occur.
If any connectivity test does not work, you should review the various
configurations made to fix the problem.
Check the connectivity between networks A and B in the scenario by pinging and
traceroute from PCA to PCC. Take screenshots showing the output of the
commands.
Pinging all interfaces from PCA:

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Traceroute from PCA to PCC:

5.- Advanced scenario

Let us complete the configuration of the scenario. This is shown in Figure 2 (which
already matches the scenario in the UC3M Virtual Lab). In other words, we are
going to configure two more PCs (PCB and PCD) and an additional link between
the RA and RB routers (which we call Network D).
a. Use the address space that has been freed up in your addressing plan and assign
a prefix to network D. Network D must be able to host 2 interfaces.
b. Assign and configure IP addresses on the router interfaces used to interconnect
the routers. These IP addresses must belong to the prefix obtained in (a).
c. Remember, if you have switched off the eth0.3 interfaces of the routers in
sections 4.1 and 4.2, you need to switch them on again. Also, if there are default
addresses on the interfaces that do not belong to the scenario, you will need to
delete them.
d. Verify that there is connectivity between the two routers using the new link by
pinging from one router to the IP of the other router's interface on Network D.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Indicate the prefix assigned to Network D. Take a screenshot of the result of the
ping in section 5.d.

The prefix of Network D is 10.4.29.20/30, the two interfaces connected are 10.4.29.21 (RA) and
10.4.29.22 (RB).

e. Add a static route on Router A to go to a prefix that includes the upper half of
Network B's prefix addresses, and route the corresponding traffic through
Network D.
f. Add on Router B a static route to go to a prefix that includes the upper half of
the prefix addresses of Network A and directs the corresponding traffic through
Network D.
Reflect on the effect of this configuration. What will now happen to the traffic
between Networks A and B? Take a screenshot showing the forwarding table for
Router A and another showing the forwarding table for Router B.
By adding these entries to the forwarding table, we are splitting the traffic between Networks A
and B between Networks C and D. All packets directed to the lower half of the prefix addresses
of subnets A and B will go through Network C and the ones directed to the upper half of the
prefix addresses will go through Network D.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

g. Configure on the eth1 interface of PCB an IP address belonging to the prefix

assigned to Network A. If the IP address of PCA belongs to the lower half of the
prefix of Network A, the IP address chosen for PCB must be from the upper half of
the prefix. If the IP address of PCA belongs to the upper half of the Network A
prefix, the IP address chosen for PCB must be from the lower half of the prefix.
h. Configure an IP address belonging to the prefix assigned to Network B on the
eth1 interface of PCD. If the IP address of PCC belongs to the lower half of the
Network B prefix, the IP address chosen for PCD must be from the upper half of
the prefix. If the IP address of PCC belongs to the upper half of the Network B
prefix, the IP address chosen for PCD must be from the lower half of the prefix
i. Perform traceroutes, with the -n option, from PCA to PCC, PCA to PCD, PCB to
PCC, and PCB to PCD.
Take screenshots showing the IP configuration of the PCB interfaces and the PCD
interfaces.

Take screenshots of the results of the traceroutes of section 5.i. Explain the result
of the traceroutes, looking at the intermediate hops and checking if they are what
you expect. Hint: we are in a situation, in some cases, of asymmetric traffic (traffic
in one direction does not go the same way as traffic in the other direction) and, in
the traceroute, TTL exceeded error messages are generated on a router and sent
to the PC from where the traceroute was made.

Group 3: Juan Marcos, Nixi Chen and David Pérez

By Juan Marcos Miguel

The traceroute from PCA to PCC is exactly as we could have expected, since PCC belongs to the
lower half of the address block of Network B, the packets are sent through Network C, and that
is the route we receive.

However, the traceroute from PCA to PCD is strange. PCD belongs to the upper half of the
address block of Network B, so it should have been sent through Netwoek D. However, the route
the command generates seems to be go through Network C. This is explained by the asymmetric
traffic mentioned in the statement: the packets sent to PCD do actually go through Network D,
but, since the packet indicating that TTL has reached 0 is created in RB and its destination is PCA,
which belongs to the lower half of the address block of Network A, this packet is sent through
Network C. Since the packets indicating that TTL reached 0 are the ones actually used by the
traceroute command to determine the route, the result it yields looks as if the packets destined
to PCD go through Network C instead of D

When we execute the traceroutes from PCB, we get the opposite result than with PCA: the route
to PCD is exactly as expected, but the route to PCC is strange, as if the packets had gone through
Network C instead of D. The explanation is the same as in the previous case, the packets sent to
PCC do go through Network C (as PCC belongs to the lower half of the address block), but since
the packet saying that the TTL ran out is generated in RB and directed to PCB, which belongs to
the upper half of the address block of its network, it goes through network D. When the
traceroute command uses that packet to show the route, it seems as if the packets sent to PCC
go through Network D, when they don’t.

From the previous cases we can conclude that the traceroute command does not actually show
the route the packets follow to reach their destination, but the one they follow to get back to
our PC.

Group 3: Juan Marcos, Nixi Chen and David Pérez