tcp incomplete log
Hi,
I found curious log like this in my iptables log:
Jul 13 07:21:48 orfeo kernel: ICMP INPUT IN=eth0 OUT= MAC=00:30:6e:36:5d:23:00:d0:95:4c:5c:d8:08:00 SRC=207.159.62.1 DST=my-server-ip LEN=56 TOS=0x00 PREC=0x00 TTL=236 ID=56340 PROTO=ICMP TYPE=3 CODE=13 [SRC=my-server-ip DST=63.240.81.5 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=58670 PROTO=TCP INCOMPLETE [8 bytes] ]
The server, is a squid proxy
I have looking for this on previous post, but I am a bit confused.
Thanks in advance.
Emilio C.
Quoted 11 lines · Emilio Casbas
I found curious log like this in my iptables log:
Jul 13 07:21:48 orfeo kernel: ICMP INPUT IN=eth0 OUT=MAC=00:30:6e:36:5d:23:00:d0:95:4c:5c:d8:08:00 SRC=207.159.62.1 DST=my-server-ip LEN=56 TOS=0x00 PREC=0x00 TTL=236 ID=56340 PROTO=ICMP TYPE=3 CODE=13 [SRC=my-server-ip DST=63.240.81.5 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=58670 PROTO=TCP INCOMPLETE [8 bytes] ]
The server, is a squid proxy
I have looking for this on previous post, but I am a bit confused.
Your squid proxy tried to connect to 63.240.81.5, but the connection failed because the connection packet was filtered.
Type Name
---- -------------------------
3 Destination Unreachable Codes
13 Communication Administratively Prohibited
The ICMP error was returned by 207.159.62.1, which is a router or firewall somewhere between your server and 63.240.81.5.
I believe the "INCOMPLETE" is netfilter's connection tracking system telling you the TCP connection never completely opened. This makes sense, since your server probably only sent the initial SYN before receiving the ICMP error (instead of the expected SYN+ACK).
-James