From: "U.Mutlu" <for-gmane@mutluit.com>
To: netfilter@vger.kernel.org
Subject: LOG target missing
Date: Tue, 18 Sep 2012 19:23:54 +0200 [thread overview]
Message-ID: <k3aan9$n75$1@ger.gmane.org> (raw)
Hi,
on a newly setup system I can't find iptables LOG target, neither ipt_LOG nor xt_LOG nor nf_LOG is present.
Has the module name changed, or what's the reason it's not found anymore?
REJECT target is present.
(I just wonder: ACCEPT, REJECT, and LOG are basic, IMHO mandatory, targets,
why not make them built-in into iptables core?)
System:
#uname -a
Linux c22 3.5.0-rc5-my1a #1 SMP Tue Jul 3 04:01:33 CEST 2012 x86_64 GNU/Linux
# iptables --version
iptables v1.4.14
root@c22:/sys/module# lsmod | grep -i ipt
ipt_REJECT 2014 45
iptable_mangle 1424 1
iptable_nat 3432 0
nf_nat 12237 1 iptable_nat
nf_conntrack_ipv4 9816 37 nf_nat,iptable_nat
nf_conntrack 47391 4 nf_nat,xt_state,iptable_nat,nf_conntrack_ipv4
iptable_filter 1312 1
ip_tables 13877 3 iptable_filter,iptable_mangle,iptable_nat
x_tables 14052 9
ip_tables,xt_tcpudp,xt_string,xt_limit,xt_state,iptable_filter,ipt_REJECT,iptable_mangle,iptable_nat
root@c22:/sys/module# lsmod | grep -i xt
xt_string 1203 1
xt_limit 1726 0
xt_state 1151 34
xt_tcpudp 2258 80
nf_conntrack 47391 4 nf_nat,xt_state,iptable_nat,nf_conntrack_ipv4
x_tables 14052 9
ip_tables,xt_tcpudp,xt_string,xt_limit,xt_state,iptable_filter,ipt_REJECT,iptable_mangle,iptable_nat
root@c22:/sys/module# lsmod | grep -i nf
nf_nat 12237 1 iptable_nat
nf_conntrack_ipv4 9816 37 nf_nat,iptable_nat
nf_defrag_ipv4 1179 1 nf_conntrack_ipv4
nf_conntrack 47391 4 nf_nat,xt_state,iptable_nat,nf_conntrack_ipv4
next reply other threads:[~2012-09-18 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 17:23 U.Mutlu [this message]
2012-09-18 20:16 ` LOG target missing U.Mutlu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='k3aan9$n75$1@ger.gmane.org' \
--to=for-gmane@mutluit.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.