From: alex@yuriev.com
To: Willy Tarreau <w@1wt.eu>
Cc: 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 14:33:00 -0400 [thread overview]
Message-ID: <20060815183300.GC15957@s2.yuriev.com> (raw)
In-Reply-To: <20060815181938.GK8776@1wt.eu>
On Tue, Aug 15, 2006 at 08:19:39PM +0200, Willy Tarreau wrote:
> > This is absolutely not correct. Routers forward packets. They do not mangle
> > the data in them.
>
> Believe it or not, there are a lot of routers nowadays that can do NAT.
> And even for very basic NAT, you have to recompute the TCP checksum, which
> means that you mangle data within the packet. Even worse, some of them are
> able to NAT complex protocols such as FTP and for this, they need to mangle
> the application payload. OK, this should not be the router's job, but it's
> often the best placed to do the job, and there is customer demand for this.
Just because you are using a Linksys/Netgear or god else knows what to
mangle your packets and call that device a router does not mean that normal
service providers have NAT enabled on their GSRs and Junipers.
The issue is not in a router running IOS somewhere. The issue is in the
broken code/broken driver/broken something on the end-point.
Alex
next prev parent reply other threads:[~2006-08-15 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 16:05 Mark Reidenbach
2006-08-15 17:01 ` Alan Cox
2006-08-15 17:30 ` Phil Oester
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 [this message]
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=20060815183300.GC15957@s2.yuriev.com \
--to=alex@yuriev.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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®