Re: analysis of TCP window size issues still around - several reports / SACK involved?

[Alessandro Suardi <alessandro.suardi@xxxxxxxxxx>]

bert hubert wrote:
> On Tue, Jul 06, 2004 at 01:19:55PM -0700, David S. Miller wrote:
>
>
> > rather it do this, so that diagnosing dumps are easier.  If tcpdump
> > tries to be too clever, scaling the window, then I might end up
> > chasing down a tcpdump bug rather than a TCP one :-)
>
>
> True - it might want to print '43 (*128=5706)' or something like that.
>
>
> > What would be more interesting is to get the tcpdump trace from the
> > other side of this connection.  This is crucial, as it will show how
> > and in what way exactly the window scale options and/or window fields
> > are being edited by a firewall or other device and thus causing
> > the problems.
>
>
> I have an appointment with Alessandro tomorrow evening at 11PM CEST to do
> just that.

Sorry about being slightly late - I read the thread from my VPN
 link (which does work), now I'm turning it off and will email
 Bert with my actual IP address and my connection.

Thanks,

--alessandro

 "Practice is more important than theory. A _lot_ more important."
    (Linus Torvalds on lkml, 1 June 2004)