Christian Villa Real Lopes wrote: > Andrew Suffield wrote: >> Then you most likely botched the installation of the new version of >> iptables; somewhere, the paths got mixed up. This is likely to cause >> you further trouble later. I'm not sufficiently familiar with redhat >> to guess at where exactly the error occurred, but a correct >> reinstallation should sort it out. >> > > I'm a litte familiar and I can say you (Scott) installed and 64 bit > version of CentOS and later installed some 32 bits packages and some how > shorewall is looking for 32bit iptables instead of 64 bits version.
Shorewall looks for $IPTABLES if that variable has been set in shorewall.conf. Otherwise, it uses $PATH as set in shorewall.conf. If neither is set, it uses a default $PATH (/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin) -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
