Information

Author(s) Olivier Bonaventure
Deadline No deadline
Submission limit No limitation
Category tags tcp

Tags

Sign in

Inferring acknowledgment numbers

TCP, as explained in the TCP chapter of Computer Networking: Principles, Protocols and Practice includes a sequence number in each segment that carries data and uses acknowledgements.


Inferring acknowledgement numbers

During this connection, the client sent some data in successive segments and then the server replied with a an acknowledgement that confirms the reception of all the previous segments. Can you infer the acknowledgement number of the segment returned by the server ?


0000  d1ce04d2c9613aed  93aaa51450187080  
0010  0000000073647173  6473710a          

0000  ÑÎ.ÒÉa:í.ª¥.P.p.
0010  ....sdqsdsq.    
  • Transmission Control Protocol, Src Port: 53710, Dst Port: 1234, Seq: 3378592493, Ack: 2477434132, Len: 8
    • Source Port: 53710
      • Destination Port: 1234
        • Sequence number: 3378592493
          • Acknowledgment number: 2477434132
            • 0101 .... = Header Length: 20 bytes (5)
              • Flags: 0x018 (PSH, ACK)
                • 000. .... .... = Reserved: Not set
                  • ...0 .... .... = Nonce: Not set
                    • .... 0... .... = Congestion Window Reduced (CWR): Not set
                      • .... .0.. .... = ECN-Echo: Not set
                        • .... ..0. .... = Urgent: Not set
                          • .... ...1 .... = Acknowledgment: Set
                            • .... .... 1... = Push: Set
                              • .... .... .0.. = Reset: Not set
                                • .... .... ..0. = Syn: Not set
                                  • .... .... ...0 = Fin: Not set
                                  • Window size value: 28800
                                    • Urgent pointer: 0
                                      • TCP payload (8 bytes)