From: Stephen Jones <hivemynd@hivemynd.net>
To: netfilter-devel@lists.netfilter.org
Subject: pptp-conntrack-nat will not apply to 2.4.29 - Workaround
Date: Sat, 22 Jan 2005 01:45:06 -0600 [thread overview]
Message-ID: <41F20482.4090300@hivemynd.net> (raw)
Hello devel-list!
I was attempting to bake a 2.4.29 kernel this weekend and ran into a
problem with applying the pptp-conntrack-nat patch from
patch-o-matic-ng-20040621 and as well from the svn version 3605.
The iptables source is for 1.2.11
The error from patch-o-matic ./runme is:
"unable to find ladd slot in src
/usr/src/linux-2.4.29/net/ipv4/netfilter/Config.in"
I compared the Config.in files from a clean 2.4.28 to the one from
2.4.29, and the only difference:
# Output of:
diff --normal /linux-2.4.28-clean/net/ipv4/netfilter/Config.in
/linux-2.4.29-clean/net/ipv4/netfilter/Config.in
69d68
< bool ' NAT of local connections (READ HELP)'
CONFIG_IP_NF_NAT_LOCAL
I got the pptp-conntrack-nat patch to apply by simply adding that line
back to the /net/ipv4/netfilter/Config.in that is included with the
2.4.29 sources. The problem is the match line in the:
/patch-o-matic-ng-XXXX/pptp-conntrack-nat/linux/net/ipv4/netfilter/Config.in.ladd_2
file is looking for:
bool ' NAT of local connections (READ HELP)'
CONFIG_IP_NF_NAT_LOCAL
in the /net/ipv4/netfilter/Config.in file, and it is no longer there.
I don't know enough about the structure of the Config.in files to
suggest an appropriate, permanent solution :(
I then remove the unneeded line before compiling the kernel sources.
PS: The nat-reservations patch is incompatible with the
pptp-conntrack-nat patch, perhaps a check in the pom-ng could prevent
people from accidentally "shooting themselves in the foot" with these
two? :)
next reply other threads:[~2005-01-22 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 7:45 Stephen Jones [this message]
2005-02-01 13:20 ` pptp-conntrack-nat will not apply to 2.4.29 - Workaround Harald Welte
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=41F20482.4090300@hivemynd.net \
--to=hivemynd@hivemynd.net \
--cc=netfilter-devel@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 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.