Bug 24350 - ipchains no longer compatible with kernel
ipchains no longer compatible with kernel
Status: CLOSED DUPLICATE of bug 22612
Product: Red Hat Linux
Classification: Retired
Component: ipchains (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
: Security
Depends On:
  Show dependency treegraph
Reported: 2001-01-19 06:33 EST by Henri Schlereth
Modified: 2007-03-26 23:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-19 08:12:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Henri Schlereth 2001-01-19 06:33:30 EST
The version of ipchains as supplied on the beta2 disc's is no longer compatible with the 2.4 kernel.
ipchains is now a loadable module in the kernel. During an upgrade from RH70 --> beta2 it will however still
upgrade ipchains. This becomes a security issue because ipchains will no longer work unless loaded as 
a module. The ipchains init scripts do not address this nor is there an apparent ipchains --> netfilter
conversion process in place. The net result is that if you upgrade a firewall you end up unprotected.

Even if the upgrade were to remove ipchains unless there is a conversion script you again would wind
up uprotected.

Last year I had 239 attempts that were blocked by a combination of ipchains, portsentry, and tcp_wrappers. As it
stands I would not dare put this on my firewall if this were the finished product.
Comment 1 Henri Schlereth 2001-01-19 08:12:26 EST
Further research shows that ipchains 1.3.10-1 will work after you insmod the
That still leaves the issue of why isnt this automated?  If this had been a real
firewall I 
would have had an unprotected network until I figured out that it requires/needs
the module.
Comment 2 Bill Nottingham 2001-01-19 12:09:10 EST

*** This bug has been marked as a duplicate of 22612 ***

Note You need to log in before you can comment on or make changes to this bug.