Shorewall users - Nov 2007 - [SOLVED] Re: Limit Rule, Recent Match support, & shorewall upgrade

This is what you said Tom Eastep
> Scott Ruckh wrote:
>>
>> $ sudo iptables -N foo
>> $ sudo iptables -A foo -m recent --update -j ACCEPT
>>
>> iptables v1.3.5: Couldn''t load match
>> `recent'':/usr/lib/iptables/libipt_recent.so: cannot open
shared object
>> file: No such file or directory
>>
>> Try `iptables -h'' or ''iptables --help'' for
more information.
>>
>> $ sudo locate libipt_recent.so
>> /usr/local/lib/iptables/libipt_recent.so
>> /lib64/iptables/libipt_recent.so
>>
>> /lib64/iptables/libipt_recent.so is from vendor supplied iptables
>> (iptables-1.2.11-3.1.RHEL4).
>>
>> /usr/local/lib/iptables/libipt_recent.so I would assume from version
>> 1.3.5
>> which I compiled some time back.
>>
>> Obviously, neither of them in the location where iptables is looking.
>
> Looks like you need to clean up such that you have a single consistent
> copy
> of iptables and its libraries installed.
>
> -Tom
That is definitely the way it appears.  For the short-haul I have just
created a symbolic link to the /usr/local/lib/iptables directory and that
appears to have worked.

When I get some time I will work on getting this cleaned up as not to have
similar problems.

Thanks for your help!! (and quick response as always).

-------------------------------------------------------------------------
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

On Wed, Nov 28, 2007 at 04:54:21PM -0700, Scott Ruckh
wrote:
> That is definitely the way it appears.  For the short-haul I have just
> created a symbolic link to the /usr/local/lib/iptables directory and that
> appears to have worked.
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.

-------------------------------------------------------------------------
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

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.


-------------------------------------------------------------------------
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

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  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key



-------------------------------------------------------------------------
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