From: James Sneeringer <james+netfilter@vincentsystems.com>
To: netfilter@lists.netfilter.org
Subject: Re: tcp incomplete log
Date: Thu, 15 Jul 2004 18:54:47 -0500 [thread overview]
Message-ID: <20040715235447.GA25403@valjean.si.ocslink.com> (raw)
In-Reply-To: <40F65927.80104@unav.es>
On Thu, Jul 15, 2004 at 12:15:03PM +0200, Emilio Casbas wrote:
> 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
prev parent reply other threads:[~2004-07-15 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 10:15 tcp incomplete log Emilio Casbas
2004-07-15 23:54 ` James Sneeringer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040715235447.GA25403@valjean.si.ocslink.com \
--to=james+netfilter@vincentsystems.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.