Routing Lab

By Luis Daniel Casais Mezquida & Javier Moreno Yébenes
Computer Networks 22/23
Bachelor's Degree in Computer Science and Engineering, grp. 89
Universidad Carlos III de Madrid

Network configuration using Linksys WRT54GS routers.

Part 0: Setup

Download and run the Virtual Machine
Update the simulator twice

lightning update

Part I: Simple network interconnection

Start the VM and load the scenario.

student@uc3m:~$ lightning start RSC/S16_escenario_1

Desired configuration:

Network	Segment
`A`	`10.0.3.0/24`
`B`	`10.0.4.0/24`
`RA-RB`	`10.0.0.0/30`

Device	Interface	IP
`RA`	`eth0.0`	`10.0.3.2/24`
	`eth0.1`	`10.0.0.1/30`
`RB`	`eth0.0`	`10.0.4.2/24`
	`eth0.1`	`10.0.0.2/30`
`PCA`	`eth1`	`10.0.3.1/24`
`PCB`	`eth1`	`10.0.4.1/24`

Remove the default IP addresses assigned to the `eth0.0` through `eth0.4` and `wlan0` interfaces in the routers.

RA# show interface eth0.0

[...]
inet=192.168.0.1/24
[...]

RA# configure terminal  # enter config mode
RA(config)# interface eth0.0  # select interface
RA(config-if)# no ip adress 192.168.0.1/24  # pre-configured IP (one received with show interface)
RA(config-if)# exit

Do the same for eth0.1, eth0.2, eth0.3, eth0.4, wlan0, and for router RB.

RA(config)# exit
RA# show interface eth0.0  # to check it was done correctly, inet shouldn't show

Assign an IP address to the Ethernet interface `eth1` of computer `PCA` that is connected to Network `A`

First we see the asigned IPs for PCA and PCB.

student@PCA:~$ ip a

[...]
3: eth1@[...]
[...]
inet=192.100.101/24  # default PCA IP
[...]

Remove the default IP.

student@PCA:~$ sudo ip addr del 192.100.100.101/24 dev eth1

Do the same for PCB.

Assign an IP address to the interface of `RA` that is connected to the Network `A`

Add IP to PCA.

student@PCA:~$ sudo ip addr add 10.0.3.1/24 dev eth1

Configure RA interface w/ PCA.

RA# configure terminal
RA(config)# interface eth0.0
RA(config-ip)# ip address 10.0.3.2/24
RA(config-ip)# exit 
RA(config)# exit

Verify that the router and the host can reach each other using the ping command.

Check that you can ping from PCA to RA.

student@PCA:~$ ping 10.0.3.2

Connect `RA` and `RB` through their Ethernet interfaces.

Assign IP addresses to the interfaces that connect both routers.

RA# configure terminal
RA(config)# interface eth0.1
RA(config-ip)# ip address 10.0.0.1/30
RA(config-ip)# exit 
RA(config)# exit

RB# configure terminal
RB(config)# interface eth0.1
RB(config-ip)# ip address 10.0.0.2/30
RB(config-ip)# exit
RB(config)# exit

Verify that routers can reach each other using the ping command.

RA# ping 10.0.0.2

RB# ping 10.0.0.1

Assign an IP address to the interface of `RB` connected to Network `B`

Add IP to PCB.

student@PCB:~$ sudo ip addr add 10.0.4.1/24 dev eth1

Configure RB interface w/ PCB.

RB# configure terminal
RB(config)# interface eth0.0
RB(config-ip)# ip address 10.0.4.2/24
RB(config-ip)# exit 
RB(config)# exit

Verify that the router and the host can reach each other using the ping command.

Check that you can ping from PCA to RA.

student@PCB:~$ ping 10.0.4.2

Configure in both routers the routing table entries so that router A can reach network B and vice versa

Forward stuff to Network B (10.0.4.0/24) through RB eth0.1 (10.0.0.2).

RA# configure terminal
RA(config)# ip route 10.0.4.0/24 10.0.0.2

Forward stuff to Network A (10.0.3.0/24) through RA eth0.1 (10.0.0.1).

RB# configure terminal
RB(config)# ip route 10.0.4.0/24 10.0.0.1

