From: Philip Craig <philipc@snapgear.com>
To: Philipp Stader <me@ph1l.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: pptp_conntrack_nat - patch-o-matic-ng-20040409 - kernel 2.4.25
Date: Tue, 13 Apr 2004 12:25:09 +1000 [thread overview]
Message-ID: <407B4F85.70109@snapgear.com> (raw)
In-Reply-To: <3340.217.83.169.111.1081644254.squirrel@217.83.169.111>
Philipp Stader wrote:
> i downloaded linux 2.4.25 from kernel.org, patch-o-matic-ng-20040409 and
> iptables 1.2.9. Unpacked all in /usr/src/ created links linux and iptables
> then applied the pptp_conntrack_nat patch which applied without errors.
> When i try to compile the kernel i get the following errors.
>
> net/network.o: In function `pptp_expectfn':
> net/network.o(.text+0x3e899): undefined reference to
> `ip_ct_gre_keymap_destroy'
> net/network.o: In function `pptp_timeout_related':
> net/network.o(.text+0x3e8cc): undefined reference to
> `ip_ct_gre_keymap_destroy'
> net/network.o: In function `conntrack_pptp_help':
> net/network.o(.text+0x3ed09): undefined reference to `ip_ct_gre_keymap_add'
> net/network.o(.text+0x3ed2e): undefined reference to `ip_ct_gre_keymap_add'
> net/network.o(.text+0x3ed96): undefined reference to `ip_ct_gre_keymap_add'
> net/network.o(.text+0x3edaa): undefined reference to `ip_ct_gre_keymap_add'
> net/network.o(.text+0x3edc8): undefined reference to
> `ip_ct_gre_keymap_destroy'
> net/network.o: In function `tcp_help':
> net/network.o(.text+0x3fd66): undefined reference to
> `ip_ct_gre_keymap_change'
> net/network.o(.text+0x3fd73): undefined reference to
> `ip_ct_gre_keymap_change'
This patch should fix that:
http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014618.html
--
Philip Craig - SnapGear, A CyberGuard Company - http://www.SnapGear.com
prev parent reply other threads:[~2004-04-13 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 0:44 pptp_conntrack_nat - patch-o-matic-ng-20040409 - kernel 2.4.25 Philipp Stader
2004-04-13 2:25 ` Philip Craig [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=407B4F85.70109@snapgear.com \
--to=philipc@snapgear.com \
--cc=me@ph1l.de \
--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