All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Carlos Munoz <carlos@kenati.com>
Cc: Ranjit Deshpande <ranjit@kenati.com>,
	netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6.20.4] Connection tracking: New SIP ALG that actually works
Date: Wed, 18 Apr 2007 20:32:25 +0200	[thread overview]
Message-ID: <46266439.2060805@trash.net> (raw)
In-Reply-To: <46265B28.2020501@kenati.com>

Carlos Munoz wrote:
> Patrick McHardy wrote:
> 
>> What you should have done is report the problems you were seeing or send
>> patches for the existing version. We're not going to just toss in a
>> huge rewritten version, especially not since you're reintroducing
>> a lot of bugs and do lots of things that only work on 2.4.
>
> 
> I understand. We've had our sip alg before one was distributed with the
> kernel sources. When we upgrade to new kernel versions we regression
> test all features and the sip alg has always failed. So we keep using
> our sip alg. Management won't allocate resources to fix the sip alg in
> the kernel when ours works. However, that might change if our sip alg
> stops working.


I see. It will stop working in 2.6.22 since we're going to remove
ip_conntrack, so you will at least have to port it to nf_conntrack
when you upgrade your kernel. Of course it would be very much
appreciated if you can convince your management to fix the version
in the kernel instead :)

      reply	other threads:[~2007-04-18 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 20:51 [PATCH 2.6.20.4] Connection tracking: New SIP ALG that actually works Carlos Munoz
2007-04-18  4:47 ` Patrick McHardy
2007-04-18 17:53   ` Carlos Munoz
2007-04-18 18:32     ` Patrick McHardy [this message]

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=46266439.2060805@trash.net \
    --to=kaber@trash.net \
    --cc=carlos@kenati.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=ranjit@kenati.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.