All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Willy Tarreau <willy@w.ods.org>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
	Henrik Nordstrom <hno@marasystems.com>,
	Martin Josefsson <gandalf@wlug.westbo.se>,
	Patrick McHardy <kaber@trash.net>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] modification in current protocol helper API to handle error/unclean packets
Date: Tue, 22 Jun 2004 13:14:08 +0200	[thread overview]
Message-ID: <40D81480.3000402@eurodev.net> (raw)
In-Reply-To: <20040622043928.GA21406@alpha.home.local>

Hi Willy,

Willy Tarreau wrote:

>Hi Jozsef,
>
>On Mon, Jun 21, 2004 at 12:51:41PM +0200, Jozsef Kadlecsik wrote:
> 
>  
>
>>So you could live happily if such packets are marked as INVALID by
>>conntrack, which implies then that the ICMP code/type checking would be
>>acceptable as well? [Pablo's patch did not want to drop the packets but
>>mark as INVALID.]
>>
>>It's time to add documentation exactly which packets are dropped or marked
>>as INVALID by conntrack.
>>    
>>
>
>May I ask that we could have a new result other than INVALID for such
>packets ? It's becoming difficult to differenciate :
>
>  - valid packets for which there is no session
>  - valid packets for which there is a session but which are invalid wrt
>    this session (wrong flags, sequence numbers, retransmits, ...)
>  - invalid packets (in the 'unclean' sense)
>  
>

I have an idea, in the case of unclean packets, perhaps we could use the 
nfcache field in skb to set a special flag like "NFC_CLEAN". Could we 
use nfcache for that purpose?

regards,
Pablo

  reply	other threads:[~2004-06-22 11:14 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
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 [this message]
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=40D81480.3000402@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=gandalf@wlug.westbo.se \
    --cc=hno@marasystems.com \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=willy@w.ods.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.