Petr Janda:
> > Something is badly screwing up TCP, perhaps by throwing away packets
> > with flags that it does not like.
>
> A misconfigured firewall? Seems unlikely as this timeout problem
> really happens a lot. Im also going to have a look at the Cisco ADSL
> router, maybe try replacing it with another one to make sure. Does
> anyone know commands that would allow me to do something like a
> tcpdump on a Cisco router? Especially Id like to see if this is ICMP
> related at all.
>
> I really have to localize this problem as soon as possible.
Good luck. I am not going to speculate, and will limit myself to
what is observable.
One odd thing is that TCP data arrives intact until offset 145,
then the next data to arrive is is a non-fragmented packet with
890 bytes starting at offset 7445, so we are missing 7300 bytes.
These 890 bytes are not the end of the message, so I would expect
to see 1460 bytes (the maximal segment size that is agreed upon in
the TCP initial handhake) instead of 890.
If there is a traffic shaper at your end, it may replace your
TCP stack's MSS=1460 announcement by something smaller, like 890.
If you dump the CISCO configuration maybe you'll see that 890 number.
Wietse
