From: syrius.ml@no-log.org
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CLASSIFY target documentation
Date: Tue, 20 Apr 2004 00:39:14 +0000 [thread overview]
Message-ID: <wazza.87hdvfa3f1.fsf@message.id> (raw)
In-Reply-To: <h5f880p4fgoqad9447g81askndc0hofom4@4ax.com>
Myrddin Emrys <techmert@dotnet.com> writes:
[...]
> I need to classify packets into PRIO queues based on iptables rules. I
> am currently setting MARKs during classification. Unfortunately, if I
> understand correctly u32 cannot see marks because they're not in the
> packet, so my next obvious solution is to skip MARKing them and just
> CLASSIFY them...
[...]
the only documentation i know about classify is provided by
patch-o-matic.
You may prefer to use "handle $mark fw" as a filter to match netfilter
marks.
Or depending on your needs, you may only want to use u32 without
netfilter marks.
As you probably know there's a howto on http://lartc.org
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-04-20 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 21:52 [LARTC] CLASSIFY target documentation Myrddin Emrys
2004-04-20 0:39 ` syrius.ml [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=wazza.87hdvfa3f1.fsf@message.id \
--to=syrius.ml@no-log.org \
--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.