Re: Duplicate TCP sequence numbers
From: Paul Hilton (paul_hilton_at_compuserve.com)
Date: 04/12/04
- Next message: max: "Can Connect, But Can't Surf"
- Previous message: David Efflandt: "Re: How to bind an IP to a variable (firewall)"
- In reply to: Tauno Voipio: "Re: Duplicate TCP sequence numbers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 12 Apr 2004 18:44:28 GMT
On Thu, 08 Apr 2004 17:38:38 +0000, Tauno Voipio wrote:
>
> The tcpdump output is somewhat difficult to decode sometimes.
>
> I suspect that you are following the wrong sequence. There are
> two sequence numbers in each segment: the number expected to be
> received next and the number of the first data in the current
> segment. If there is no data in the segment, the sent number
> stays put. An ACK segment is simply a segment with no data.
>
> The ACK flag name is somewhat misleading: actually it says:
> I have synchronized with your send sequence numbers with my
> ACK numbers.
>
> Please get the Ethereal network dumper (tethereal for no X)
> and trace the connection again.
>
> HTH
>
> Tauno Voipio
> tauno voipio @ iki fi
Tauno,
Thanks very much for your help.
OK, I've got ethereal, learned how to make it work, captured the same
sequence. You are quite right, the output is much easier to follow.
However the same thing shows up, I could email the actual dump if it
helps, packets 3 and 4, both from my computer, have the same sequence number.
(and the same problem later).
Here is the summary: (appologies for the line lengths)
No. Time Source Destination Protocol Info
1 0.000000 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [SYN] Seq=180881316 Ack=0 Win=5840 Len=0
2 0.018201 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [SYN, ACK] Seq=148578 Ack=180881317 Win=512 Len=0
3 0.018280 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [ACK] Seq=180881317 Ack=148579 Win=5840 Len=0
4 0.018873 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [PSH, ACK] Seq=180881317 Ack=148579 Win=5840 Len=8
5 0.041082 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [ACK] Seq=148579 Ack=180881325 Win=512 Len=0
6 0.365783 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [PSH, ACK] Seq=148579 Ack=180881325 Win=512 Len=11
7 0.365861 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [ACK] Seq=180881325 Ack=148590 Win=5840 Len=0
8 0.379847 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [FIN, ACK] Seq=148590 Ack=180881325 Win=512 Len=0
9 0.379980 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [FIN, ACK] Seq=180881325 Ack=148591 Win=5840 Len=0
10 0.392271 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [FIN, ACK] Seq=148590 Ack=180881325 Win=512 Len=0
11 0.392386 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [ACK] Seq=180881326 Ack=148591 Win=5840 Len=0
12 0.398712 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [ACK] Seq=148591 Ack=180881326 Win=512 Len=0
13 0.411110 192.168.1.10 Candide.acculin TCP cadlock2 > 41666 [ACK] Seq=148591 Ack=180881326 Win=512 Len=0
14 0.411134 Candide.acculin 192.168.1.10 TCP 41666 > cadlock2 [RST] Seq=180881326 Ack=0 Win=0 Len=0
Paul
- Next message: max: "Can Connect, But Can't Surf"
- Previous message: David Efflandt: "Re: How to bind an IP to a variable (firewall)"
- In reply to: Tauno Voipio: "Re: Duplicate TCP sequence numbers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|