Linux Netfilter discussions
 help / color / mirror / Atom feed
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 15:03:15 +0100	[thread overview]
Message-ID: <20021126140315.GA12281@gnjilux.srk.fer.hr> (raw)
In-Reply-To: <200211260853.46333.netfilter@newkirk.us>

On Tue, Nov 26, 2002 at 08:53:46AM -0500, Joel Newkirk wrote:
> > >
> > > Does the ULOG target work in other uses, IE "iptables -A FORWARD -j ULOG"
> > > ?
> >
> > Nope, it gives same error:
> >
> > $ iptables -A FORWARD -j ULOG -p tcp -m state --state NEW
> > iptables v1.2.6a: You must specify `--state'
> >
> > with INPUT and OUTPUT, also same thing. I'm not doing anything special
> > (like NAT, conntrack, ftp, ...), just plain INPUT filtering.
> 
> Well, did you try the example I asked about?  I suspect not, because the 

Oh, I thought that you were referring to other chains...

> problem here seems to be that "-j ULOG" should be AFTER the state matching 
> part of the rule...  If I enter the line you used, I get the same '--state' 
> error, but if I put the target after the match (or remove the match, as per 
> my debugging suggestion above) it does NOT.

When using reversed order (first state, then ULOG) it works fine, thanks
for resolving this.

-- 
@


  reply	other threads:[~2002-11-26 14:03 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 [this message]
2002-11-26 19:49         ` Still an IPTABLES newbie Bob Avery-Babel
2002-11-26 21:18           ` Dan Egli
2002-11-26 11:34   ` ULOG with -m state Iva Cabric Cabric

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=20021126140315.GA12281@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