public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Fwd: IPS configuration recommendations for IPFire users
Date: Tue, 10 Nov 2020 08:39:13 +0100	[thread overview]
Message-ID: <3242c3c9-fa40-b440-8202-07946aeac564@ipfire.org> (raw)
In-Reply-To: <02e65bad-9fb4-514e-ac4a-bb573e11a754@ipfire.org>

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


Hi all,

Peter Müller wrote another great blog article 
https://blog.ipfire.org/post/ips-configuration-recommendations-for-ipfire-users.

Thank you for that.

After reading this one and looking into my IPS logs I had an idea and I 
would like to hear your opinion about it.
If I have activated IPS not only on Red but also on other zones, 
wouldn't it make sense to be able to split the IPS logs to see faster / 
easier what happened in which zone?
Is this even possible with reasonable effort?

-

Daniel


           reply	other threads:[~2020-11-10  7:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <02e65bad-9fb4-514e-ac4a-bb573e11a754@ipfire.org>]

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=3242c3c9-fa40-b440-8202-07946aeac564@ipfire.org \
    --to=daniel.weismueller@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