On 4/05/2012 12:22 p.m., Daniel Echizen wrote:
Thanks for reply.. but no luck.. this is very frustrating .. im
starting to thinking is something with mikrotik
anyone knows how i look where syn/ack is getting dropped? i can i see
is that syn/ack arrives from server but cannot reach client in the
mikotik router..
You mean its leaving Squid but the Mikrotik is somehow absorbing it?
Once you have isolated it to the Mikrotik contacting their help service
is best.
I was going to suggest tcpdump on the Squid box to verify if the ACK is
leaving Squid, but it sounds like you have already done that.
Why there is an extra ACK after SYN-ACK without DATA in there is a
mystery ... the TCP flow should be:
client :: squid
SYN -->
<-- SYN ACK
DATA (REQUEST) -->
<-- ACK
DATA (REQUEST) -->
<-- ACK
...
<-- DATA (REPLY)
ACK (REPLY DATA) -->
<-- DATA (REPLY)
ACK (REPLY DATA) -->
...
Amos
