Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jose Maria Lopez <jkerouac@eresmas.com>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: RE: Iptables error
Date: 25 Aug 2004 21:25:22 +0200	[thread overview]
Message-ID: <1093444934.26740.8.camel@nostromo.bgsecm.com> (raw)
In-Reply-To: <D5C9032B2B09C64EA2409D6214E91AC90512D0@asimail2.alphanumeric.com>

El mié, 25 de 08 de 2004 a las 14:56, Jason Opperisano escribió:
> > 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
> 

I also agree the problem could be that you have not recompiled the
userspace utils, but it's strage, because I think p-o-m use to ask
for the iptables sources to be executed. Maybe you have a too old
version of iptables or maybe the p-o-m ng it's too new for your
quite old (2.4.20) kernel. Why don't updating the iptables to the
last version and also the kernel to 2.4.27 so you have to recompile
both of them?

-- 
Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
jkerouac@bgsec.com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
                -- Jack Kerouac, "On the Road"



  reply	other threads:[~2004-08-25 19:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 12:56 Iptables error Jason Opperisano
2004-08-25 19:25 ` Jose Maria Lopez [this message]
  -- 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=1093444934.26740.8.camel@nostromo.bgsecm.com \
    --to=jkerouac@eresmas.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