Answered step by step
Verified Expert Solution
Question
1 Approved Answer
The following image shows a trace log in WireShark. In packet 1-10, you'll notice a TCP 3-way handshake, HTTP GET request, the response to said
The following image shows a trace log in WireShark. In packet 1-10, you'll notice a TCP 3-way handshake, HTTP GET request, the response to said request and the connection being closed. In packet 11 (highlighted), the user was able to send a HTTP request, even though the connection has previously closed and no new TCP connection has been opened. How is this possible? (Hint: This has something to do with the TCP"options that were used during the initial 3-way handshakes in packets 1-3). Describe the process through which TCP may send data without opening a new connection. You will have to do some searching of your own for this. From the point of view of page load times, will the use of TCP with this option continue to reduce the PLT as the bandwidth keeps increasing? Justify your answer. Into 40 X Apply a display filter ... No. Time Source 1 0.000000 172.16.1.25 2 0.000104 172.16.1.1 3 0.888176 172.16.1.25 4 0.989935 172.16.1.25 5 6.681249 172.16.1.1 6 8.681279 172.16.1.1 7 0.001710 172.16.1.25 B 20.691952 172.16.1.25 9 20.692197 172.16.1.1 18 28.692285 172.16.1.25 11 28.399520 172.16.1.25 12 28.399684 172.16.1.1 13 28.399817 172.16.1.25 14 28.399946 172.16.1.1 15 28.498249 172.16.1.25 Destination Protocol 172.16.1.1 TCP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.1 HTTP 172.16.1.25 TCP 172.16.1.25 HTTP 172.16.1.1 TCP 172.16.1.1 TCP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.1 HTTP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.25 HTTP 172.16.1.1 TCP Length 78 56346 - 80 (SYN] Seq=@ Win=292e0 Len= MSS=1460 SACK_PERM=1 TSval=4846018255 TSecr= WS=128 TFOR 86 Be - 56346 (SYN, ACK) Seq=@ Ack=1 Win=28968 Len=@ MSS=1460 SACK_PERM=1 TSval=8982848 TSecr=4046018255 WS=128 TFO=C 66 56346 - 80 [ACK) Seq=1 Ack=1 Win=29312 Len=@ TSval=4646018256 TSecr=8882848 398 GET /favicon.ico HTTP/1.1 66 B8 - 56346 [ACK] Seq=1 Ack=333 Win=38888 Len=6 TSval=8682848 TSecr=4846818256 451 HTTP/1.1 404 Not Found (text/html) 66 56346 - 80 [ACK] Seq=333 Ack=386 Win=30336 Len=8 TSval=4646818256 TSecr=B082849 66 56346 - 88 (FIN, ACK) Seq=333 Ack=386 Win=38336 Len=8 TSval=4846823428 TSecr=B882849 66 Be 56346 (FIN, ACK) Seq=386 Ack=334 Win=38888 Len=8 TSval=8888821 TSecr=4846823428 66 56346 - 88 [ACK] Seq=334 Ack=387 Win=30336 Len=8 TSval=4846623429 TSecr=BBBB821 418 GET /favicon.ico HTTP/1.1 74 88 - 56366 (SYN, ACK) Seq= Ack=333 Win=28968 Len=8 MSS=1468 SACK_PERM=1 Tsval=8889948 TSecr=4846025355 WS=128 66 56366 - 8D [ACK) Seq=333 Ack=1 Win=29312 Len=8 TSval=4846825355 TSecr=8B89948 451 HTTP/1.1 404 Not Found (text/html) 66 56366 - 88 [ACK) Seq=333 Ack=386 Win=30336 Len=8 TSval=4846825356 TSecr=8889948 Frame 11: 418 bytes on wire (3344 bits), 418 bytes captured (3344 bits) on Interface \Device\NPF_{2F482FE9-6DB6-4898-9135-EFACA2A6B43E), id @ Ethernet II, Src: Microsof_8d: 4a:08 (00:15:50:8d:4:00), Dst: Microsof_8d: 4a: 86 (0:15:50:8d: 4a: 06) Internet Protocol Version 4, Src: 172.16.1.25, Dst: 172.16.1.1 Transmission Control Protocol, Src Port: 56366, Dst Port: 80, Seq: @, Len: 332 Source Port : 56366 Destination Port: 80 (Stream index: 11 [TCP Segment Len: 332] Sequence Number: 0 (relative sequence number) Sequence Number (raw): 3187920817 [Next Sequence Number: 333 (relative sequence number)] Acknowledgment Number: 0 Acknowledgment number (raw): @ 1101 .... = Header Length: 52 bytes (13) Flags: 8x682 (SYN) Window: 29200 Calculated window size: 29200) Checksum: Bx5c71 [unverified) [Checksun Status: Unverified] Urgent Pointer: @ Options: (32 bytes), Maximum segment size, SACK permitted, Timestamps, No-Operation (NOP), Window scale, TCP Fast Open, No-Operation (NOP), No-Operation (NOP) (SEO/ACK analysis) (ARTT: 6.808297220 seconds) [Bytes in flight: 332) [Bytes sent since last PSH flag: 332] (Timestamps) TCP payload (332 bytes) Hypertext Transfer Protocol GET /favicon.ico HTTP/1.1 Host: 172.16.1.1 Connection: keep-alive User-Agent: Mozilla/5.0 (x11; Linux x86_64) Applewebkit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Accept: image/webp, image/apng, image/*,*/*;q=0.8 Referer: http://172.16.1.18 Accept-Encoding: gzip,deflate Accept-Language: en-Us, en;q=0.8 [Full request URI: http://172.16.1.1/favicon.ico) (HTTP request 1/1) [Response in frane: 141 The following image shows a trace log in WireShark. In packet 1-10, you'll notice a TCP 3-way handshake, HTTP GET request, the response to said request and the connection being closed. In packet 11 (highlighted), the user was able to send a HTTP request, even though the connection has previously closed and no new TCP connection has been opened. How is this possible? (Hint: This has something to do with the TCP"options that were used during the initial 3-way handshakes in packets 1-3). Describe the process through which TCP may send data without opening a new connection. You will have to do some searching of your own for this. From the point of view of page load times, will the use of TCP with this option continue to reduce the PLT as the bandwidth keeps increasing? Justify your answer. Into 40 X Apply a display filter ... No. Time Source 1 0.000000 172.16.1.25 2 0.000104 172.16.1.1 3 0.888176 172.16.1.25 4 0.989935 172.16.1.25 5 6.681249 172.16.1.1 6 8.681279 172.16.1.1 7 0.001710 172.16.1.25 B 20.691952 172.16.1.25 9 20.692197 172.16.1.1 18 28.692285 172.16.1.25 11 28.399520 172.16.1.25 12 28.399684 172.16.1.1 13 28.399817 172.16.1.25 14 28.399946 172.16.1.1 15 28.498249 172.16.1.25 Destination Protocol 172.16.1.1 TCP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.1 HTTP 172.16.1.25 TCP 172.16.1.25 HTTP 172.16.1.1 TCP 172.16.1.1 TCP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.1 HTTP 172.16.1.25 TCP 172.16.1.1 TCP 172.16.1.25 HTTP 172.16.1.1 TCP Length 78 56346 - 80 (SYN] Seq=@ Win=292e0 Len= MSS=1460 SACK_PERM=1 TSval=4846018255 TSecr= WS=128 TFOR 86 Be - 56346 (SYN, ACK) Seq=@ Ack=1 Win=28968 Len=@ MSS=1460 SACK_PERM=1 TSval=8982848 TSecr=4046018255 WS=128 TFO=C 66 56346 - 80 [ACK) Seq=1 Ack=1 Win=29312 Len=@ TSval=4646018256 TSecr=8882848 398 GET /favicon.ico HTTP/1.1 66 B8 - 56346 [ACK] Seq=1 Ack=333 Win=38888 Len=6 TSval=8682848 TSecr=4846818256 451 HTTP/1.1 404 Not Found (text/html) 66 56346 - 80 [ACK] Seq=333 Ack=386 Win=30336 Len=8 TSval=4646818256 TSecr=B082849 66 56346 - 88 (FIN, ACK) Seq=333 Ack=386 Win=38336 Len=8 TSval=4846823428 TSecr=B882849 66 Be 56346 (FIN, ACK) Seq=386 Ack=334 Win=38888 Len=8 TSval=8888821 TSecr=4846823428 66 56346 - 88 [ACK] Seq=334 Ack=387 Win=30336 Len=8 TSval=4846623429 TSecr=BBBB821 418 GET /favicon.ico HTTP/1.1 74 88 - 56366 (SYN, ACK) Seq= Ack=333 Win=28968 Len=8 MSS=1468 SACK_PERM=1 Tsval=8889948 TSecr=4846025355 WS=128 66 56366 - 8D [ACK) Seq=333 Ack=1 Win=29312 Len=8 TSval=4846825355 TSecr=8B89948 451 HTTP/1.1 404 Not Found (text/html) 66 56366 - 88 [ACK) Seq=333 Ack=386 Win=30336 Len=8 TSval=4846825356 TSecr=8889948 Frame 11: 418 bytes on wire (3344 bits), 418 bytes captured (3344 bits) on Interface \Device\NPF_{2F482FE9-6DB6-4898-9135-EFACA2A6B43E), id @ Ethernet II, Src: Microsof_8d: 4a:08 (00:15:50:8d:4:00), Dst: Microsof_8d: 4a: 86 (0:15:50:8d: 4a: 06) Internet Protocol Version 4, Src: 172.16.1.25, Dst: 172.16.1.1 Transmission Control Protocol, Src Port: 56366, Dst Port: 80, Seq: @, Len: 332 Source Port : 56366 Destination Port: 80 (Stream index: 11 [TCP Segment Len: 332] Sequence Number: 0 (relative sequence number) Sequence Number (raw): 3187920817 [Next Sequence Number: 333 (relative sequence number)] Acknowledgment Number: 0 Acknowledgment number (raw): @ 1101 .... = Header Length: 52 bytes (13) Flags: 8x682 (SYN) Window: 29200 Calculated window size: 29200) Checksum: Bx5c71 [unverified) [Checksun Status: Unverified] Urgent Pointer: @ Options: (32 bytes), Maximum segment size, SACK permitted, Timestamps, No-Operation (NOP), Window scale, TCP Fast Open, No-Operation (NOP), No-Operation (NOP) (SEO/ACK analysis) (ARTT: 6.808297220 seconds) [Bytes in flight: 332) [Bytes sent since last PSH flag: 332] (Timestamps) TCP payload (332 bytes) Hypertext Transfer Protocol GET /favicon.ico HTTP/1.1 Host: 172.16.1.1 Connection: keep-alive User-Agent: Mozilla/5.0 (x11; Linux x86_64) Applewebkit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Accept: image/webp, image/apng, image/*,*/*;q=0.8 Referer: http://172.16.1.18 Accept-Encoding: gzip,deflate Accept-Language: en-Us, en;q=0.8 [Full request URI: http://172.16.1.1/favicon.ico) (HTTP request 1/1) [Response in frane: 141
Step by Step Solution
There are 3 Steps involved in it
Step: 1
Get Instant Access to Expert-Tailored Solutions
See step-by-step solutions with expert insights and AI powered tools for academic success
Step: 2
Step: 3
Ace Your Homework with AI
Get the answers you need in no time with our AI-driven, step-by-step assistance
Get Started