I've been able to capture a tcpdump from both ends during the problem
and its my belief there is a bug in 2.6.20.1 (at the client side) in
that it issues a SACK option for an old sequence which the current
window being advertised is beyond it. This is the most concerning issue
as the integri
This is a reproducible problem (would take me between 30 mins and a day
to reproduce it). Please feel free to provide me with tcpdump options
to be sure I include to get the information you need.
I've been informed there is no firewall at all, the only firewalling
that takes place is the lo
CLIENT = Linux 2.6.20.1-smp [Customer build]
SERVER = Linux 2.6.9-55.ELsmp [Red Hat Enterprise Linux AS release 4 (Nahant
Update 5)]
The problems start around time index 09:21:39.860302 when the CLIENT issues a
TCP packet with SACK option set (seemingly for a data segment which has already
bee
3 matches
Mail list logo