From: "Игорь Осин" <osin@vita-samara.ru>
To: netfilter@lists.netfilter.org
Subject: pom-ng h323-conntrack-nat failure
Date: Tue, 22 Mar 2005 08:23:22 +0400 [thread overview]
Message-ID: <005e01c52e96$e29cdbf0$7900000a@vita.local> (raw)
kernel 2.6.11
iptables-1.3.1.
patch-o-matic-ng-20050320
# ./runme h323-conntrack-nat
Hey! KERNEL_DIR is not set.
Where is your kernel source directory? [/usr/src/linux]
Hey! IPTABLES_DIR is not set.
Where is your iptables source code directory? [/usr/src/iptables]
Loading patchlet
definitions.............................................................................................
done
Welcome to Patch-o-matic ($Revision: 3733 $)!
Kernel: 2.6.11, /usr/src/linux
Iptables: 1.3.1, /usr/src/iptables
Each patch is a new feature: many have minimal impact, some do not.
Almost every one has bugs, so don't apply what you don't need!
-------------------------------------------------------
Already applied:
Testing h323-conntrack-nat... not applied
The h323-conntrack-nat patch:
Author: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>, Max Kellermann
<max@duempel.org>
Status: Alpha
[...]
-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?] Y
unable to find ladd slot in src
/tmp/pom-19236/include/linux/netfilter_ipv4/ip_conntrack.h
-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?]
...
next reply other threads:[~2005-03-22 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 4:23 Игорь Осин [this message]
2005-03-22 4:37 ` port triggering with iptables Chow Kin Lum
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 11:39 pom-ng h323-conntrack-nat failure Justin Piszcz
2005-03-22 11:48 ` Igor Osin
2005-03-21 13:47 Игорь Осин
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='005e01c52e96$e29cdbf0$7900000a@vita.local' \
--to=osin@vita-samara.ru \
--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;
as well as URLs for NNTP newsgroup(s).