mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: How to find a sick router with 2.6.17+ and tcp_window_scaling enabled
Date: Sat, 19 Aug 2006 18:42:18 +0200	[thread overview]
Message-ID: <20060819164218.GG9537@charite.de> (raw)
In-Reply-To: <44E1F0CD.7000003@everytruckjob.com>

* Mark Reidenbach <m.reidenbach@everytruckjob.com>:
> I had made an earlier post concerning very poor network performance 
> after upgrading to 2.6.17 and later kernels.  The solution provided by 
> the e1000 developers was that it was in fact a change to the default tcp 
> window scaling settings and that there was a router somewhere between my 
> computer and its destination.

Are you looking for a traceroute-/mtr-like tool that sends specially
crafted packets and finally comes up with a message like "the router
between x and y is broken"?

-- 
Ralf Hildebrandt (i.A. des IT-Zentrums)         Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF                 send no mail to spamtrap@charite.de

      parent reply	other threads:[~2006-08-19 16: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
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 [this message]

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=20060819164218.GG9537@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --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

Powered by JetHome