From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@lists.netfilter.org>
Subject: Re: xt_request_find_match
Date: Tue, 09 Jan 2007 11:44:33 +0100 [thread overview]
Message-ID: <45A37211.2010000@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0612232254110.10087@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> On Dec 20 2006 10:17, Patrick McHardy wrote:
>
>>Jan Engelhardt wrote:
>>
>>>>Make sure the user specifies the match on the command line before
>>>>your match. Look at the TCPMSS or REJECT targets for examples for
>>>>this.
>>>
>>>That would mean I'd have to
>>>
>>> -p tcp -m multiport --dport 1,2,3,4 -m time --time sundays -m
>>>lotsofothers -j TARGET
>>> -p udp -m multiport --dport 1,2,3,4 -m time --time sundays -m
>>>lotsofothers -j TARGET
>>
>>I don't see any match that would depend on an other match in
>>your example. How about your start explaining what you would
>>like to do, ideally with some code.
>
>
> Yup, on the spot!
> http://jengelh.hopto.org/f/chaostables/chaostables-0.1.tar.bz2
> (Contains a target, but still something that could use
> xt_request_find_module.)
That looks a bit silly, you combine matches and targets through
code instead of through the ruleset.
/* Equivalent to
-A chaos -m random --average 1 -j REJECT --reject-with
host-unreach
-A chaos -p tcp -j TARPIT
-A chaos -j DROP
*/
Just do that ..
next prev parent reply other threads:[~2007-01-09 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 17:55 [PATCH] xt_request_find_match Jan Engelhardt
2006-12-19 11:51 ` Patrick McHardy
2006-12-19 13:07 ` Jan Engelhardt
2006-12-19 13:28 ` Patrick McHardy
2006-12-19 15:27 ` Jan Engelhardt
2006-12-20 8:16 ` Patrick McHardy
2006-12-20 9:11 ` Jan Engelhardt
2006-12-20 9:17 ` Patrick McHardy
2006-12-23 21:57 ` xt_request_find_match Jan Engelhardt
2007-01-09 10:44 ` Patrick McHardy [this message]
2007-01-09 21:44 ` xt_request_find_match Jan Engelhardt
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=45A37211.2010000@trash.net \
--to=kaber@trash.net \
--cc=jengelh@linux01.gwdg.de \
--cc=netfilter-devel@lists.netfilter.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.