Linux, FreeBSD, Juniper, Cisco / Network security articles and troubleshooting guides

It is currently Sat Aug 08, 2020 12:06 pm

Post a reply :: TCP ack after two packets
Message body:
Enter your message here, it may contain no more than 60000 characters. 

:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
Font size:
Font colour
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation code
Confirmation code:
In an effort to prevent automatic submissions, we require that you enter both of the words displayed into the text field underneath.

Topic review - TCP ack after two packets
Author Message
Post subject: Re: TCP ack after two packets  |  Post Posted: Tue Dec 13, 2016 10:04 am
Good info and straight to the point. Thank you
Post subject: Re: TCP ack after two packets  |  Post Posted: Tue Jun 14, 2016 9:54 am
No. The TCP window is meant to let the other party know approximately what size is my receive buffer. This means I'm still going to ACK as soon as possible, but I can process only the amount of data in the RX buffer as I notified in the TCP window.

Delaying ACK (depends how much) significantly impacts TCP performance because the sender expects that other party acknowledges the data asap. Otherwise, the sender will start thinking something went wrong and will trigger retransmission due to timeout - every byte sent over TCP has a timeout interval inside which it needs to be acknowledged, calculated based on the RTT - this is another TCP mechanism to ensure reliability.
Keep going through TCP / IP Illustrated books and wireshark books. TCP is very complex protocol.
Post subject: TCP ack after two packets  |  Post Posted: Mon Jun 13, 2016 5:14 pm
im using wireshark for tcp project.
when ACK is sent i get window size of 65536 but every two pockets in the list are followed by ACK send
isnt ACK sent after receiving 65536 bytes?
some times the window sie jump and the goes back to 63k
what cause it to happend?

bloody hell tcp
Jump to:  
cronNews News Site map Site map SitemapIndex SitemapIndex RSS Feed RSS Feed Channel list Channel list

Delete all board cookies | The team | All times are UTC - 5 hours [ DST ]