Configure the routing tables in `PCA` so it can reach Network `B`

Route stuff to the outside (default/0.0.0.0/0), and Network B (10.0.4.0/24) through RA eth0.0 (10.0.3.2).

student@PCA:~$ sudo ip route add default via 10.0.3.2
student@PCA:~$ sudo ip route add 10.0.4.0/24 via 10.0.3.2

Perform the corresponding settings in PCB

Route stuff to the outside (default/0.0.0.0/0), and Network A (10.0.3.0/24) through RB eth0.0 (10.0.4.2).

student@PCB:~$ sudo ip route add default via 10.0.4.2
student@PCB:~$ sudo ip route add 10.0.3.0/24 via 10.0.4.2

Use the `ping` and `traceroute` command from `PCA` to `PCB`

student@PCA:~$ ping 10.0.4.1
student@PCB:~$ ping 10.0.3.1

student@PCA:~$ traceroute -n 10.0.4.1
student@PCB:~$ traceroute -n 10.0.3.1

Close lightning with

student@uc3m:~$ lightning stop

Part II: Network configuration

Start the VM and load the scenario.

student@uc3m:~$ lightning start RYSCA/p_encam_a

Configuration:

We'll use the 10.0.98.0/24 segment.

Network	Segment
`O1`	`10.0.98.0/25`
`O2`	`10.0.98.128/27`
`S`	`10.0.98.160/28`
`R1-R2`	`10.0.98.176/30`
`R1-R3`	`10.0.98.180/30`
`R2-R3`	`10.0.98.184/30`
`R3-R4`	`10.0.98.188/30`
`I`	`10.0.0.0/24`
`M`	`10.0.0.100/24`

Device	Interface	IP
`R1`	`eth0.0`	`10.0.98.1/25`
	`eth0.1`	`10.0.98.182/30`
	`eth0.2`	`10.0.98.177/30`
`R2`	`eth0.1`	`10.0.98.129/27`
	`eth0.2`	`10.0.98.178/30`
	`eth0.3`	`10.0.98.185/30`
`R3`	`eth0.1`	`10.0.98.161/28`
	`eth0.2`	`10.0.98.189/30`
	`eth0.3`	`10.0.98.181/30`
	`eth0.4`	`10.0.98.186/30`
`R4`	`eth0.1`	`10.0.0.69/24`
	`eth0.2`	`10.0.98.190/30`
`hstOfi1`	`eth1`	`10.0.98.2/25`
`hstOfi2`	`eth1`	`10.0.98.130/27`
`R100`	`eth0.0`	`10.0.100.100/24`
	`eth0.1`	`10.0.0.100/24`

DO NOT TOUCH R100.

Assign IP addresses to the router interfaces

(for each router Rx, each interface eth0.y)

Rx# configure terminal
Rx(config)# interface eth0.y
Rx(config-if)# no ip adress <old_ip>
Rx(config-ip)# ip address <new_ip>  # ip with prefix
Rx(config-ip)# exit 
Rx(config)# exit

Also remember to delete wlan0

Assign IP addresses to the hosts

(for each host hstOfix):

student@hstOfix:~$ ip a  # show ip
student@hstOfix:~$ sudo ip addr del <old_ip> dev eth1
student@hstOfix:~$ sudo ip addr add <new_ip> dev eth1  # ip with prefix

Check that connectivity exists between PCs `hstOfi1`, `hstOfi2` and the routers `R1`, `R2`

Ping from hstOfix to Ry (for each host hstOfix, router Ry):

student@hstOfix:~$ ping <ip Ry eth0.1>  # ip without prefix
Ry ping <ip hstOfix>

Check connectivity in each of the point-to-point network that interconnects the routers

Ping from Rx ethi to Ry ethj (for each pair of routers in the same network, using the correct interfaces, the ones "pointing" to the other router)

Rx# ping <ip Ry ethj>
Ry# ping <ip Rx ethi>

Configure the required static routes in the routers (routing tables)

Remember to put all routes, and that direct connections don't need to be configured.

The routing tables are:

R1

Network	Destination	Next Hop	Metric
`O2`	`10.0.98.128/27`	`10.0.98.178`	1
	`10.0.98.128/27`	`10.0.98.181`	5
