From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Karl Hiramoto <karl@hiramoto.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC 0/4] nfnetlink_queue bypass queue to userspace X bytes of connection
Date: Sun, 25 Jul 2010 12:42:44 +0200 [thread overview]
Message-ID: <4C4C1524.8070805@netfilter.org> (raw)
In-Reply-To: <4C4BDFEC.4080600@hiramoto.org>
On 25/07/10 08:55, Karl Hiramoto wrote:
> On 07/24/2010 08:26 PM, Pablo Neira Ayuso wrote:
>> I think that you could avoid this extensions by means of conntrack marks
>> and the string match. Could you elaborate your application, please?
> I thought about that before i made the extension but there's no way, to do it reliably and avoid race conditions. string matches are also really inefficient, with string matches every packet with a certain mark would be scanned
You can limit the string matching for only a few bytes in the very
beginning of the packet. If you find a matching, you can pass the packet
to user-space. Using the Boyer-Moore approach provides efficient searching.
> but its not necessary since in HTTP because you know which part of the message you want to scan, but it changes on every request/response.
>
> It's a HTTP 1.1 filter, so it has to support persistent connections, multiple requests per connection.
> There is the possibility that some requests are allowed and others are not. Using connmark its posible to allow an entire connection to NF_ACCEPT bypassing the queue, however not really possible when there are multiple requests per connection.
>
> Some of the features of my app are:
> * Filter Accept/block by URL, or HTTP "Host:" tag
> * Log all request/responses, URL, content length, time duration of request / response.
> * Parts of a HTTP 1.1 persistent connection can be rejected, other parts accepted.
This extension seems to me very specific for HTTP/1.1.
next prev parent reply other threads:[~2010-07-25 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 15:44 [RFC 0/4] nfnetlink_queue bypass queue to userspace X bytes of connection Karl Hiramoto
2010-07-24 15:44 ` [RFC 1/4] netfilter/Kconfig: NF_QUEUE_CONNBYTES_BYPASS Karl Hiramoto
2010-07-24 15:44 ` [RFC 2/4] nf_conntrack_queue: define struct that will be stored in nf_ct_extend Karl Hiramoto
2010-07-24 15:44 ` [RFC 3/4] nf_conntrack: add nf_queue extension Karl Hiramoto
2010-07-24 15:44 ` [RFC 4/4] nfnetlink_queue: allow part of a connection to bypass the queue Karl Hiramoto
2010-07-24 18:26 ` [RFC 0/4] nfnetlink_queue bypass queue to userspace X bytes of connection Pablo Neira Ayuso
2010-07-25 6:55 ` Karl Hiramoto
2010-07-25 10:42 ` Pablo Neira Ayuso [this message]
2010-07-26 6:50 ` Karl Hiramoto
[not found] ` <4C4D2C33.6050901@hiramoto.org>
2010-07-26 17:35 ` Pablo Neira Ayuso
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=4C4C1524.8070805@netfilter.org \
--to=pablo@netfilter.org \
--cc=karl@hiramoto.org \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).