From: "Jan Kaastrup" <jka@protego.dk>
To: 'Alexis' <alexis@attla.net.ar>
Cc: 'netfilter' <netfilter@lists.netfilter.org>
Subject: RE: Problems with kernel 2.6.1 and iptables
Date: Mon, 16 Feb 2004 15:05:23 +0100 [thread overview]
Message-ID: <009101c3f495$eb553440$2d64a8c0@pcjka> (raw)
In-Reply-To: <1458943229.20040216101803@attla.net.ar>
Hi
Thanks so much for the answer.
That did the trick.
Now the iptables modules can be loaded automaticly!
I found out that it could not load the module iptable_filter.
So doing:
#modprobe iptable_filter - made it work.
-----Original Message-----
From: Alexis [mailto:alexis@attla.net.ar]
Sent: 16. februar 2004 14:18
To: Jan Kaastrup
Cc: netfilter
Subject: Re: Problems with kernel 2.6.1 and iptables
you need to change some things in /etc/rc.sysinit in order to modules
work again.
check for /proc/ksyms in that file and change it to /proc/kallsyms.
then do a depmod -a
maybe these changes could help you
http://thomer.com/linux/migrate-to-2.6.html
hope it helps
Hello Jan,
Monday, February 16, 2004, 7:13:48 AM, you wrote:
JK> Hi list
JK> I have search google for this error most of my weekend, and I cannot
get
JK> the answer :(
JK> I have upgraded my kernel to 2.6.1 and made all the iptables stuff
as
JK> modules.
JK> I can load all modules by hand perfectly, but still i get this
error:
JK> #Iptables -L
JK> iptables v1.2.9: can't initialize iptables table `filter': Table
does
JK> not exist (do you need to insmod?)
JK> Perhaps iptables or your kernel needs to be upgraded.
JK> I have reinstalled iptables and done depmod -a
JK> I have installed module-init-tools-2.0-pre10
JK> It seems like it cannot mount modules automaticly, any ideas?
JK> Which modules should absolutly be loaded, to make iptables work?
JK> Could it be, that i am missing a
JK>
iptables-need-to-be-installed-to-make-iptables-work-for-kernel-2.6.x-pac
JK> ket?
JK> Thanks a lot
next prev parent reply other threads:[~2004-02-16 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 15:39 Routing problem Carlos Fernandez Sanz
2004-02-13 15:50 ` Antony Stone
2004-02-13 16:30 ` Carlos Fernandez Sanz
2004-02-13 17:12 ` Antony Stone
2004-02-14 8:41 ` Carlos Fernandez Sanz
2004-02-14 9:09 ` Antony Stone
2004-02-14 15:15 ` Carlos Fernandez Sanz
2004-02-14 15:19 ` Carlos Fernandez Sanz
2004-02-14 15:38 ` Antony Stone
2004-02-16 10:13 ` Problems with kernel 2.6.1 and iptables Jan Kaastrup
2004-02-16 10:26 ` Ray Leach
2004-02-16 10:47 ` Antony Stone
2004-02-16 11:19 ` Ray Leach
2004-02-16 13:18 ` Alexis
2004-02-16 14:05 ` Jan Kaastrup [this message]
2004-02-13 17:16 ` Routing problem Scott MacKay
2004-02-14 8:47 ` Carlos Fernandez Sanz
2004-02-13 16:53 ` John A. Sullivan III
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='009101c3f495$eb553440$2d64a8c0@pcjka' \
--to=jka@protego.dk \
--cc=alexis@attla.net.ar \
--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