Hello again,
I was just corrected by one of my colleagues as to the hardware and os
of the squid server.
Hardware: IBM x360
OS: RedHat Enterprise Linux 4 update 3
Also, here is the combined tcpdump output from gre1 and eth2:
### This is the 3-way handshake.
gre1 12:17:04.712823 IP 10.160.100.38.3582 > 12.160.37.9.http: S
3102010967:3102010967(0) win 16384 <mss 1260,nop,nop,sackOK>
eth2 12:17:04.712820 IP 12.160.37.9.http > 10.160.100.38.3582: S
2210366198:2210366198(0) ack 3102010968 win 5840 <mss 1460,nop,nop,sackOK>
gre1 12:17:04.714861 IP 10.160.100.38.3582 > 12.160.37.9.http: . ack
2210366199 win 17640
### Client pushes packet -- the "GET http://squid-cache.org/";
gre1 12:17:04.716128 IP 10.160.100.38.3582 > 12.160.37.9.http: P
0:378(378) ack 1 win 17640
eth2 12:17:04.716153 IP 12.160.37.9.http > 10.160.100.38.3582: . ack 379
win 6432
## I expect squid died on something it didn't like at this point
## and initiated the session tear-down (fin-ack-fin-ack)
### Proxy initiates end of session (FIN)
eth2 12:17:04.739317 IP 12.160.37.9.http > 10.160.100.38.3582: F 1:1(0)
ack 379 win 6432
gre1 12:17:04.741874 IP 10.160.100.38.3582 > 12.160.37.9.http: . ack 2
win 17640
gre1 12:17:04.742200 IP 10.160.100.38.3582 > 12.160.37.9.http: F
378:378(0) ack 2 win 17640
eth2 12:17:04.742224 IP 12.160.37.9.http > 10.160.100.38.3582: . ack 380
win 6432
## Once squid exits gracefully, it automatically restarts.
## Perhaps just a thread died and respawned?
Cheers,
/Jason
