badbass Posted January 23, 2013 Share Posted January 23, 2013 First post of 2013 you can kick me now. This question does not belong here. Okay this how I think it works Shoot me if I am wrong. Tcp windowing is for flow control. If a buffer fills up it tells the sending to slow down. It also determines how many packets can be sent without an ack. The idea is to provide reliable data transport. Does it set a timer to tell the other side to stop sending for a certain amount of time with the receive buffer is full. Is this close to being correct I should know this. Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted January 23, 2013 Share Posted January 23, 2013 http://www.tcpipguide.com/free/t_TCPWindowSizeAdjustmentandFlowControl.htm Reading that (found with Google) and using some key terms in Google again should find you everything you need to know. Quote Link to comment Share on other sites More sharing options...
digip Posted January 23, 2013 Share Posted January 23, 2013 (edited) From what I recall in my cisco class, you can set the window size, for metric testing, and see where it fails, but in general, TCP, is a "if this packet fails, resend" protocol, unlike UDP, which is connectionless, where, it just says "hello world, I am talking, can you hear everything I am saying" and if any of that is not heard, oh well, you're shit out of luck because UDP, will not repeat itself. Its often why UDP, is used for video streaming and game play online, voip, etc, because, you don't want to be talking to someone, have packets come in out of order, adn then say, oh, you missed packets 3 and 9, resend, and then try to play that in real time, the info being streamed would be like trying to listen to yoda talk. The message would be out of order. TCP, keeps track of all packets, and when one if bad or missing, it resends them and then reassembles the data on your end using sequencing to keep track. The window, just tells the stack how large and how much data it can send at one time, and when the threshold fails, it reduces that window size, and breaks up the data into more fragments. In other words, lets see if we can fit 10 pounds of shit in a 5 pound bag and when it can't we'll get some more bads and then send the rest later, and you can dump it all in when you get it on your side and figure out where it all goes. http://www.cisco.com/en/US/docs/ios/12_2t/12_2t8/feature/guide/tcpwslfn.html#wp1025043 http://ask.wireshark.org/questions/2365/tcp-window-size-and-scaling Edited January 23, 2013 by digip Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.