From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Suricata core130 Date: Mon, 01 Apr 2019 10:49:01 +0100 Message-ID: <6A916025-05B5-4345-A5E4-67CAD72AA032@ipfire.org> In-Reply-To: <000401d4e841$8781dc60$96859520$@net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1950437017564358525==" List-Id: --===============1950437017564358525== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 Ste= fan so that he can have a look. When a backup is being restored, there is a script called =E2=80=9Cconvert-sn= ort=E2=80=9D that is being run. Could you run that manually and see if that r= eports any errors? I guess that the problem is there=E2=80=A6 Best, -Michael > On 1 Apr 2019, at 05:15, Mentalic wrote: >=20 > 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 l= oading but restoring backup from version 129 results in the IPS service no lo= nger running. Tried a number of things, rebooting, stop/start IPS with no luc= k. =20 > =20 > Backup up contains: > -Geoip groups > -Geoip Blocking > -Snort oinkcode but IDS is not enabled. > -Web Proxy disabled > -18 firewall rules several using Geoip groups. > =20 > Thanks and Regards > Wayne --===============1950437017564358525==--