本次python代写要求是用提供的起始代码编程并完成Python UDP通信，包括server端和client端。

Background

In Assignment #2 we implemented both TCP and UDP based versions of the same application. The TCP version handled the reliable data transfer for us while the UDP version did not, luckily it was a simple date/time server so the potential for network errors impacting the UDP version were minimal. We are going to be introducing some errors into the network intentionally so we will need to develop our own reliable data transfer protocol implemented with UDP. We will be using the rdt 3.0 protocol from the course textbook which allows us to use UDP for reliable data transfers.

Summary

We will create two applications (UDP_Client.py and UDP_Server.py) using the UDP protocol to communicate across a network that can corrupt or lose data packets. This means we have to implement the reliable data transfer protocol (rdt 3.0) we saw in our textbook.

The second part of this assignment will be to test your applications using the tc command to create a queing discipline. The specifics are beyond the scope of this assignment but the basic premise is that this command allows us to introduce reordering, delays, and losses in the channel so you can see how your applications perform.

Procedure

Below are the FSMs for both the client(sender) and server(receiver) we need to create (please note – the server/receiver FSM uses rdt 2.2 as there is no need to define a new rdt 3.0 for it):

We will be using the following format for our Pseudo UDP packet:

ACK – Indicates if packet is ACK or not. Valid values (1 or 0)
SEQ – Sequence number of packet. Valid values (1 or 0)
DATA – Application Data (8 bytes)
CHKSUM – MD5 Checksum of packet (32 Bytes)

You will need to create the packet, load it with the necessary values and then send it to the server. The server will receive the packet, check to see if it is corrupted and then take appropriate action. This process will exactly mirror rdt 3.0 as shown in the textbook, so please make sure you follow it carefully!

Pictured below are four cases that your applications should be able to deal with:

To help you understand the values that would be set for communication in normal, corruption, and data loss situations please reference the chart below:

You must create two files, UDP_Client.py and UDP_Server.py. The details of each are shown below.

UDP_Client –

This app must connect to the UDP_Server app via UDP (you must use the local loopback address of 127.0.0.1 but please choose any port number you wish) then send three separate packets containing the following information:

NCC-1701
NCC-1664
NCC-1017

When adding the timer to the Client.py application, the timeout value should be set to 9ms

Remember, in order to accomplish this, the client application must also be able to receive data in the form of acknowledgements from the server because we will be using the rdt 3.0 process for creating a reliable transfer over UDP. 

UDP_Server –

This app will establish a UDP socket and listen for incoming connections from the client. When a connection is made the server will consume the data and follow the rdt 2.2 process as shown in chapter 3 of the course textbook.

Remember, in order to accomplish this, the server application must also be able to send acknowledgements because we will be using the rdt 2.2 process for creating a reliable transfer over UDP. 

Configuring Loopback Adapter to Introduce Delays and Losses –

To introduce packet losses and delays we will use this command:

sudo tc qdisc add dev lo root netem delay 10ms reorder 50% 50% loss 40%

This command will delay packets for 10ms (50% of the time) and lose 40% of packets. This queueing discipline runs on your loopback adapter so you must use the loopback address in both your applications.

To revert the loopback adapter to normal behaviour run the following command:

sudo tc qdisc del root dev lo

After you have configured the loopback adapter for delays and losses you will run your applications. Keep in mind that from the screenshots we should be able to see the lost or delayed packets based on what your applications are displaying on the screen.

The output from the UDP_Server and UDP_Client should display a line of text for each of the following actions:

• Received Packet (with all packet values shown)
• Packet Checksum Compare Result (ie. Corrupt or not corrupt)
• Sent Packet (with all packet values shown)
• Timer Expired

Other Information

I have included sample files for both UDP_Client and UDP_Server to get you started. The sample files show you how to do the following:

• Create a UDP connection
• Create a ‘pseudo UDP packet’
• Calculate the checksum
• Fill the packet and send it to the server
• Receive the packet and unpack it
• Compare checksums to ensure the packet is not corrupted

You will need to do the rest.

What to Submit

You will be submitting the following via OWL :

• Files UDP_Server.py and UDP_Client.py with documentation for any command line arguments/variables to be set. (We need to know how to run your app!)
• Two screen captures showing
  1. UDP_Client.py output messages during the session
  2. UDP_Server.py output messages during the session

Grading

100 points           Total
100 points            Function and design of your client and server apps
You will be graded on the following:

• Design and function of your applications
• Documentation within your applications (Yes, it is important. No one wants to work on undocumented apps)