From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Newkirk Subject: Re: ULOG with -m state Date: Sun, 24 Nov 2002 19:45:38 -0500 Sender: netfilter-admin@lists.netfilter.org Message-ID: <200211241945.38762.netfilter@newkirk.us> References: <20021122155352.GA5665@gnjilux.srk.fer.hr> Reply-To: netfilter@newkirk.us Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20021122155352.GA5665@gnjilux.srk.fer.hr> Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: Iva Cabric Cabric , netfilter@lists.netfilter.org On Friday 22 November 2002 10:53 am, Iva "Cabric" Cabric wrote: > Hello, > I have found a bug in iptables when "-j ULOG" and "-m state" are > used together, for example: > > $ iptables -A ssh -j ULOG -p tcp -m state --state NEW > > reports: > > iptables v1.2.6a: You must specify `--state' > Try `iptables -h' or 'iptables --help' for more information. > > but using DROP works fine: > > $ iptables -A ssh -j DROP -p tcp -m state --state NEW Does the ULOG target work in other uses, IE "iptables -A FORWARD -j ULOG"= ? j