From: Nikolai Lusan <nikolai@lusan.id.au>
To: netfilter@vger.kernel.org
Subject: Multiple mangling
Date: Tue, 12 Nov 2013 06:45:54 +1000 [thread overview]
Message-ID: <1384202754.19072.44.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Greetings all,
I am at the point in writing my "new and improved"(tm) firewall where I
am adding QoS. I am marking the packets in the MANGLE table with DSCP
values, but I also want to mark packets again so that my iproute2 qdiscs
can have an easier time handling them. This requires that I mark the
packets twice (i.e. once with "-j DSCP --set-dscp-class AF32", and again
with "-j MARK --set-mark 6").
The question is: can I do this with consecutive rules in the MANGLE
table? What is the behaviour once a packet has matched a rule in one of
the MANGLE table chains? Does it continue to drop through? Does it
effect a RETURN?
Thanks in advance.
--
Nikolai Lusan <nikolai@lusan.id.au>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-11-11 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 20:45 Nikolai Lusan [this message]
2013-11-13 16:07 ` Multiple mangling Humberto Jucá
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=1384202754.19072.44.camel@localhost \
--to=nikolai@lusan.id.au \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox