Scribd
Upload
2 views

Lab-Test-2023

The document outlines a lab assessment for the Computer Networks course at BITS Pilani, requiring students to implement client-server programs in C using TCP/IP socket APIs. Clients c1 and c2 must upload files to server s1 using a stop-and-wait ARQ protocol, with specific packet structures and error simulation. Submissions must be made by April 26, 2023, and will be evaluated for integrity and functionality, with penalties for plagiarism.

Uploaded by

ADITYA AGARWAL
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
2 views

Lab-Test-2023

The document outlines a lab assessment for the Computer Networks course at BITS Pilani, requiring students to implement client-server programs in C using TCP/IP socket APIs. Clients c1 and c2 must upload files to server s1 using a stop-and-wait ARQ protocol, with specific packet structures and error simulation. Submissions must be made by April 26, 2023, and will be evaluated for integrity and functionality, with penalties for plagiarism.

Uploaded by

ADITYA AGARWAL
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Department of Computer Science and Information Systems, BITS Pilani

Second Semester 2022-2023


Computer Networks (CS F303)
LAB ASSESSMENT (ONLINE MODE-OPEN BOOK)
Assessment Available: 10:00 AM
Submission Deadline: 10:00 PM Date: 26-04-2023 Marks: 20
Read the document carefully before starting your work.
Instructions:
a) Take this assessment component as a learning opportunity and attempt it with full integrity.
The submitted files will be checked by a Plagiarism tool. Plagiarized submissions will attract a
HUGE penalty.
b) You must implement the following problem in C language using UNIX/LINUX TCP/IP socket APIs.
Your code must compile on the gcc compiler.
Problem Statement: Write client-server programs to upload one file from each client, c1 and c2, to a
server, s1. Client c1 sends a file name.txt, and client c2 sends a file id.txt simultaneously to the server
using stop-and-wait ARQ protocol over unreliable channels, which can drop the packets (Data and
Acknowledgments) but does not corrupt the packets. The clients c1 and c2 make two separate TCP
connections to the server. The server should receive the packets alternatively from the clients' c1 and c2
and write them into a file list.txt. (Protocol is the same as Q.2 of the mid-semester exam.)

Implementation details:
1. Packetization: The name.txt comprises student names separated by a comma. Client c1 sends one
student name at a time in a packet using stop-and-wait protocol by encapsulating it in the form of a packet
structure. Similarly, id.txt comprises student ids corresponding to the student's names in the name.txt,
separated by a comma. Client c2 sends one id at a time in a packet using stop-and-wait protocol by
encapsulating it as a packet structure. A full-stop (.) character terminates the files name.txt and id.txt.
Remember, c1 and c2 are independent and send packets to s1 without any coordination between them.

Note: Create name.txt and id.txt files and add a few names and ids in the specified format to test your
programs. However, we will use our files for evaluation purposes with a similar format.

2. Packet Structure (Same for c1 and c2): Besides the payload, the packet structure should contain the
following information in the form of header fields.
a) The Size (number of bytes) of the payload
b) The seq_no (byte sequence number) specifies the offset of the first byte of a packet to the file.
The character comma (,) is used as a delimiter between student names and ids, hence do not
count it for offset calculation.
c) Use one Byte field TYPE to differentiate between DATA or ACK packets. (Note: The seq_no field
in the ACK packet would correspond to the DATA packet with the same seq_no value received
from the client.

Note: You can use any other header field(s) required to implement the desired functionality. Provide a
brief justification for that within the code file as a comment.

3. To simulate the erroneous channel (described above), the server randomly drops a received packet
with probability PDR and does not send ACK back to the client. Keep the value of PDR at 10%. While
evaluating, we may test your program's working for different PDR values.

4. Keep the retransmission timeout duration at the client as two seconds. Keep a copy of the transmitted
packet to facilitate retransmission instead of reconstructing a new packet from the input file again.
Page | 1
5. Server s1 is not allowed to buffer any out-of-order packet. For example, s1 is waiting for a packet from
c1, and before it receives a packet from c2, s1 should discard the packet received from c2. Similarly, s1
should discard an out-of-order packet received from the same client.

6. The server first writes the student name received from client c1 and then the corresponding student id
received from client c2 to the file list.txt. The list.txt format is as follows:

Archit Nigam,2021a7ps0089,Dharma Teja, 2020phxf0042

7. The client and server programs should produce the output in the following format: (The output format
is the same for c1 to s1 and c2 to s1 communication.)

Note: If you have used any additional packet header field, you can add that to the client and server
output for better clarity.

Client Output Server Output


SENT PKT: Seq. No. = 0, Size = 40 Bytes RCVD PKT: Seq. No. = 0, Size = 40 Bytes
RCVD ACK: Seq. No. = 0 SENT ACK: Seq. No. = 0
SENT PKT: Seq. No.= 40, Size = 30 Bytes DROP PKT: Seq. No. = 40
RE-TRANSMIT PKT: Seq. No. = 40, Size = 30 Bytes RCVD PKT: Seq. No. = 40, Size = 30 Bytes

Key functionalities to be implemented by you are as follows:


 Input file reading, creating packets, and sending them over TCP sockets by c1 and c2.
 Receiving packets by s1 alternatively from c1 and c2.
 Writing the data received from c1 and c2 to the file list.txt by s1.
 Output format at c1, c2, and s1, as discussed above.
 Packet drop simulation and retransmission of dropped packets.

Submission Instructions:
Create a single zip file of three code files, c1.c, c2.c, and s1.c, and two input files, name.txt, and id.txt, and
upload to the link provided on NALANDA. The zip file name must be your BITS-ID (e.g., 2021a7ps0007).
You must upload your solution before the deadline, i.e., 26-04-2023, by 10:00 PM.
Please note that I will not receive your submission by any other means; hence, uploading your solution
before the deadline is your responsibility.

Evaluation Scheme:
Your code should compile without any error for considering it for evaluation.

xx—0x0—xx

Page | 2

You might also like