From: Oscar Mateo <omateo@gmail.com>
To: netfilter@lists.netfilter.org
Subject: unable to apply PPTP patches
Date: Tue, 6 Sep 2005 16:50:24 +0200 [thread overview]
Message-ID: <a8a372c05090607507e8353c3@mail.gmail.com> (raw)
In-Reply-To: <a8a372c05090607457fce3ca9@mail.gmail.com>
Hi all:
I have been trying to apply the pptp patches (pom-ng-20050905,
iptables-1.3.3) to the kernel source (kernels 2.6.9.x, 2.6.11.x and
2.6.12.x) and I have found the same error that populates the August
2005 netfilter Archives:
- If I only apply the pptp/gre patches I get
`__ip_conntrack_expect_find' undefined (when compiling either in the
kernel or as a module).
- If I try to apply nfnetlink and ctnetlink patches, ctnetlink is
rejected (6 rejects out of 48 hunks).
- If I force the ctnetlink patch, I get `__ip_conntrack_hash_insert' undeclared.
Did someone get the patch working with kernels >= 2.6?
Does anyone have any ideas how to deal with this problem?
Thanks in advance for your help ^_^
Oscar
next parent reply other threads:[~2005-09-06 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8a372c05090607457fce3ca9@mail.gmail.com>
2005-09-06 14:50 ` Oscar Mateo [this message]
2005-09-06 15:50 unable to apply PPTP patches Greg Scott
2005-09-06 16:04 ` Oscar Mateo
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=a8a372c05090607507e8353c3@mail.gmail.com \
--to=omateo@gmail.com \
--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