fre 2009-10-09 klockan 02:47 -0700 skrev dtinazzi:
> So Henrik,
>
> can we say the problem is inside the proxy (nic, os, squid)? what can we
> exclude?
The problem is outside the TCP/IP stack of the server where Squid runs.
The problem is not inside Squid.
Next steps is to
1. Run a packet capture on the client to see if the same TCP sequence
number issue is seen there.
2. If not then run a packet capture on the network wire to the server,
either by inserting a bridge between the server & switch or configuring
a mirror port on the switch.
3. If problem is seen on the server network wire, then do the same on
the client side.
4. Continue narrowing down until you know where the TCP sequence number
corruption problem is introduced.
My bets are
a) a malfunctioning firewall or NAT between client & squid
b) malfunctioning TCP offload in the client station
Regards
Henrik
Received on Fri Oct 09 2009 - 13:36:03 MDT
This archive was generated by hypermail 2.2.0 : Fri Oct 09 2009 - 12:00:02 MDT