Re: How to find a sick router with 2.6.17+ and tcp_window_scaling enabled

[Ralf Hildebrandt]

* Mark Reidenbach <m.reidenbach@xxxxxxxxxxxxxxxxx>:
> 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@xxxxxxxxxx
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@xxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/