From: Patrick McHardy <kaber@trash.net>
To: philipc@snapgear.com
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 3/4] log dropped ICMP redirects
Date: Wed, 24 May 2006 18:26:10 +0200 [thread overview]
Message-ID: <44748922.4060207@trash.net> (raw)
In-Reply-To: <20060524040951.092582000@snapgear.com>
philipc@snapgear.com wrote:
> Log dropped ICMP redirects for untracked connections.
>
> This was required to meet a certification test. But there are
> many more locations that can drop packets without logging them,
> which weren't tested for certification. Should all instances of
> NF_DROP in netfilter/iptables have a call to nf_log_packet?
There was a patch called "dropped table" once that hooked in kfree_skb.
I'm also not completely satisfied with the current situation .. but
I don't think adding excessive packet logging is the best solution,
often drops just occur because of failed validity checks which can
just as well happen outside of the netfilter code.
In this case I'm actually having trouble understanding what the code
is supposed to do, why would we receive an ICMP redirect for a
unhashed connection (unhashed == first packet hasn't even left the
box yet)?
> @@ -132,8 +133,13 @@ ip_nat_fn(unsigned int hooknum,
> (*pskb)->nh.iph->ihl*4,
> sizeof(_hdr), &_hdr);
> if (hp != NULL &&
> - hp->type == ICMP_REDIRECT)
> + hp->type == ICMP_REDIRECT) {
> + if (LOG_INVALID(IPPROTO_ICMP))
> + nf_log_packet(PF_INET, 0, *pskb,
> + NULL, NULL, NULL, "ip_nat: "
> + "untracked ICMP redirect ");
> return NF_DROP;
> + }
> }
> return NF_ACCEPT;
> }
>
> --
>
>
next prev parent reply other threads:[~2006-05-24 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 4:04 [PATCH 0/4] netfilter patches for consideration philipc
2006-05-24 4:04 ` [PATCH 1/4] TCPMSS: dont drop packets philipc
2006-05-24 16:16 ` Patrick McHardy
2006-05-24 23:42 ` Philip Craig
2006-05-26 14:40 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 2/4] TCPMSS: clamp to input interface MTU too philipc
2006-05-24 16:18 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 3/4] log dropped ICMP redirects philipc
2006-05-24 16:26 ` Patrick McHardy [this message]
2006-05-25 2:34 ` Philip Craig
2006-05-26 14:49 ` Patrick McHardy
2006-05-24 4:04 ` [PATCH 4/4] drop ftp bounce attacks philipc
2006-05-24 16:31 ` Patrick McHardy
2006-05-25 2:55 ` Philip Craig
2006-05-26 14:51 ` Patrick McHardy
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=44748922.4060207@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=philipc@snapgear.com \
/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.