Scribd
Upload
38 views

Paa4 - Subnet Addressing and Routing in Mininet Questions

This document outlines the requirements for PA#4 lab assignment, which involves setting up a network topology with routing. It lists 8 requirements including providing the network design, screenshots of a working program without errors, successful ping tests between all hosts, changes made to the code and why, answers to questions, and screenshots of a working chat client, Wireshark traces of encrypted traffic, downloading a file from the web server, and decrypted server certificates.

Uploaded by

api-596367097
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
38 views

Paa4 - Subnet Addressing and Routing in Mininet Questions

This document outlines the requirements for PA#4 lab assignment, which involves setting up a network topology with routing. It lists 8 requirements including providing the network design, screenshots of a working program without errors, successful ping tests between all hosts, changes made to the code and why, answers to questions, and screenshots of a working chat client, Wireshark traces of encrypted traffic, downloading a file from the web server, and decrypted server certificates.

Uploaded by

api-596367097
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Richard Rivera, Crystal Lauren, Zack Hester, Kevin Swei

Oct. 22, 2022


Lab: PA#4

1. Correct Network design that follows the IP addressing rules for this assignment, listed above,
and allows all the hosts to successfully ping each other. Draw and submit the network design in
pdf format with all interfaces labelled with interface names (e.g., s1-eth1) and interface IP
addresses.
2. Screen capture of the program that runs with no Python errors.
3. Screen capture of successful pingall at the mininet> prompt. (5 points are given if h1, h2, h3
and h4 can successfully ping each other, but pingall is not successful.)
4. A list of lines that were changed and why

● Setting the routers IP addresses and subnet masks


● Set the host’s IP address, subnet mask, and default route
● Set link’s IP address and subnet mask for r3-eth1, r4-eth1, and r5-eth1
● Adding static routes

5. Answers to these questions:


A. What were any interesting findings and lessons learned?
The lesson that was learned was the importance of defining roles and regular communications
between members of the team.

B. Why didn’t the original program forward packets between the hosts?
It couldn’t because the initial configuration of the topology, and the hosts didn’t have a subnet
mask or a default routes configuration. Neither hosts know whether the other has the same
subnet and wouldn’t know where to forward packets to each other.

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


Yes, the line is required for r3 to act as a router by enabling the forwarding of the IPv4 packets.

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.
When we broke the working program, h1 couldn’t ping to h2 and r4’s routing table didn’t have
the route of 10.0.2.0/24. It doesn’t know that interface r4-eth1 exist and there was no matches
of the entries. It would drop the packets and return the ICMP message to the source stating the
destination network being unreachable.

6. Screen capture of a successful chat session between the two chat clients (15 points) and a
screen capture of a Wireshark trace of the communication between a chat client and the chat
server (10 points). For the Wireshark trace, you must select the Server Hello packet, and in the
packet details, expand the TLS Record Layer Server Key Exchange after expanding the
Transport Layer Security.

7. Screen capture of the successful wget (or curl) of the web server index file.
8. Screenshot of both decrypted server (web and chat) certificates.

You might also like