From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Neutron Soutmun <neo.neutron@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.12 released
Date: Fri, 11 May 2012 23:58:05 +0100 [thread overview]
Message-ID: <4FAD997D.8060104@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205112138580.22653@blackhole.kfki.hu>
>> I don't suppose you are working on ways to include ipset targets in tc
>> by any chance, are you? *hopeful look*
>>
>
> Nothing required, all iptables targets are supported by tc.
>
I meant ipsets themselves. In other words, instead of:
tc filter add dev ifb0 protocol ip parent be:0 prio 10 u32 match ip src
10.1.1.1/24 match ip dst 10.2.1.1/24 match ip protocol 6 ...
to have ipset matching on src, destination, protocol etc instead of
specifying hard-coded values, like "10.1.1.1/24", "10.2.1.1/24" and
"protocol 6" in the above example.
To my knowledge, that isn't yet possible or have I missed something?
next prev parent reply other threads:[~2012-05-11 22:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 10:18 [ANNOUNCE] ipset 6.12 released Jozsef Kadlecsik
2012-05-10 10:39 ` Jan Engelhardt
2012-05-10 11:17 ` Jozsef Kadlecsik
2012-05-10 11:28 ` Jan Engelhardt
2012-05-10 11:41 ` Jozsef Kadlecsik
2012-05-10 12:12 ` Neutron Soutmun
2012-05-10 15:13 ` Neutron Soutmun
2012-05-10 15:27 ` Jozsef Kadlecsik
2012-05-10 15:52 ` Neutron Soutmun
2012-05-10 16:00 ` Neutron Soutmun
2012-05-10 16:28 ` Neutron Soutmun
2012-05-10 22:00 ` Mr Dash Four
2012-05-11 2:37 ` Neutron Soutmun
2012-05-11 12:45 ` Mr Dash Four
2012-05-11 19:40 ` Jozsef Kadlecsik
2012-05-11 22:58 ` Mr Dash Four [this message]
2012-05-11 23:06 ` Jan Engelhardt
2012-05-11 23:20 ` Mr Dash Four
2012-05-11 8:40 ` Jozsef Kadlecsik
2012-05-11 9:00 ` Neutron Soutmun
2012-05-10 14:24 ` Mr Dash Four
2012-05-10 14:30 ` Jozsef Kadlecsik
2012-05-10 15:45 ` Mr Dash Four
2012-05-11 6:09 ` Andreas Herz
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=4FAD997D.8060104@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=neo.neutron@gmail.com \
--cc=netfilter-devel@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.