public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] collectd.conf: Change chain from HOSTILE to HOSTILE_DROP - fixes bug#12838
Date: Tue, 05 Apr 2022 13:16:38 +0200	[thread overview]
Message-ID: <6334140a-4431-d58c-6ee0-9f2ac2ae4cae@ipfire.org> (raw)
In-Reply-To: <20220404203331.3612132-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

Reviewed-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
Acked-by: Bernhard Bitsch <bbitsch(a)ipfire.org>

Am 04.04.2022 um 22:33 schrieb Adolf Belka:
> From: Bernhard Bitsch <bbitsch(a)ipfire.org>
> 
> - Chain that was specified was HOSTILE but actual used is HOSTILE_DROP
> - Using HOSTILE caused no update fro the hostile data used in the Firewall Hits graph
> 
> Fixes: bug#12838
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>   config/collectd/collectd.conf | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config/collectd/collectd.conf b/config/collectd/collectd.conf
> index 2a0237100..e34a97da1 100644
> --- a/config/collectd/collectd.conf
> +++ b/config/collectd/collectd.conf
> @@ -52,7 +52,7 @@ include "/etc/collectd.precache"
>   	Chain filter POLICYOUT DROP_OUTPUT
>   	Chain filter POLICYIN DROP_INPUT
>   	Chain filter SPOOFED_MARTIAN DROP_SPOOFED_MARTIAN
> -	Chain filter HOSTILE DROP_HOSTILE
> +	Chain filter HOSTILE_DROP DROP_HOSTILE
>   </Plugin>
>   
>   #<Plugin logfile>

      parent reply	other threads:[~2022-04-05 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 20:33 Adolf Belka
2022-04-04 20:33 ` [PATCH 2/2] graphs.pl: Change directory name to replace HOSTILE with " Adolf Belka
2022-04-05 11:18   ` Bernhard Bitsch
2022-04-05 11:16 ` Bernhard Bitsch [this message]

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=6334140a-4431-d58c-6ee0-9f2ac2ae4cae@ipfire.org \
    --to=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.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