From: Mentalic <mentalic@cox.net>
To: development@lists.ipfire.org
Subject: RE: Suricata core130
Date: Mon, 01 Apr 2019 08:43:55 -0500 [thread overview]
Message-ID: <000b01d4e890$f3682390$da386ab0$@net> (raw)
In-Reply-To: <6A916025-05B5-4345-A5E4-67CAD72AA032@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Hello Michael
Created a bug report on this issue.
Ran the convert-snort script which reports:
/var/ipfire/snort/settings not found - Nothing to do. Exiting!
Regards
Wayne
-----Original Message-----
From: Michael Tremer [mailto:michael.tremer(a)ipfire.org]
Sent: Monday, April 01, 2019 4:49 AM
To: Mentalic
Cc: IPFire: Development-List; Stefan Schantl
Subject: Re: Suricata core130
Hello Wayne,
Thank you very much for your feedback!
I am very excited to have the new IPS released, but it looks like there are a couple of bumps in the road that we have to sort out.
Could you please open a bug report for me for this? I will assign this to Stefan so that he can have a look.
When a backup is being restored, there is a script called “convert-snort” that is being run. Could you run that manually and see if that reports any errors? I guess that the problem is there…
Best,
-Michael
> On 1 Apr 2019, at 05:15, Mentalic <mentalic(a)cox.net> wrote:
>
> Loaded the nightly build of 130 and then managed to break IPS every time I restore a backup to the machine. Tried several rebuilds, off line or online loading but restoring backup from version 129 results in the IPS service no longer running. Tried a number of things, rebooting, stop/start IPS with no luck.
>
> Backup up contains:
> -Geoip groups
> -Geoip Blocking
> -Snort oinkcode but IDS is not enabled.
> -Web Proxy disabled
> -18 firewall rules several using Geoip groups.
>
> Thanks and Regards
> Wayne
prev parent reply other threads:[~2019-04-01 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000401d4e841$8781dc60$96859520$@net>
2019-04-01 9:49 ` Michael Tremer
2019-04-01 13:43 ` Mentalic [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='000b01d4e890$f3682390$da386ab0$@net' \
--to=mentalic@cox.net \
--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