From: Phil Oester <kernel@linuxace.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Reidenbach <m.reidenbach@everytruckjob.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to find a sick router with 2.6.17+ and tcp_window_scaling enabled
Date: Tue, 15 Aug 2006 10:30:46 -0700 [thread overview]
Message-ID: <20060815173046.GA2034@linuxace.com> (raw)
In-Reply-To: <1155661308.24077.297.camel@localhost.localdomain>
On Tue, Aug 15, 2006 at 06:01:47PM +0100, Alan Cox wrote:
> Ar Maw, 2006-08-15 am 11:05 -0500, ysgrifennodd Mark Reidenbach:
> > Does anyone have a way to find the broken router if you are not running
> > the networks involved?
>
> You are almost certainly looking for a broken/crap NAT box, firewall or
> similar product. Routers that are just being routers don't touch the TCP
> layer so even if they are broken/crap/ancient they won't do any harm to
> it.
>
> The usual offenders are cheap NAT boxes and badly designed load
> balancers. They may not even show up in a trace but you should expect
> them to be at one end or the other, unless your ISP is providing you
> with NATted addresses or some kind of managed security service.
Certain versions of BSD ipfilter are also broken. Try some of Apple's
websites for examples.
Is the destination box BSD or behind a BSD firewall?
Phil
next prev parent reply other threads:[~2006-08-15 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 16:05 How to find a sick router with 2.6.17+ and tcp_window_scaling enabled Mark Reidenbach
2006-08-15 17:01 ` Alan Cox
2006-08-15 17:30 ` Phil Oester [this message]
2006-08-15 17:47 ` Mark Reidenbach
2006-08-15 18:07 ` linux-os (Dick Johnson)
2006-08-15 18:06 ` alex
2006-08-15 18:19 ` Willy Tarreau
2006-08-15 18:33 ` alex
2006-08-15 18:45 ` Willy Tarreau
2006-08-15 19:53 ` Mark Reidenbach
2006-08-15 20:20 ` Willy Tarreau
2006-09-13 14:00 ` Mark Reidenbach
2006-08-19 16:42 ` Ralf Hildebrandt
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=20060815173046.GA2034@linuxace.com \
--to=kernel@linuxace.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m.reidenbach@everytruckjob.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.