All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herve Eychenne <rv@wallfire.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Max Kellermann <max@duempel.org>,
	netfilter-devel@lists.netfilter.org,
	Robert Iakobashvili <roberti@GoNetworks.com>
Subject: Re: [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview
Date: Wed, 19 Jan 2005 09:56:15 +0100	[thread overview]
Message-ID: <20050119085615.GD10200@eychenne.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0501190900080.10476@blackhole.kfki.hu>

On Wed, Jan 19, 2005 at 09:30:38AM +0100, Jozsef Kadlecsik wrote:

> On Wed, 19 Jan 2005, Max Kellermann wrote:

> > I have worked a bit on porting the H.323 conntrack module to Linux
> > 2.6. Here is my first preview. Both connection tracking and NAT work
> > well in my home network (gnomemeeting and ohphone, tunneling
> > disabled).
> >
> > It's still the old brute force method, no real protocol evaluation is
> > performed. I will implement that the "right" way after the port to the
> > Linux 2.6 API is finished and tested. The current algorithm is not
> > recommended for production environments, because it is insecure,
> > sometimes buggy and horribly inefficient.

> Yes, exactly. That was why I refrained from porting it to 2.6...

> If you want to write a decent helper, then ethereal has got a H.323 (ASN)
> decoder written in C, which could probably be re-used. :-)

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?

 Herve

-- 
 _
(°=  Hervé Eychenne
//)
v_/_ WallFire project:  http://www.wallfire.org/

  parent reply	other threads:[~2005-01-19  8:56 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 [this message]
2005-01-19  9:06     ` Max Kellermann
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=20050119085615.GD10200@eychenne.org \
    --to=rv@wallfire.org \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=max@duempel.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=roberti@GoNetworks.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.