From: "pupilla@libero.it" <pupilla@libero.it>
To: netdev@vger.kernel.org
Subject: routing policy based on u32 classifier
Date: Wed, 1 Feb 2017 11:34:04 +0100 (CET) [thread overview]
Message-ID: <1326989143.11056951485945244609.JavaMail.httpd@webmail-35.iol.local> (raw)
Hello everyone,
Kindly I would like to ask if there is a way to do routing
policy based on u32 classifier without fwmark/netfilter.
I have read doc/tc-filters and doc/actions/actions-general
from iproute2-4.9.0 package but I am not able to find any
actions doing this kind of job: the only way is to mark
packets with netfilter.
Any response are welcome
TIA
Marco
next reply other threads:[~2017-02-01 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 10:34 pupilla [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-10 9:22 routing policy based on u32 classifier Marco Berizzi
2007-12-10 14:57 ` Brian S Julin
2007-12-10 15:20 ` Marco Berizzi
[not found] ` <5A630F46702DD1498FFD48394B4A664C347275DE@john.ad.clarku.edu>
2007-12-10 16:09 ` Marco Berizzi
[not found] ` <5A630F46702DD1498FFD48394B4A664C347275E0@john.ad.clarku.edu>
2007-12-11 11:11 ` Marco Berizzi
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=1326989143.11056951485945244609.JavaMail.httpd@webmail-35.iol.local \
--to=pupilla@libero.it \
--cc=netdev@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