Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-users: Re: [Wireshark-users] TCP Retransmitted Packet Assigned with New Seq #

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Sake Blok <sake@xxxxxxxxxx>
Date: Mon, 3 Mar 2008 11:38:38 +0100

On Mon, Mar 03, 2008 at 02:28:53AM -0800, Becky Vict wrote:
> Hi everyone,
> 
> I have noticed a few retransmitted packets in my captures that are assigned with new seq # by the server. 
> 
> For example packets with seq. # 1, 2, 3, 4 are lost and the server retransmits 1, 2, 11 and 12; 11 and 12 being totally new but part of the retransmissions and there will be no recurrence of 3 and 4 anymore from the server.
> 
> Is this a TCP bug or perfectly normal? 

It could be that the frames with seq 2, 3 and 4 are merged into one 
retransmission with seq 2. Have a look at the length of the packets
to find out...

Cheers,
    Sake

  • References:
    • [Wireshark-users] TCP Retransmitted Packet Assigned with New Seq #
      • From: Becky Vict
  • Prev by Date: [Wireshark-users] TCP Retransmitted Packet Assigned with New Seq #
  • Next by Date: [Wireshark-users] "Playback" a capture file
  • Previous by thread: [Wireshark-users] TCP Retransmitted Packet Assigned with New Seq #
  • Next by thread: [Wireshark-users] "Playback" a capture file
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation