[lkml]   [2000]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: TCP: peer x.x.x.x:y/z shrinks window a:b:c... wrote:
> Hello!
> > I'll keep looking.
> Is it easy to reproduce? If so, try to make tcpdump, which
> covers one of these messages.

It's extremely rare. We maintain persistent connections open for long
periods of time and even though a user who triggered it is online, it
only triggers the message a maximum of 26 times (typically ~4) and the
traffic volume we handle, it is not extremely practical for me to log
all traffic.

Of the IPs which triggered the response and were online at the time,
every single one of thm has either not had any ports open, been
firewalled or had nmap not be able to guess correctly with a single
exception of a machine which nmap said was "Windows NT4 / Win95 / Win98,
Windows NT 4 SP3, Windows NT 4.0 Server SP5 + 2047 Hotfixes." that had
port 1500/tcp (vlsi-lm) open.

However, during the scan, nmap reported that the report server was
sending RST from port 1500. One thing I did notice is that most of the
machines which I could ping that triggered this message were extremely
lagged (ping times 800+).

I'll keep trying though.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.073 / U:2.760 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site