From: Max Kellermann <max@duempel.org>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview
Date: Wed, 19 Jan 2005 10:06:32 +0100 [thread overview]
Message-ID: <20050119090632.GA15919@roonstrasse.net> (raw)
In-Reply-To: <20050119085615.GD10200@eychenne.org>
On 2005/01/19 09:56, Herve Eychenne <rv@wallfire.org> wrote:
> Yes... but do we really want a big ASN-1 parser in the kernel? Is
> there a nice way to have it rely on kernel facilities, while staying
> in userspace though?
The module needs to know one thing: the location of the sender's IP
and port within the data portion of the packet. It currently does that
by looking for the raw IP, and using whatever follows as the port
number.
I believe it's possible to implement a tiny parser without all the
features we don't need. Though I havn't looked at the protocol
in-depth yet.
Max
next prev parent reply other threads:[~2005-01-19 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 0:43 [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview Max Kellermann
2005-01-19 0:44 ` [PATCH pom-ng 1/5] update kernel requires Max Kellermann
2005-01-19 0:45 ` [PATCH pom-ng 2/5] author update Max Kellermann
2005-01-19 0:46 ` Max Kellermann
2005-01-19 0:45 ` [PATCH pom-ng 3/5] whitespace and indentation Max Kellermann
2005-01-19 0:47 ` [PATCH pom-ng 4/5] use c99 initializers Max Kellermann
2005-01-19 0:47 ` [PATCH pom-ng 5/5] port the module to Linux 2.6 Max Kellermann
2005-01-19 8:30 ` [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview Jozsef Kadlecsik
2005-01-19 8:48 ` Max Kellermann
2005-01-19 8:56 ` Herve Eychenne
2005-01-19 9:06 ` Max Kellermann [this message]
2005-01-19 9:59 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2005-01-19 13:08 Robert Iakobashvili
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=20050119090632.GA15919@roonstrasse.net \
--to=max@duempel.org \
--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.