All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: IMQ
Date: Tue, 14 May 2002 10:24:23 +0000	[thread overview]
Message-ID: <marc-lartc-102137193602386@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102136425229085@msgid-missing>

Hi.

Odri Kornel wrote:
> Thank you for your quick answer.
> 
> My problem was that although imq is a device it is called via iptables like a 
> table just as snat. As far as I know if iptables finds a matching rule, it 
> jumps out of the chain, and does not process the other rules. Is this where I 
> made a mistake? I haven't found any description about this...

Yes this is not true. If a packet is not explicit dropped / accepted it 
continues traversal. Think about the MARK target, in fact the IMQ target 
is just a modified MARK target.
Also, the imq device is not called via iptables, iptables is just used 
for specifying that the current packet should pass through the imq 
device at a later point. The IMQ device feeds itself through netfilter 
hooks, so in theory you could f.e. mark all IPX/whatever packets 
somewhere during their processing and they would pass the imq device, too.

> So, youre saying, that the packet will be processed trough the other 
> postrouting rules after being marked by the mangle rule?
> 
> For ex.:
> 
> iptables -t mangle -A POSTROUTING -o eth0 -j IMQ
> iptables -t mangle -A POSTROUTING -o ipsec0 -j IMQ
> iptables -t nat -A POSTROUTING -j SNAT ...
> 
> This should work?

Yes.
Bye,
Patrick

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-05-14 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  8:16 [LARTC] Re: IMQ Patrick McHardy
2002-05-14 10:24 ` Patrick McHardy [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=marc-lartc-102137193602386@msgid-missing \
    --to=kaber@trash.net \
    --cc=lartc@vger.kernel.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.