From: Harald Welte <laforge@gnumonks.org>
To: Luca Adesso <ladesso@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: iptables and 2.4.17
Date: Wed, 16 Jan 2002 13:03:17 +0100 [thread overview]
Message-ID: <20020116130317.H30850@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <5.1.0.14.0.20020116115713.00a96ec0@popmail.libero.it>
In-Reply-To: <5.1.0.14.0.20020116115713.00a96ec0@popmail.libero.it>; from ladesso@libero.it on Wed, Jan 16, 2002 at 12:13:11PM +0100
On Wed, Jan 16, 2002 at 12:13:11PM +0100, Luca Adesso wrote:
> There is some problem with iptables modules and kernel 2.4.17 ?
> I'm using 2.4.10 and it works fine; I tried on another computer at work the
> 2.4.17 but I got unresolved symbol errors
> ip_tables.o: unresolved symbol nf_unregister_sockopt
> ip_tables.o: unresolved symbol nf_register_sockopt
Strange. Are you sure you really did it in the following order:
make clean (better: make mrproper)
- configure the kernel
make bzImage
- install your new bzImage
make modules
make modules_install
- boot into your new kernel
We haven't had any bug report regarding your problem, and I'm personally
also running plain 2.4.17 on one of my boxes without any problems.
> Thanks.
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
next prev parent reply other threads:[~2002-01-16 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 11:13 Luca Adesso
2002-01-16 12:03 ` Harald Welte [this message]
2002-01-16 13:28 ` Luca Adesso
2002-01-16 14:32 ` Harald Welte
2002-01-16 13:46 ` Bruce Harada
2002-01-16 13:49 ` Luca Adesso
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=20020116130317.H30850@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=ladesso@libero.it \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®