All of lore.kernel.org
 help / color / mirror / Atom feed
From: Worik <worik@noggon.co.nz>
To: netfilter@lists.netfilter.org
Subject: MASQUERADE and QUEUE target.  Can they be used together?
Date: 27 Apr 2003 14:28:20 +1200	[thread overview]
Message-ID: <1051410500.29656.66.camel@stolberg> (raw)

Friends

I have about a weeks experience now with iptables, and am having a ball
with it.  But I have run into a brick wall.

I am using a MASQUERADE target for machines on my lan.

I want to pipe all packets that are masqueraded through  my user space
process.

So my rules are...

 iptables -t nat -L POSTROUTING
Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
MASQUERADE  all  --  anywhere             anywhere           
QUEUE      all  --  192.168.0.0/24       anywhere           


Problem is that I the QUEUE never sees the packets.  But nowhaere in the
docs that I can find does it state that if a MASQUERADE target is
matched does processing in the chain stop.

Am I missing something?

My user space Queue process (using libipq) works, but I can only ACCEPT
(NF_ACCEPT) or DROP (NF_DROP via ipq_set_verdict()) packets, both of
which *do* stop processing in the chain, so reversing the order of the
rules will not work.

Questions:

Does a match on a rule with a MASQUERADE target stop processing in the
chain?

(If so) does a match on *any* rule stop processing in the chain?  LOG
doesn't, so the answer must be no.

Should I be using ULOG?  I am having difficulty tracking down any
documentation on ulogd (I have installed it from a Debian package, but
there is no indication of how to get data out of it.  I have a ULOG
target and there is nothing in  /var/log/ulogd*)








                 reply	other threads:[~2003-04-27  2:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1051410500.29656.66.camel@stolberg \
    --to=worik@noggon.co.nz \
    --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 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.