Scribd
Upload
55 views

Pa4 Documentation

The document provides documentation for a PA4 assignment, including: 1) A network design diagram with labels 2) Screenshots of a Python script running without errors and a successful 'pingall' command 3) A list of 10 line changes made to the Python script to address issues with IP addresses and routing between subnets

Uploaded by

api-594946400
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
55 views

Pa4 Documentation

The document provides documentation for a PA4 assignment, including: 1) A network design diagram with labels 2) Screenshots of a Python script running without errors and a successful 'pingall' command 3) A list of 10 line changes made to the Python script to address issues with IP addresses and routing between subnets

Uploaded by

api-594946400
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Class: CST 311

Title: PA4 Documentation


Author: Angela Cheng, Denis Mulalic, Janet Pham, Ben Textor
Date: October 21, 2022

Team 5 PA4 Documentation

1. Network Design Topography with Labels

2. Screenshot of legacy_network.py successfully running without errors


3. Screenshot of legacy_network.py successful ‘pingall’ command

4. List of line changes for legacy_network.py:

1. The two switch instantiations on lines 30 and 31 originally were placed after the
instantiation of r5, however this caused a build error, so it was moved.

2. The ip address of r5 on line 33 was changed from 0.0.0.0. so that it would be part of the
proper subnet, 10.0.2.0.

3. The ip address of r4 on line 36 was changed from 0.0.0.0. so that it would be part of the
proper subnet, 192.168.1.0.

4. The ip address of r3 on line 39 was changed from 0.0.0.0. so that it would be part of the
proper subnet, 10.0.1.0.

5. The ip address of host h3 on line 44 was changed from 10.0.0.1 so that it would be in
the appropriate subnet, 10.0.2.0.

6. The ip address of host h1 on line 45 was changed from 10.0.0.2 so that it would be in
the appropriate subnet, 10.0.1.0.
7. The ip address of host h2 on line 46 was changed from 10.0.0.3 so that it would be in
the appropriate subnet, 10.0.1.0.

8. The ip address of host h4 on line 47 was changed from 10.0.0.4 so that it would be in
the appropriate subnet, 10.0.2.0.

9. On lines 57 and 58, links between r3 & r4, and r4 & r5, were altered to explicitly set
interface ips for the connection.

10. on lines 63, 64, 66, 67, 69, and 70, static routes were created and set for each end of
each router, allowing for inter-subnet communication.

5. Answers to Questions:

a. What were any interesting findings and lessons learned?


Answer: Over the course of this assignment, we learned an incredible amount about IP
Assignments, the difference between Broadcast. Network, and Host IPs. We’re very grateful for
the assistance of Sam Ogden, Ian Lowe, Harold Millan, and Tiffany Andersen for providing
assistance and advice on our script problems.

b. Why didn’t the original program forward packets between the hosts?
Answer: The original program would not successfully build because the router r5 was being
instantiated before the switches s1 and s2 were created. With that problem fixed, however, the
program would still not successfully be able to forward packets between hosts on different
subnets. This is because the original program had did not have the appropriate links and routes
to establish a two-way connection between subnets.

c. Is the line ‘r3.cmd(‘sysctl -w net.ipv4.ip_forward=1’)’ required?


Answer: Yes, without this line, the hosts on different subnets cannot successfully ping
each other.

d. Intentionally break your working program, e.g.: change a subnet length, IP


address, or default route for a host. Explain why your change caused the
network break.
Answer: In the spirit of an issue we ran into, we set the static routes incorrectly in order
to break our working program. In a command creating a static route, first the target IP is listed,
then the interface IP of what’s on the other side of an explicitly named connection. We had
initially been setting the second IP address to the interface IP of the port itself, which causes
myriad connection problems, as a subnet connection was being created around the routers,
instead of between them.

You might also like