`S`	`10.0.98.160/28`	`10.0.98.181`	1
	`10.0.98.160/28`	`10.0.98.178`	5
`R2-R3`	`10.0.98.184/30`	`10.0.98.178`	1
	`10.0.98.184/30`	`10.0.98.181`	5
`R3-R4`	`10.0.98.188/30`	`10.0.98.178`	1
	`10.0.98.188/30`	`10.0.98.181`	5
`I`	`10.0.0.0/24`	`10.0.98.181`	1
	`10.0.0.0/24`	`10.0.98.178`	5
`M`	`10.0.100.0/24`	`10.0.98.181`	1
	`10.0.100.0/24`	`10.0.98.178`	5

R2

Network	Destination	Next Hop	Metric
`O1`	`10.0.98.0/25`	`10.0.98.177`	1
	`10.0.98.0/25`	`10.0.98.186`	5
`S`	`10.0.98.160/28`	`10.0.98.186`	1
	`10.0.98.160/28`	`10.0.98.177`	5
`R1-R3`	`10.0.98.180/30`	`10.0.98.177`	1
	`10.0.98.180/30`	`10.0.98.186`	5
`R3-R4`	`10.0.98.188/30`	`10.0.98.186`	1
	`10.0.98.188/30`	`10.0.98.177`	5
`I`	`10.0.0.0/24`	`10.0.98.186`	1
	`10.0.0.0/24`	`10.0.98.177`	5
`M`	`10.0.100.0/24`	`10.0.98.186`	1
	`10.0.100.0/24`	`10.0.98.177`	5

R3

Network	Destination	Next Hop	Metric
`O1`	`10.0.98.0/25`	`10.0.98.182`	1
	`10.0.98.0/25`	`10.0.98.185`	5
`O2`	`10.0.98.128/27`	`10.0.98.185`	1
	`10.0.98.128/27`	`10.0.98.182`	5
`R1-R2`	`10.0.98.176/30`	`10.0.98.182`	1
	`10.0.98.176/30`	`10.0.98.185`	5
`I`	`10.0.0.0/24`	`10.0.98.190`	1
`M`	`10.0.100.0/24`	`10.0.98.190`	1

R4

Network	Destination	Next Hop	Metric
*	`10.0.98.0/24`	`10.0.98.189`	1

The metrics are used to set the priority of each route. By default, it's 1 (max priority), so set the secondary routes to 5 (you can leave the rest empty).

Let's configure the tables (for each router Rx, each entry in the routing table)

Rx# configure terminal
Rx(config)# ip route <dest> <next hop> <metric>

You can check the configuration with:

Rx# show ip route

To delete a configured route:

Rx(config)# no ip route <dest> <next hop>

Configure the required static routes in the hosts (routing tables)

(for each host hstOfix connected to router Ry)

student@hstOfix:~$ sudo ip route add default via <ip Ry eth0.1>

You can check the configuration with:

student@hstOfix:~$ ip route

To delete a configured route:

student@hstOfix:~$ sudo ip route del <dest> <next hop>

Check the network is connected

You can both use ping and traceroute (traceroute is more useful for debugging).

Let's check if it reaches from hstOfi1 to hstOfi2, and vice versa.

student@hstOfi1:~$ ping 10.0.98.130

student@hstOfi2:~$ ping 10.0.98.2

Now let's check it reaches outside.

student@hstOfi2:~$ ping 10.0.0.69

Force a link failure, use the interface configuration command shutdown to disable the interfaces on both the routers connected to the link

Let's cut link between R1 and R2 and try to reach from hstOfi1 to hstOfi2

R1(config)# interface eth0.3
R1(config-if)# shutdown

R2(config)# interface eth0.2
R2(config-if)# shutdown

To restore the link.

R1(config-if)# no shutdown

R2(config-if)# no shutdown

And traceroute:

student@hstOfi1:~$ traceroute -n 10.0.98.130

Part III: RIP protocol

First remove the static routes previously configured in the routers (no ip route).

Enable and configure the dynamic routing protocol RIP in the corresponding router interfaces

(for each router Rx in network Ny through interface eth0.z)

