Skip to main content
Related image







Packet Tracer Simulation – TCP and UDP Communications

Part 1: Generate Network Traffic in Simulation Mode
Step 1: Generate traffic to populate Address Resolution Protocol (ARP) tables. 
  • Click MultiServer and click the Desktop tab > Command Prompt. 
  • Enter the ping 192.168.1.255 command. This will take a few seconds as every device on the network responds to MultiServer. 
  • Close the MultiServer window.
Step 2: Generate web (HTTP) traffic. 
  • Switch to Simulation mode. 
  • Click HTTP Client and click the Desktop tab > Web Browser. 
  • In the URL field, enter 192.168.1.254 and click Go. Envelopes (PDUs) will appear in the simulation window. 
  • Minimize, but do not close, the HTTP Client configuration window.
Step 3: Generate FTP traffic. 
  • Click FTP Client and click the Desktop tab > Command Prompt. 
  • Enter the ftp 192.168.1.254 command. PDUs will appear in the simulation window. 
  • Minimize, but do not close, the FTP Client configuration window.
Step 4: Generate DNS traffic.
  • Click DNS Client and click the Desktop tab > Command Prompt. 
  • Enter the nslookup multiserver.pt.ptu command. A PDU will appear in the simulation window. 
  • Minimize, but do not close, the DNS Client configuration window.
Step 5: Generate Email traffic. 
  • Click E-Mail Client and click the Desktop tab > E Mail tool. 
  • Click Compose and enter the following information: 
    • 1)  To: user@multiserver.pt.ptu 
    • 2)  Subject: Personalize the subject line 
    • 3)  E-Mail Body: Personalize the Email 
  • Click Send. 
  • Minimize, but do not close, the E-Mail Client configuration window.
Step 6: Verify that the traffic is generated and ready for simulation. 
Every client computer should have PDUs listed in the Simulation Panel.
Part 2: Examine Functionality of the TCP and UDP Protocols 
Step 1: Examine multiplexing as all of the traffic crosses the network. 
You will now use the Capture/Forward button and the Back button in the Simulation Panel.
  • Click Capture/Forward once. All of the PDUs are transferred to the switch. 
  • Click Capture/Forward again. Some of the PDUs disappear. What do you think happened to them? 
  • Click Capture/Forward six times. All clients should have received a reply. Note that only one PDU can cross a wire in each direction at any given time. What is this called? 
  • A variety of PDUs appears in the event list in the upper right pane of the simulation window. Why are they so many different colors? 
  • Click Back eight times. This should reset the simulation.
Step 2: Examine HTTP traffic as the clients communicate with the server. 
  • Filter the traffic that is currently displayed to display only HTTP and TCP PDUs filter the traffic that is currently displayed: 
  • 1)  Click Edit Filters and toggle the Show All/None check box. 
  • 2)  Select HTTP and TCP. Click anywhere outside of the Edit Filters box to hide it. The Visible Events should now display only HTTP and TCP PDUs. 
  • Click Capture/Forward. Hold your mouse above each PDU until you find one that originates from HTTP Client. Click the PDU envelope to open it. 
  • Click the Inbound PDU Details tab and scroll down to the last section. What is the section labeled? Are these communications considered to be reliable? 
  • Record the SRC PORT, DEST PORT, SEQUENCE NUM, and ACK NUM values. What is written in the field to the left of the WINDOW field? 
  • Close the PDU and click Capture/Forward until a PDU returns to the HTTP Client with a checkmark. 
  • Click the PDU envelope and select Inbound PDU Details. How are the port and sequence numbers 

different than before?
  • There is a second PDU of a different color, which HTTP Client has prepared to send to MultiServer. This is the beginning of the HTTP communication. Click this second PDU envelope and select Outbound PDU Details. 
  • What information is now listed in the TCP section? How are the port and sequence numbers different from the previous two PDUs? 
  • Click Back until the simulation is reset. 
Step 3: Examine FTP traffic as the clients communicate with the server. 
  • In the Simulation Panel, change Edit Filters to display only FTP and TCP. 
  • Click Capture/Forward. Hold your cursor above each PDU until you find one that originates from FTP Client. Click that PDU envelope to open it. 
  • Click the Inbound PDU Details tab and scroll down to the last section. What is the section labeled? 
