From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwhits graphs ( addendum )
Date: Tue, 03 May 2022 12:50:17 +0100 [thread overview]
Message-ID: <E211C261-3A22-491E-AB02-5ADAFAB96CE9@ipfire.org> (raw)
In-Reply-To: <03b658d2-019c-2c84-3963-527cc5b35189@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
Hello,
Is there a patch for this?
-Michael
> On 4 Apr 2022, at 15:38, Bernhard Bitsch <bbitsch(a)ipfire.org> wrote:
>
>
> I've added the CTINVALID events of the firewall. Maybe be of interest also.
> The color doeasn't mean anything. Just tried the numbers until the data were easily visible. ;)
>
> -Bernhard
>
prev parent reply other threads:[~2022-05-03 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65e70c14-f1e2-3f5d-6a84-de6124693d3a@ipfire.org>
2022-04-04 14:38 ` Bernhard Bitsch
2022-05-03 11:50 ` Michael Tremer [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=E211C261-3A22-491E-AB02-5ADAFAB96CE9@ipfire.org \
--to=michael.tremer@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