Rx# configure terminal
Rx(config)# router rip
Rx(config-router)# network <ip Ny>
Rx(config-router)# network eth0.z

You can check your config with:

Rx# show ip rip
Rx# show ip rip status

To delete something:

Rx(config-router)# no network <ip Ny>
Rx(config-router)# no network eth0.z

Check it works

Ping from router to router, and from PC to PC.

student@hstOfi1:~$ ping 10.0.98.130

student@hstOfi2:~$ ping 10.0.98.2

Now let's check it reaches outside.

student@hstOfi2:~$ ping 10.0.0.69

Name		Name	Last commit message	Last commit date
Latest commit History 10 Commits
img		img
README.md		README.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Routing Lab

Part 0: Setup

Part I: Simple network interconnection

Start the VM and load the scenario.

Remove the default IP addresses assigned to the `eth0.0` through `eth0.4` and `wlan0` interfaces in the routers.

Assign an IP address to the Ethernet interface `eth1` of computer `PCA` that is connected to Network `A`

Assign an IP address to the interface of `RA` that is connected to the Network `A`

Connect `RA` and `RB` through their Ethernet interfaces.

Assign an IP address to the interface of `RB` connected to Network `B`

Configure in both routers the routing table entries so that router A can reach network B and vice versa

Configure the routing tables in `PCA` so it can reach Network `B`

Perform the corresponding settings in PCB

Use the `ping` and `traceroute` command from `PCA` to `PCB`

Part II: Network configuration

Start the VM and load the scenario.

Assign IP addresses to the router interfaces

Assign IP addresses to the hosts

Check that connectivity exists between PCs `hstOfi1`, `hstOfi2` and the routers `R1`, `R2`

Check connectivity in each of the point-to-point network that interconnects the routers

Configure the required static routes in the routers (routing tables)

Configure the required static routes in the hosts (routing tables)

Check the network is connected

Force a link failure, use the interface configuration command shutdown to disable the interfaces on both the routers connected to the link

Part III: RIP protocol

Enable and configure the dynamic routing protocol RIP in the corresponding router interfaces

Check it works

About

ldcas-uc3m/CN-Lr

Folders and files

Latest commit

History

Repository files navigation

Routing Lab

Part 0: Setup

Part I: Simple network interconnection

Start the VM and load the scenario.

Remove the default IP addresses assigned to the eth0.0 through eth0.4 and wlan0 interfaces in the routers.

Assign an IP address to the Ethernet interface eth1 of computer PCA that is connected to Network A

Assign an IP address to the interface of RA that is connected to the Network A

Connect RA and RB through their Ethernet interfaces.

Assign an IP address to the interface of RB connected to Network B

Configure in both routers the routing table entries so that router A can reach network B and vice versa

Configure the routing tables in PCA so it can reach Network B

Perform the corresponding settings in PCB

Use the ping and traceroute command from PCA to PCB

Part II: Network configuration

Start the VM and load the scenario.

Assign IP addresses to the router interfaces

Assign IP addresses to the hosts

Check that connectivity exists between PCs hstOfi1, hstOfi2 and the routers R1, R2

Check connectivity in each of the point-to-point network that interconnects the routers

Configure the required static routes in the routers (routing tables)

Configure the required static routes in the hosts (routing tables)

Check the network is connected

Force a link failure, use the interface configuration command shutdown to disable the interfaces on both the routers connected to the link

Part III: RIP protocol

Enable and configure the dynamic routing protocol RIP in the corresponding router interfaces

Check it works

About

Resources

Stars

Watchers

Forks

Remove the default IP addresses assigned to the `eth0.0` through `eth0.4` and `wlan0` interfaces in the routers.

Assign an IP address to the Ethernet interface `eth1` of computer `PCA` that is connected to Network `A`

Assign an IP address to the interface of `RA` that is connected to the Network `A`

Connect `RA` and `RB` through their Ethernet interfaces.

Assign an IP address to the interface of `RB` connected to Network `B`

Configure the routing tables in `PCA` so it can reach Network `B`

Use the `ping` and `traceroute` command from `PCA` to `PCB`

Check that connectivity exists between PCs `hstOfi1`, `hstOfi2` and the routers `R1`, `R2`