| To: | lkml@xxxxxxxxx |
|---|---|
| Subject: | Re: sequence number problem with zero length window size |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Tue, 08 Apr 2003 15:17:05 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx, kuznet@xxxxxxxxxxxxx |
| In-reply-to: | <16019.1179.697600.659029@xxxxxxxxxxxxxxxxx> |
| References: | <16019.1179.697600.659029@xxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: lkml@xxxxxxxxx
Date: Tue, 8 Apr 2003 13:19:23 -0400
This IS the problem I'm reporting:
When the window size goes to zero, the sender (Linux 2.4.19) sends a
packet with the wrong sequence number. In the attached trace, see
packets starting at number 5470, time stamp 695.453571. Here the
client acks for sequence number ....741 but the sender then sends
a packet with sequence number ...740.
Congratulations, you've witnessed a zero-window probe.
This is not a bug. We probe zero windows by sending a dummy
byte "in the past" that we know the other side has received
already, because this packet will be:
1) legal, in the window
2) make the other side generate an ACK and thus give us
an updated indication of the current window size
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | sequence number problem with zero length window size, lkml |
|---|---|
| Next by Date: | [Patch 2.4.20+] missing SNMP stats, Nivedita Singhvi |
| Previous by Thread: | sequence number problem with zero length window size, lkml |
| Next by Thread: | [Patch 2.4.20+] missing SNMP stats, Nivedita Singhvi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |