I did again something stupid, as rewrap was used, then probably a ^Z for
some other reason undone that. Re-sending a wrapped message (I hope)
This has been happening for some time, but only noticed last week and
happens either with iptables-1.4.13 or with the new version
iptables-1.4.14, just installed after being notified by Bruce in the
"book" list.
The following appears at boot or starting iptables:
# /etc/rc.d/init.d/iptables start
Starting iptables...FATAL: Module ipt_LOG not found.
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
In /etc/rc.d/rc.iptables I have identified the following lines as
sources of the error messages (by commenting out)
modprobe ipt_LOG
iptables -A INPUT -j LOG --log-prefix "FIREWALL:INPUT "
iptables -I INPUT -p tcp -m state --state INVALID \
-j LOG --log-prefix "FIREWALL:INVALID"
I understand the first error message having no ipt_LOG module:
$ grep -i ipt /boot/config-3.4.0
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP6_NF_IPTABLES=y
# CONFIG_NET_ACT_IPT is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_SND_RIPTIDE is not set
# iptables trigger is under Netfilter config (LED target)
I understand the other error messages as consequence of something
necessary, perhaps ipt_LOG.
Other than commenting out the offending lines, what can be done to
correct this?
Help would be much appreciated.
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
