mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrik Nordstrom <hno@marasystems.com>
To: Chris Chabot <chabotc@reviewboard.com>,
	Nick Craig-Wood <ncw@axis.demon.co.uk>
Cc: Harald Welte <laforge@gnumonks.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, netfilter-devel@lists.samba.org
Subject: Re: 2.4.18-pre9: iptables screwed?
Date: Fri, 15 Feb 2002 00:11:25 +0100	[thread overview]
Message-ID: <200202150006.35881@henrik.marasystems.com> (raw)
In-Reply-To: <a3vjts$r7l$1@cesium.transmeta.com> <20020214161225.A2867@axis.demon.co.uk> <3C6C0977.7030004@reviewboard.com>
In-Reply-To: <3C6C0977.7030004@reviewboard.com>

This topic has been discussed on netfilter-devel quite recently.

The RedHat RPM for some reason compiles the iptables package with 
debugging enabled. This makes the program overly paranoid about 
different revisions of the netfilter kernel components.

Details:

When you build iptables from the source tarball then the Makefile 
includes -DNDEBUG to disable all debugging. Unfortunately the RPM 
build process overrides the compilation options set in the Makefile 
and leaves NDEBUG undefined, causing a lot of debug code to be 
compiled in.

Regards
Henrik Nordström



On Thursday 14 February 2002 20.01, Chris Chabot wrote:
> I ran into the same problems with 2.4.18pre9, however upgrading to
> iptables 1.2.5 fixed the problem. (there's no redhat packages for
> it yet, i did a compile of the source pkg)
>
> 	-- Chris
>
> Nick Craig-Wood wrote:
> > On Fri, Feb 08, 2002 at 09:46:49AM +0100, Harald Welte wrote:
> >>On Thu, Feb 07, 2002 at 08:24:28PM -0800, H. Peter Anvin wrote:
> >>>I get the following error with iptables on 2.4.18-pre9:
> >>>
> >>>sudo iptables-restore < /etc/sysconfig/iptables
> >>>iptables-restore: libiptc/libip4tc.c:384: do_check: Assertion
> >>>`h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> >>>Abort (core dumped)
> >
> > I've noticed this too.
> >
> > Specifically it is fine with 2.4.17 but broken with
> > 2.4.18-pre7-ac2
> >
> > I use the mangle table to set the TOS for a few things but it
> > gives this error :-
> >
> >   iptables -t mangle -A add-tos -p tcp --dport ssh -m tos --tos
> > Minimize-Delay
> >
> >   iptables: libiptc/libip4tc.c:384: do_check: Assertion
> > `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> >
> >>Could you please tell me, what iptables version are you using?
> >>(btw: please follow-up to netfilter-devel@lists.samba.org)
> >
> > This is using Redhat 7.2 iptables v1.2.4 from the redhat package
> > iptables-1.2.4-2.
> >
> > Apologies if this info is too late but I didn't see a followup to
> > lkml.

  reply	other threads:[~2002-02-14 23:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  4:24 H. Peter Anvin
2002-02-08  8:03 ` Stelian Pop
2002-02-08  8:46 ` Harald Welte
2002-02-14 16:12   ` Nick Craig-Wood
2002-02-14 19:01     ` Chris Chabot
2002-02-14 23:11       ` Henrik Nordstrom [this message]
2002-02-14 23:37       ` Harald Welte
2002-02-14 19:15     ` Stelian Pop
2002-02-14 23:31     ` Harald Welte
2002-02-14 22:28   ` Michael Cohen
2002-02-27  1:15     ` Lukasz Trabinski

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=200202150006.35881@henrik.marasystems.com \
    --to=hno@marasystems.com \
    --cc=chabotc@reviewboard.com \
    --cc=hpa@zytor.com \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw@axis.demon.co.uk \
    --cc=netfilter-devel@lists.samba.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®