From: Phil Oester <kernel@linuxace.com>
To: Paul Kosinski <prk@iment.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Throttling by 'limit' in one chain fails whenever a *different* chain is modified
Date: Tue, 28 Dec 2004 12:59:51 -0800 [thread overview]
Message-ID: <20041228205951.GA7990@linuxace.com> (raw)
In-Reply-To: <041228124435.278000@ime1.iment.com>
On Tue, Dec 28, 2004 at 12:44:34PM -0500, Paul Kosinski wrote:
> [Posting this to the general list got no response since Dec 15, so I'll try the developer list.]
Did you search the archives prior to posting? That is generally
considered to be a good idea (as is wrapping lines at 80 characters).
> The problem I experience is that whenever the dynamic-rule script fires, I get a log entry for an established-tunnel packet. Since the first script fires N times per hour, I get N times as many log entries for the tunnel as I want. This makes my examination of the firewall log more tedious and error prone than it should be.
Please see this thread:
https://lists.netfilter.org/pipermail/netfilter-devel/2004-September/016826.html
Phil
next prev parent reply other threads:[~2004-12-28 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 17:44 Throttling by 'limit' in one chain fails whenever a *different* chain is modified Paul Kosinski
2004-12-28 20:59 ` Phil Oester [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 23:44 Paul Kosinski
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=20041228205951.GA7990@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=prk@iment.com \
/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.