Open the NAT_home_side file and answer the following questions. You might find it
useful to use a Wireshark filter so that only frames containing HTTP messages are
displayed from the trace file.
1. What is the IP address of the client? (Answer: 192.168.1.100)
2. The client actually communicates with several different Google servers in order to
64.233.169.104” (without quotes) into the Filter: field in Wireshark .
3. Consider now the HTTP GET sent from the client to the Google server (whose IP
address is IP address 64.233.169.104) at time 7.102967. What are the source and
destination IP addresses and TCP source and destination ports on the IP datagram
4. At what time is the corresponding 200 OK HTTP message received from the
addresses and TCP source and destination ports on the IP datagram carrying this
5. Recall that before a GET command can be sent to an HTTP server, TCP must first
set up a connection using the three-way SYN/ACK handshake. At what time is
the client-to-server TCP SYN segment sent that sets up the connection used by
destination IP addresses and source and destination ports for the TCP SYN
80) What are the source and destination IP addresses and source and destination
ports of the ACK sent in response to the SYN. (Answer: Source:
will need to clear the Filter expression you entered above in step 2. If you enter
the filter “tcp”, only TCP segments will be displayed by Wireshark).
In the following we’ll focus on the two HTTP messages (GET and 200 OK) and the TCP
SYN and ACK segments identified above. Our goal below will be to locate these two
HTTP messages and two TCP segments in the trace file (NAT_ISP_side) captured on the
link between the router and the ISP. Because these captured frames will have already
been forwarded through the NAT router, some of the IP address and port numbers will
have been changed as a result of NAT translation.