| 2020-09-20 15:17:20 +0000 | received badge | ● Famous Question (source) |
| 2019-08-07 17:27:54 +0000 | received badge | ● Notable Question (source) |
| 2019-08-07 17:27:54 +0000 | received badge | ● Popular Question (source) |
| 2018-08-22 19:14:46 +0000 | marked best answer | TCP sequence numbers - beginners question Apologies for the beginners question. TCP basics (known to me :) ) - TCP sequence number is increasing for each byte of data send. I have learned that SYN packet (len=0, no data are being send) also increases the sequence number. Is there a reason for that? I googled around for a good explanation or RFC document, but I can't find anything. FIN appears to be the same way (also causes sequence number to go up by 1 although no data are being carried by the packet). The best information I could find is here: http://packetlife.net/blog/2010/jun/7... == quote == Notice that the acknowledgement number has been increased by 1 although no payload data has yet been sent by the client. This is because the presence of the SYN or FIN flag in a received packet triggers an increase of 1 in the sequence. (This does not interfere with the accounting of payload data, because packets with the SYN or FIN flag set do not carry a payload.) == end of quote == Thank you, Aleksandr |
| 2018-08-22 19:14:46 +0000 | received badge | ● Scholar (source) |
| 2018-08-22 19:13:25 +0000 | commented answer | TCP sequence numbers - beginners question Jim, Many thanks! This is a great explanation, makes sense. Aleksandr |
| 2018-08-20 23:03:53 +0000 | asked a question | TCP sequence numbers - beginners question TCP sequence numbers - beginners question Apologies for the beginners question. TCP basics (known to me :) ) - TCP sequ |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.