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.
Further research shows that ipchains 1.3.10-1 will work after you insmod the ipchains.o. 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.
*** This bug has been marked as a duplicate of 22612 ***