From: Max Kellermann <max@duempel.org>
To: Javier Kohen <jkohen@users.sourceforge.net>
Cc: netfilter-devel@lists.netfilter.org, netfilter@lists.netfilter.org
Subject: Re: Cannot apply h323-conntrack-nat
Date: Fri, 25 Mar 2005 23:20:27 +0100 [thread overview]
Message-ID: <20050325222027.GA12915@roonstrasse.net> (raw)
In-Reply-To: <1111695753.32351.34.camel@localhost>
On 2005/03/24 21:22, Javier Kohen <jkohen@users.sourceforge.net> wrote:
> I'm trying to apply the h323-conntrack-nat patch to kernel 2.6.11-ck2
> using pom-ng revision 3805, but it keeps saying: «unable to find ladd
> slot in src /tmp/pom-29949/include/linux/netfilter_ipv4/ip_conntrack.h.»
> Note that the -ck2 patchset does not modify file ip_conntrack.h.
Hi Javier,
I have already posted patches to h323-conntrack-nat, unfortunately
they have not been applied to svn yet. You can find patches against
pom-ng trunk on my home page:
http://max.kellermann.name/projects/netfilter/h323.html
Max
next prev parent reply other threads:[~2005-03-25 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 20:22 Cannot apply h323-conntrack-nat Javier Kohen
2005-03-25 22:20 ` Max Kellermann [this message]
2005-04-03 17:32 ` Patrick McHardy
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=20050325222027.GA12915@roonstrasse.net \
--to=max@duempel.org \
--cc=jkohen@users.sourceforge.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox