From: Pablo Neira <pablo@eurodev.net>
To: Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] modification in current protocol helper API to handle error/unclean packets
Date: Mon, 14 Jun 2004 13:37:46 +0200 [thread overview]
Message-ID: <40CD8E0A.6050900@eurodev.net> (raw)
In-Reply-To: <40CD0BE7.3050802@trash.net>
Hi Patrick and Jozsef,
I'll reply you both in this email
Jozsef Kadlecsik wrote:
>I like it, too! I think the tcp-window-tracking patch should be made
>dependent of your patch
>
>
happy that you both like it! :-)
>NF_DROP == 0, so it should simply return an NF_* value. Thus the condition
>
>+ /* It may be an special packet, error, unclean... */
>+ if ((ret = proto->error(*pskb, &ctinfo, hooknum)))
>+ return ret;
>
>should be
>
>+ /* It may be an special packet, error, unclean... */
>+ if ((ret = proto->error(*pskb, &ctinfo, hooknum)) != NF_ACCEPT)
>+ return ret;
>
>
I'm still in doubt, if we found an unclean packet, we should return
NF_ACCEPT, so we let the packet continues its travel. In that case, the
skbuff won't have a conntrack associated and the sysadmin could
explicitely drop invalid packets with an iptables rule, am I right?
So I need a return value to say: "do nothing", that is, go ahead with
conntrack session, and I can use neither NF_ACCEPT to do that nor 0
because == NF_DROP. Should I use -1 then?
>And as Patrick noted, UDP checksumming in IPv4 is not mandatory.
>
I missed that, I'll take it into account for an extra patch to check for
udp/icmp unclean packets which will go on top of my patch.
Patrick McHardy wrote:
> Couldn't you use ip_ct_find_proto(IPPROTO_ICMP)->error() instead ?
true, I'll have a look at this
> invert_tuple and find_tuple probably should be prefixed with ip_ct_
> then.
so, I could rename those
>> - oh! I added udp checksum checking, well, I just stole that from
>> Joszef's tcp tracking code and rename things...
>
>
> This should be an extra patch.
ok, so I'll do them like an extra patch on top of this.
regards,
Pablo
next prev parent reply other threads:[~2004-06-14 11:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 0:10 [PATCH] modification in current protocol helper API to handle error/unclean packets Pablo Neira
2004-06-14 2:22 ` Patrick McHardy
2004-06-14 3:05 ` Patrick McHardy
2004-06-14 11:37 ` Pablo Neira [this message]
2004-06-14 14:03 ` Jozsef Kadlecsik
2004-06-17 12:09 ` Pablo Neira
2004-06-17 12:46 ` Patrick McHardy
2004-06-17 13:46 ` Pablo Neira
2004-06-17 14:15 ` Patrick McHardy
2004-06-17 17:26 ` Pablo Neira
2004-06-17 13:17 ` Jozsef Kadlecsik
2004-06-20 19:17 ` Martin Josefsson
2004-06-20 22:05 ` Pablo Neira
2004-06-21 0:07 ` Patrick McHardy
2004-06-22 12:19 ` Pablo Neira
2004-06-21 8:56 ` Jozsef Kadlecsik
2004-06-21 10:14 ` Henrik Nordstrom
2004-06-21 10:51 ` Jozsef Kadlecsik
2004-06-22 4:39 ` Willy Tarreau
2004-06-22 11:14 ` Pablo Neira
2004-06-22 13:17 ` Jozsef Kadlecsik
2004-06-22 13:31 ` Jozsef Kadlecsik
2004-06-22 16:18 ` Willy Tarreau
2004-06-21 12:46 ` Pablo Neira
2004-06-21 13:32 ` Jozsef Kadlecsik
2004-06-21 8:11 ` Jozsef Kadlecsik
2004-06-14 9:05 ` Jozsef Kadlecsik
2004-06-21 4:20 ` Willy Tarreau
2004-06-21 13:40 ` Jozsef Kadlecsik
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=40CD8E0A.6050900@eurodev.net \
--to=pablo@eurodev.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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.