mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* iptables and 2.4.17
@ 2002-01-16 11:13 Luca Adesso
  2002-01-16 12:03 ` Harald Welte
                   ` (3 more replies)
  0 siblings, 4 replies; 6+ messages in thread
From: Luca Adesso @ 2002-01-16 11:13 UTC (permalink / raw)
  To: linux-kernel

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

I downloaded 2.4.16 and compiled with the same configuration and it works fine.
I have Slackware 7.0

Please CC me for the reply.
Thanks.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iptables and 2.4.17
  2002-01-16 11:13 iptables and 2.4.17 Luca Adesso
@ 2002-01-16 12:03 ` Harald Welte
  2002-01-16 13:28 ` Luca Adesso
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 6+ messages in thread
From: Harald Welte @ 2002-01-16 12:03 UTC (permalink / raw)
  To: Luca Adesso; +Cc: linux-kernel

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+(*)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iptables and 2.4.17
  2002-01-16 11:13 iptables and 2.4.17 Luca Adesso
  2002-01-16 12:03 ` Harald Welte
@ 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
  3 siblings, 1 reply; 6+ messages in thread
From: Luca Adesso @ 2002-01-16 13:28 UTC (permalink / raw)
  To: Harald Welte; +Cc: linux-kernel

At 13.03 16/01/02 +0100, you wrote:
>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
Sure I always do in the same way!
I go in /usr/src and rm -r linux and rm linux-2.4.5 (the kernel installed 
with Slackware 7.0) then downloaded kernel 2.4.17
make mrproper and reconfigured my kernel.
I create a script to compile the kernel, so I'm sure I do al the same 
everytime.
The script is:
#mkernel begin
#!/bin/sh
make dep && make clean && make bzImage && make modules
make modules_install
cp System.map /boot
cp arch/i386/boot/bzImage /boot
lilo
#mkernel end

>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.
I have problem with iptables.o and with apm.o.
For apm I haven't found help and I never create a working modules so I 
compiled it in the kernel.
I was sure that iptables works like modules and now it's working fine on 
that system with 2.4.16

Any suggestions?


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iptables and 2.4.17
  2002-01-16 11:13 iptables and 2.4.17 Luca Adesso
  2002-01-16 12:03 ` Harald Welte
  2002-01-16 13:28 ` Luca Adesso
@ 2002-01-16 13:46 ` Bruce Harada
  2002-01-16 13:49 ` Luca Adesso
  3 siblings, 0 replies; 6+ messages in thread
From: Bruce Harada @ 2002-01-16 13:46 UTC (permalink / raw)
  To: Luca Adesso; +Cc: laforge, linux-kernel

On Wed, 16 Jan 2002 14:28:53 +0100
Luca Adesso <ladesso@libero.it> wrote:

> I go in /usr/src and rm -r linux and rm linux-2.4.5 (the kernel installed 
> with Slackware 7.0) then downloaded kernel 2.4.17

Er... are you sure you don't mean Slackware 8.0? Slackware 7.0 was 2.2.x.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iptables and 2.4.17
  2002-01-16 11:13 iptables and 2.4.17 Luca Adesso
                   ` (2 preceding siblings ...)
  2002-01-16 13:46 ` Bruce Harada
@ 2002-01-16 13:49 ` Luca Adesso
  3 siblings, 0 replies; 6+ messages in thread
From: Luca Adesso @ 2002-01-16 13:49 UTC (permalink / raw)
  To: Bruce Harada; +Cc: laforge, linux-kernel

At 22.46 16/01/02 +0900, you wrote:
> > with Slackware 7.0) then downloaded kernel 2.4.17
>
>Er... are you sure you don't mean Slackware 8.0? Slackware 7.0 was 2.2.x.
Sorry! you are right! Slackware 8.0


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: iptables and 2.4.17
  2002-01-16 13:28 ` Luca Adesso
@ 2002-01-16 14:32   ` Harald Welte
  0 siblings, 0 replies; 6+ messages in thread
From: Harald Welte @ 2002-01-16 14:32 UTC (permalink / raw)
  To: Luca Adesso; +Cc: linux-kernel

On Wed, Jan 16, 2002 at 02:28:53PM +0100, Luca Adesso wrote:

> >Strange. Are you sure you really did it in the following order:

> Sure I always do in the same way!

Could you please send me your .config kernel configuration in private mail
(NOT to the linux-kernel list), I will try to reproduce your problem

> I was sure that iptables works like modules and now it's working fine on 
> that system with 2.4.16

It definitely works in all relesed kernel version since 2.4.0 as modules, 
I've used all of them :)

> Any suggestions?

-- 
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+(*)

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-01-16 14:42 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-16 11:13 iptables and 2.4.17 Luca Adesso
2002-01-16 12:03 ` Harald Welte
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

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®