From: Dash Four <mr.dash.four@googlemail.com>
To: lartc@vger.kernel.org
Subject: Re: ipset-based routing
Date: Sun, 28 Apr 2013 13:20:13 +0000 [thread overview]
Message-ID: <517D220D.9000300@googlemail.com> (raw)
In-Reply-To: <517C3065.9060901@googlemail.com>
Remy Mudingay wrote:
> Hi Dash,
>
> This has already been integrated with iproute2. TC (traffic control)
> can now match IPsets through the ematch classifier.
> There are a few examples around including documentation provided in
> the iproute2 source package.
> TC support was added in Kernel versions 3.7.
I am aware of all that since I was involved in testing this feature
before it became main stream. My question was about using ipsets in
routing, not traffic shaping.
next prev parent reply other threads:[~2013-04-28 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 20:09 ipset-based routing Dash Four
2013-04-28 10:21 ` Remy Mudingay
2013-04-28 13:20 ` Dash Four [this message]
2013-04-28 13:20 ` Dash Four
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=517D220D.9000300@googlemail.com \
--to=mr.dash.four@googlemail.com \
--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.