From: "Gilad Benjamini" <gilad.benjamini@gmail.com>
To: 'Colin Davis' <col@colsmemory.co.uk>, netfilter@vger.kernel.org
Subject: RE: iptables - how to create a rule that expires automatically
Date: Thu, 19 Feb 2009 09:48:48 -0800 [thread overview]
Message-ID: <499d9b99.20018e0a.361e.4b2b@mx.google.com> (raw)
In-Reply-To: <499D9292.902@colsmemory.co.uk>
A script, possibly with crontab or at, is your best bet.
For some scenarios it might be easier to use the "condition" match, and have
your script change the proc value rather than the actual chain.
> -----Original Message-----
> From: netfilter-owner@vger.kernel.org [mailto:netfilter-
> owner@vger.kernel.org] On Behalf Of Colin Davis
> Sent: Thursday, February 19, 2009 9:11 AM
> To: netfilter@vger.kernel.org
> Subject: iptables - how to create a rule that expires automatically
>
>
> Hi,
>
> Not sure if this is possible. I wish to create a rule that once created
> will
> automatically expire (and be removed) after say 10 minutes.
>
> Please
>
> Many thanks,
> Colin.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-19 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 17:10 iptables - how to create a rule that expires automatically Colin Davis
2009-02-19 17:32 ` Simon Gray
2009-02-19 17:36 ` Ivan Petrushev
2009-02-19 17:42 ` Colin Davis
2009-02-19 17:56 ` Peter Renzland
2009-02-19 18:14 ` Colin Davis
2009-02-19 18:15 ` Peter Renzland
2009-02-19 18:17 ` Ivan Petrushev
2009-02-19 18:18 ` Gilad Benjamini
2009-02-19 17:48 ` Gilad Benjamini [this message]
2009-02-19 18:36 ` G.W. Haywood
2009-02-20 9:01 ` Mart Frauenlob
2009-02-20 9:16 ` Michael Schwartzkopff
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=499d9b99.20018e0a.361e.4b2b@mx.google.com \
--to=gilad.benjamini@gmail.com \
--cc=col@colsmemory.co.uk \
--cc=netfilter@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