Scribd
Upload
39 views8 pages

Pa4 Documentation Forgacs Khuu Varela

Uploaded by

api-596648574
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
39 views8 pages

Pa4 Documentation Forgacs Khuu Varela

Uploaded by

api-596648574
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/ 8

#Class: CST 311 - FA22

#Name: Steven Forgacs, Nina Khuu, Christopher Varela (Team 8)


#Title: Programming_Assignment #4 Subnet Addressing and Routing in Mininet
#Date: 22 October 2022

1. Network Design
2. python run

3. pingall

4. Changes
a. Lines 35-43
i. Moved the instantiation of switches before the instantiation of legacy routers to get rid of build errors.
ii. Updated IP addresses to legacy routers in accordance with our network design
1. Original value ‘0.0.0.0’

b. Lines 47-50
i. Updated IP addresses to hosts in accordance with our network design
1. Original values ‘10.0.0.1’, ‘10.0.0.2’, ‘10.0.0.3’, ‘10.0.0.4’
ii. Updated default route for each host to assign pathway to first router
1. Original value ‘None’

c. Lines 55-69
i. Added interface names and IP addresses to links in accordance with our network design

d. Lines 72-76
i. Added static routes between routers to allow packets to successfully travel between networks.
e. Lines 93-111
i. Added makeTerm calls to start xterm and allow the host to run programs

5. Questions

a. What were any interesting findings and lessons learned?


i. It was an interesting assignment because it encompassed many things that we learned throughout the
class. By creating our own network, we were able to gain more in depth knowledge about previously
taught concepts, while also learning about new concepts. Having hands-on experience in assigning IP
addresses to our network helped to increase our understanding of subnet addressing and interfaces.
Building our own topology on a python script allowed us to learn about various APIs and syntaxes used
to configure the network. We learned how to transform our current client/server socket programs to be
TLS-enabled. We also learned what static routes are, and how to implement them into our network.

b. Why didn’t the original program forward packets between the hosts?
i. Subnets were not established between hosts which prevents h1 to h2 and h3 to h4 communication.
ii. There were no IP addresses assigned to router interfaces preventing hosts from sending packets to these
routers. The inability to send packets to routers means that the packets will not be forwarded and routed
to the other networks.
iii. There were no static routes in the original program. The addition of static routes creates a routing table to
establish a proper pathway for packets to travel between West Coast and East Coast Networks.
c. Is the line ‘ r3.cmd('sysctl -w net.ipv4.ip_forward=1') ’ required?
i. The line is required to enable IP forwarding, which allows the system to act as a router and transfer
packets between networks. If IP forwarding is disabled, h1 and h2 would not be able to communicate
with h3 and h4
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 to break.
i. We changed the default routes for h1 and h2 to the same default routes as h3 and h4. This change in the
routing table will not allow communication to/from network 10.0.1.0/24. h1 and h2 are now set to the ip
address of r5-eth0. This interface is not linked to hosts h1 and h2, which is why the communication is
unsuccessful.

6. Chat and chat server hello wireshark capture


7. curl

8. Decrypted certificates

You might also like