From: Iva "Cabric" Cabric <ivac@gnjilux.srk.fer.hr>
To: Joel Newkirk <netfilter@newkirk.us>
Cc: netfilter@lists.netfilter.org
Subject: Re: ULOG with -m state
Date: Tue, 26 Nov 2002 12:34:34 +0100 [thread overview]
Message-ID: <20021126113434.GC9457@gnjilux.srk.fer.hr> (raw)
In-Reply-To: <200211241945.38762.netfilter@newkirk.us>
More update,....
I have put new iptables version (1.2.7a-7 from Debian), and no
change:
$ iptables -A INPUT -j ULOG -p tcp -m state --state NEW
iptables v1.2.7a: You must specify `--state'
Try `iptables -h' or 'iptables --help' for more information.
also it looks that ULOG is not working at all:
Chain INPUT (policy ACCEPT 128K packets, 77M bytes)
pkts bytes target prot opt in out source destination
5065 374K ACCEPT all -- * * xxx.xxx.xxx.xxx/19 xxx.xxx.xxx.xxx
0 0 ACCEPT all -- * * xxx.xxx.xxx.xxx/18 xxx.xxx.xxx.xxx
4022 338K ULOG all -- * * 0.0.0.0/0 0.0.0.0/0 ULOG copy_range 0 nlgroup 1 prefix `INPUT:DROP' queue_threshold 1
12630 1061K ULOG all -- * * 0.0.0.0/0 0.0.0.0/0 ULOG copy_range 0 nlgroup 1 prefix `INPUT:DROP' queue_threshold 50
12630 1061K DROP all -- * * 0.0.0.0/0 0.0.0.0/0
kernel is matching packets but ulogd doesnt produce any output in log
files. I have tried to strace ulogd but it just waits in "recvfrom(6,",
and according to lsof descriptor 6 is:
ulogd 21070 root 6u sock 0,0 322745 can't identify protocol
Any help appreciated.
--
@
prev parent reply other threads:[~2002-11-26 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 15:53 ULOG with -m state Iva Cabric Cabric
2002-11-25 0:45 ` Joel Newkirk
2002-11-25 8:16 ` Iva Cabric Cabric
2002-11-26 10:54 ` Iva Cabric Cabric
2002-11-26 13:53 ` Joel Newkirk
2002-11-26 14:03 ` Iva Cabric Cabric
2002-11-26 19:49 ` Still an IPTABLES newbie Bob Avery-Babel
2002-11-26 21:18 ` Dan Egli
2002-11-26 11:34 ` Iva Cabric Cabric [this message]
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=20021126113434.GC9457@gnjilux.srk.fer.hr \
--to=ivac@gnjilux.srk.fer.hr \
--cc=netfilter@lists.netfilter.org \
--cc=netfilter@newkirk.us \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox