Re: ipmasq not doing NAT after upgrade

["Mihalis I. Tsoukalos" <mtsouk@freemail.gr>]

On Wed, Sep 24, 2003 at 11:24:57PM +0100, Pigeon wrote:
> On Wed, Sep 24, 2003 at 10:32:30AM +0300, Mihalis I. Tsoukalos wrote:
> > After a kernel recompile the NAT problem is fixed.
> > I have added some modules to the kernel.
> > 
> > I still get some "iptables: No chain/target/match by that name" error
> > messages:
> > 
> > /sbin/iptables -A INPUT -j LOG -i ! lo -s 127.0.0.1/255.0.0.0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A INPUT -j LOG -i ppp0 -s 10.100.0.1/255.255.0.0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A FORWARD -j LOG -o ppp0 -d 10.100.0.1/255.255.0.0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A OUTPUT -j LOG -o ppp0 -d 10.100.0.1/255.255.0.0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A INPUT -j LOG -s 0.0.0.0/0 -d 0.0.0.0/0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A OUTPUT -j LOG -s 0.0.0.0/0 -d 0.0.0.0/0
> > iptables: No chain/target/match by that name
> > /sbin/iptables -A FORWARD -j LOG -s 0.0.0.0/0 -d 0.0.0.0/0
> > iptables: No chain/target/match by that name
> > 
> > What can I do to fix this?
> 
> modprobe ipt_LOG perhaps? (I'm no iptables expert, but...)

That was it.
It was not compiled at all. It is now a module.

Many thanks.
have a nice day,
Mihalis

-- 
 13:31:48 up 1 day,  3:10,  2 users,  load average: 0.99, 0.55, 0.24