From: David <david@blue-labs.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Jim Woodward <jim@jim.southcom.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2 TCP window shrinking
Date: Fri, 02 Mar 2001 18:44:12 -0800 [thread overview]
Message-ID: <3AA05A7C.5020109@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0103030426210.12977-100000@jim.southcom.com.au> <15008.6084.410042.53699@pizda.ninka.net>
David S. Miller wrote:
> We need desperately to know exactly what OS the xxx.xxx.1.14 machine
> is running. Because you've commented out the first two octets, I
> cannot check this myself using nmap.
I see them all the time on my sites. I have active mirrors so they
abound. Here are a few, I've also attached nmap's guesses.
TCP: peer 148.75.156.238:1025/7000 shrinks window
3317772066:0:3317772330. Bad, what else can I say?
TCP: peer 195.226.233.21:1774/6660 shrinks window
2502834461:2920:2502837525. Bad, what else can I say?
TCP: peer 195.39.136.145:1702/7000 shrinks window
2750401402:2920:2750405782. Bad, what else can I say?
TCP: peer 213.189.87.228:1190/6660 shrinks window
2933193691:1072:2933194827. Bad, what else can I say?
#1, unknown
#2, running proxy squid/2.3.stable4, can't tell what OS is on it.
#3, unknown
#4, unknown
#2 and #4 both have the following in http headers:
Via: 1.1 netcache (NetCache 4.1R6)
-d
next prev parent reply other threads:[~2001-03-03 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 17:26 Jim Woodward
2001-03-02 21:59 ` David S. Miller
2001-03-03 1:27 ` Phil Brutsche
2001-03-03 2:05 ` Jesse Wyant
2001-03-03 2:44 ` David [this message]
2001-03-03 10:09 ` green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AA05A7C.5020109@blue-labs.org \
--to=david@blue-labs.org \
--cc=davem@redhat.com \
--cc=jim@jim.southcom.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®