From: Michelle Konzack <linux4michelle@freenet.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: ULOG: invalid argument
Date: Thu, 26 Feb 2004 02:40:18 +0100 [thread overview]
Message-ID: <20040226014018.GH27875@freenet.de> (raw)
In-Reply-To: <LAW12-F18Uhyx9w8OjU000276ef@hotmail.com>
Am 2004-02-19 20:46:12, schrieb T. Take:
>I cannot use "ULOG".
>
>#iptables -A INPUT -i $OUTER_PORT -s $INNER_IP -j ULOG --ulog-nlgroup 32
>--ulog-prefix "spoofed packet "
>#iptables: Invalid argument
>
>Although I updated iptables to version 1.2.9 and installed ulogd by apt-get
>install (Debian), I have not used ULOG yet. And there is ipt_ULOG.o in
>"/lib/modules/2.4.24/kernel/net/ipv4/netfilter".
>
>Did you have the same problem about ULOG?
>I hope your advises.
I had he same problem...
It is NOT an iptables problem/bug !!!
It is the ULOG Package from WOODY !!!
It is too old. put the source from unstable
in your /etc/apt/sources.list like
deb-src ftp://ftp.debian.org/debian unstable main
Then make a
apt-get build-dep ulogd
and last not least a
apt-get -b source ulogd
It will compile automaticly and install ist.
Have fun with 'iptables' and 'ulogd'
Greetings
Michelle
--
Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/
next prev parent reply other threads:[~2004-02-26 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 11:46 ULOG: invalid argument T. Take
2004-02-19 18:38 ` William Stearns
2004-02-26 1:40 ` Michelle Konzack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 5:53 T. Take
2004-02-20 14:16 ` William Stearns
2004-02-22 6:28 T. Take
2004-03-05 9:53 T. Take
2004-03-05 10:01 ` Jozsef Kadlecsik
2004-03-05 17:44 ` Michelle Konzack
2004-03-05 17:51 ` Jozsef Kadlecsik
2004-03-05 18:14 ` Michelle Konzack
2004-03-05 19:30 ` Jozsef Kadlecsik
2004-03-06 10:25 T. Take
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=20040226014018.GH27875@freenet.de \
--to=linux4michelle@freenet.de \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox