From: "Jason Opperisano" <Jopperisano@alphanumeric.com>
To: netfilter@lists.netfilter.org
Subject: RE: Iptables error
Date: Wed, 25 Aug 2004 08:56:49 -0400 [thread overview]
Message-ID: <D5C9032B2B09C64EA2409D6214E91AC90512D0@asimail2.alphanumeric.com> (raw)
> This morning I rebooted one of our firewalls, I have created a new kernel for
> it (2.4.20, patched kernel with latest p-o-m ng).
> When I run my firewall script, all I get is errors, seems to be a problem with
> iptables 'tables' as none of the rules are create but the default policies
> are in place, in dmesg I have the following error:
>
> ip_tables: table screwed up!
>
> This firewall is a production server and I can only really take it down
> tonight to check it, anyone had something like this before?
>
> Paulo
sounds to me like you applied p-o-m, rebuilt your kernel, but did not rebuild your userspace. anytime you apply a patch from pom that changes structures, or requires additional libraries, you need to recompile your userspace iptables utilities. since it's unclear to me when the userspace rebuild is required--i do it everytime. sounds like it was in this case for you...
-j
next reply other threads:[~2004-08-25 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 12:56 Jason Opperisano [this message]
2004-08-25 19:25 ` Iptables error Jose Maria Lopez
-- strict thread matches above, loose matches on Subject: below --
2009-06-25 12:56 iptables ERROR Ritesh Majumdar
2009-06-25 13:39 ` Richard Horton
2009-06-25 14:00 ` Ritesh Majumdar
2009-06-25 15:11 ` Jan Engelhardt
2009-06-25 18:08 ` Jozsef Kadlecsik
2004-08-25 8:19 Iptables error Paulo Andre
2004-01-15 0:08 IPTables error Jerry Rasmussen
2004-01-15 0:17 ` Antony Stone
2002-11-12 0:07 iptables error jelenkovic
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=D5C9032B2B09C64EA2409D6214E91AC90512D0@asimail2.alphanumeric.com \
--to=jopperisano@alphanumeric.com \
--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