From: Russell King <rmk@arm.linux.org.uk>
To: Joe <joeja@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.18 and RH 7.2
Date: Wed, 27 Feb 2002 20:26:22 +0000 [thread overview]
Message-ID: <20020227202622.A25404@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3C7D24F9.B93D47E6@mindspring.com>
In-Reply-To: <3C7D24F9.B93D47E6@mindspring.com>; from joeja@mindspring.com on Wed, Feb 27, 2002 at 10:27:05AM -0800
On Wed, Feb 27, 2002 at 10:27:05AM -0800, Joe wrote:
> Not sure if this has been reported as I am not on the mailing list. I'm
> guessing probably yes.
>
> I have a RH 7.2 box and am getting the following error from iptables and
> kernel 2.4.18. I don't get it in 2.4.17.
>
> output from /etc/init.d/iptables start
>
> Flushing all current rules and user defined chains: [ OK ]
> Clearing all current rules and user defined chains: [ OK ]
> iptables: libiptc/libip4tc.c:384: do_check: Assertion
> `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> /etc/init.d/iptables: line -242: 1222 Aborted iptables
> -t $i -Fiptables: libiptc/libip4tc.c:384: do_check: Assertion
> `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> /etc/init.d/iptables: line -239: 1225 Aborted iptables
> -t $i -Xiptables: libiptc/libip4tc.c:384: do_check: Assertion
> `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> /etc/init.d/iptables: line -235: 1228 Aborted iptables
> -t $i -ZApplying iptables firewall rules:
> iptables-restore: libiptc/libip4tc.c:384: do_check: Assertion
> `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
> /etc/init.d/iptables: line -232: 1230 Done grep -v
> "^[[:space:]]*#" $IPTABLES_CONFIG
> 1231 | grep -v '^[[:space:]]*$'
> 1232 Aborted | /sbin/iptables-restore -c
I'll add a "me too" to this - 2.4.18, iptables 1.2.4
Setting up IPv4 mangle rules:
iptables: libiptc/libip4tc.c:384: do_check: Assertion `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
/etc/fw-ipv4/mangle: line 2: 215 Aborted iptables -t mangle -F
iptables: libiptc/libip4tc.c:384: do_check: Assertion `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
/etc/fw-ipv4/mangle: line 3: 216 Aborted iptables -t mangle -X
iptables: libiptc/libip4tc.c:384: do_check: Assertion `h->info.valid_hooks == (1 << 0 | 1 << 3)' failed.
/etc/fw-ipv4/mangle: line 15: 217 Aborted iptables -t mangle -A PREROUTING -i eth0 -d xxx.xxx.xxx.xxx/xx -j ACCEPT
... lots more ...
The rules do appear to be in the kernel however.
iptables 1.2.4 was rebuild for the 2.4.17 because it stopped working at
that point. I hope it isn't requirement to rebuild iptables against each
stable kernel release.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-02-27 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 18:27 kernel 2.4.18 and RH 7.2 Joe
2002-02-27 20:26 ` Russell King [this message]
2002-02-27 21:12 ` Alan Cox
2002-02-27 22:49 ` Joe
2002-02-27 21:17 ` 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=20020227202622.A25404@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.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