Are these communications considered to be reliable?
  • Record the SRC PORT, DEST PORT, SEQUENCE NUM, and ACK NUM values. What is written in the field to the left of the WINDOW field? 
  • Close the PDU and click Capture/Forward until a PDU returns to the FTP Client with a checkmark. 
  • Click the PDU envelope and select Inbound PDU Details. How are the port and sequence numbers different than before? 
  • Click the Outbound PDU Details tab. How are the port and sequence numbers different from the previous two results? 
  • Close the PDU and click Capture/Forward until a second PDU returns to the FTP Client. The PDU is a different color. 
  • Open the PDU and select Inbound PDU Details. Scroll down past the TCP section. What is the message from the server? 
  • Click Back until the simulation is reset.
Step 4: Examine DNS traffic as the clients communicate with the server. 
  • In the Simulation Panel, change Edit Filters to display only DNS and UDP. 
  • Click the PDU envelope to open it. 
  • Click the Inbound PDU Details tab and scroll down to the last section. What is the section labeled? 

Are these communications considered to be reliable?
  • Record the SRC PORT and DEST PORT values. Why is there no sequence and acknowledgement number? 
  • Close the PDU and click Capture/Forward until a PDU returns to the DNS Client with a checkmark. 
  • Click the PDU envelope and select Inbound PDU Details. How are the port and sequence numbers 

different than before?
  • What is the last section of the PDU called? 
  • Click Back until the simulation is reset.
Step 5: Examine email traffic as the clients communicate with the server. 
  • In the Simulation Panel, change Edit Filters to display only POP3, SMTP and TCP. 
  • Click Capture/Forward. Hold your cursor above each PDU until you find one that originates from E-mail
    Client. Click that PDU envelope to open it. 
  • Click the Inbound PDU Details tab and scroll down to the last section. What transport layer protocol does
    email traffic use?

Are these communications considered to be reliable?
  • Record the SRC PORT, DEST PORT, SEQUENCE NUM, and ACK NUM values. What is written in the field to the left of the WINDOW field? 
  • Close the PDU and click Capture/Forward until a PDU returns to the E-Mail Client with a checkmark. 
  • Click the PDU envelope and select Inbound PDU Details. How are the port and sequence numbers
different than before?
  • Click the Outbound PDU Details tab. How are the port and sequence numbers different from the previous two results? 
  • There is a second PDU of a different color that HTTP Client has prepared to send to MultiServer. This is the beginning of the email communication. Click this second PDU envelope and select Outbound PDU Details. 
  • How are the port and sequence numbers different from the previous two PDUs? 
  • What email protocol is associated with TCP port 25? What protocol is associated with TCP port 110? 
  • Click Back until the simulation is reset.
Step 6: Examine the use of port numbers from the server. 
  • To see TCP active sessions, perform the following steps in quick succession: 
  • 1)  Switch back to Realtime mode. 
  • 2)  Click MultiServer and click the Desktop tab > Command Prompt.
Labels:

Comments

Post a Comment

Popular posts from this blog

Configuration of Routing Information Protocol

Configuration of Routing Information Protocol Routing Information Protocol  ( RIP ) is a dynamic  routing protocol  which uses hop count as a  routing  metric to find the best path between the source and the destination network. It is a distance vector  routing protocol  which has AD value 120 and works on the application layer of OSI model.  RIP  uses port number 520. Features of RIP 1. Updates of the network are exchanged periodically. 2. Updates (routing information) are always broadcast. 3. Full routing tables are sent in updates. 4. Routers always trust on routing information received from neighbor routers. This is also known as  Routing on rumours . RIP versions :  There are three vesions of routing information protocol –  RIP Version1 ,  RIP Version2  and  RIPng . RIP v1  is known as  Classful  Routing Protocol because it doesn’t send information of subnet mask in...
Post a Comment
Read more
Configuration of Static/Dynamic NAT in Cisco Router Static NAT (Network Address Translation) is one-to-one mapping of a private IP address to a public IP address. Static NAT (Network Address Translation) is useful when a network device inside a private network needs to be accessible from internet. In order to configure NAT we have to understand four basic terms; inside local, inside global, outside local and outside global. These terms define which address will be mapped with which address. Term : Description Inside Local IP Address : Before translation source IP address located inside the local network. Inside Global IP Address : After translation source IP address located outside the local network. Outside Global IP Address: Before translation destination IP address located outside the remote network. Outside Local IP Address : After translation destination IP address locat...
Post a Comment
Read more