From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire meets Suricata - Call for tester
Date: Wed, 20 Feb 2019 08:19:41 +0100 [thread overview]
Message-ID: <b05929b902032400f9f7bd072c21c14ec0abbd4c.camel@ipfire.org> (raw)
In-Reply-To: <002401d4c8a0$2df74790$89e5d6b0$@net>
[-- Attachment #1: Type: text/plain, Size: 3462 bytes --]
Hello Wayne,
thanks for the positive feedback - I'm happy for you, that everything
is working fine now.
Best regards,
-Stefan
> Stefan
>
> Yep I had downloaded the nightly and suspected is was not current,
> and so posted the build number.
>
> With the 5d7d8749 loaded I have not seen any of the previous issues
> nor any others thus far.
>
> Regards
> Wayne
>
> -----Original Message-----
> From: Development [mailto:development-bounces(a)lists.ipfire.org] On
> Behalf Of Stefan Schantl
> Sent: Tuesday, February 19, 2019 5:34 AM
> To: development(a)lists.ipfire.org
> Subject: Re: IPFire meets Suricata - Call for tester
>
> Hello Wayne,
>
> it seems you accidentally downloaded and tested the wrong image.
>
> The latest one is 5d7d8749 were you downloaded one is an older
> release.
>
> Sadly the nightly build service and therefore the images are one day
> later than the upgrade tarballs....
>
> You simply can update to this release by using the RC3 tarball or
> download the available "5d7d8749" ISO.
>
> Best regards,
>
> -Stefan
> > Loaded the new iso, reports build 77c07352. Still having
> > connection
> > issues with suricata as soon as its activated where existing
> > connections would continue to work, no new connections were
> > possible.
> > Reboot results in no connection timeouts. Disable suricata,
> > reboot,
> > connections work.
> >
> > Any graphical data trend under Status tab reports errors and
> > remains
> > blank. Typically on new installs the trends at least show the
> > chart
> > even though data had not been collected.
> >
> > Configured options:
> > Geoip
> > Proxy on green and blue
> > URL filter
> > suricata on red/blue Running a number of emerging threats rule
> > sets.
> >
> > Regards
> > Wayne
> >
> >
> >
> > -----Original Message-----
> > From: Development [mailto:development-bounces(a)lists.ipfire.org] On
> > Behalf Of Stefan Schantl
> > Sent: Monday, February 18, 2019 7:16 AM
> > To: development(a)lists.ipfire.org
> > Subject: Re: IPFire meets Suricata - Call for tester
> >
> > Hello list,
> >
> > I've uploaded the third release candidate, which hopefully would
> > be
> > the last one.
> >
> > It fixes the issue that no traffic could be passed through the
> > firewall when suricata was running on some machines and no graphs
> > could be displayed anymore. Thanks to Wayne for reporting and
> > Michael
> > Tremer for testing and fixing.
> >
> > The new tarball (i586 for 32bit-systems, and x86_64) can be found
> > here:
> >
> > https://people.ipfire.org/~stevee/suricata/
> >
> > To start testing download the tarball and place it on your IPFire
> > system. Extract the tarball and launch the install (install.sh)
> > script.
> >
> > If you already have installed a previous test version or image,
> > with
> > the same steps as noted above you can update the the new version.
> >
> > As always, if you prefer a fresh installation, the latest image can
> > be
> > grabbed from here:
> >
> > https://nightly.ipfire.org/next-suricata/latest/x86_64/
> >
> > Direct link for downloading the ISO image:
> >
> > https://nightly.ipfire.org/next-suricata/latest/x86_64/ipfire-2.21.x86
> > _64-full-core128.iso
> >
> > Thanks for downloading and testing. There are no known bugs so far,
> > as
> > usual please file any bugs to our bugtracker (
> > https://bugzilla.ipfire.org) and share your feedback on the list.
> >
> > Best regards,
> >
> > -Stefan
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-20 7:19 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 19:43 Stefan Schantl
2018-12-11 20:53 ` Peter Müller
2018-12-12 20:54 ` Peter Müller
2018-12-16 20:28 ` Peter Müller
2018-12-17 14:21 ` Stefan Schantl
2018-12-17 17:05 ` Michael Tremer
2018-12-17 19:08 ` Stefan Schantl
2018-12-19 16:30 ` Michael Tremer
2018-12-20 13:03 ` Stefan Schantl
2018-12-20 14:05 ` Michael Tremer
2018-12-21 16:03 ` Tim FitzGeorge
2018-12-25 19:17 ` Stefan Schantl
2018-12-25 21:56 ` Michael Tremer
2018-12-25 19:03 ` Stefan Schantl
2019-01-01 13:32 ` Stefan Schantl
2019-01-02 15:54 ` Michael Tremer
2019-02-06 8:58 ` Stefan Schantl
2019-02-14 14:28 ` Stefan Schantl
2019-02-14 15:20 ` ummeegge
2019-02-14 18:01 ` Matthias Fischer
2019-02-14 21:49 ` Stefan Schantl
2019-02-14 23:16 ` Matthias Fischer
2019-02-14 23:36 ` Mentalic
2019-02-15 7:51 ` Stefan Schantl
2019-02-15 0:03 ` Mentalic
2019-02-15 7:54 ` Stefan Schantl
2019-02-17 11:58 ` Stefan Schantl
2019-02-17 12:59 ` Michael Tremer
2019-02-17 19:57 ` Stefan Schantl
2019-02-18 11:44 ` Michael Tremer
2019-02-18 13:09 ` Stefan Schantl
2019-03-03 11:37 ` ummeegge
2019-03-03 18:48 ` Stefan Schantl
2019-03-04 6:28 ` ummeegge
2019-02-18 13:16 ` Stefan Schantl
2019-02-18 22:11 ` Mentalic
2019-02-19 11:33 ` Stefan Schantl
2019-02-19 22:12 ` Mentalic
2019-02-19 23:22 ` Mentalic
2019-02-20 7:55 ` Stefan Schantl
2019-02-21 21:56 ` Mentalic
2019-02-22 10:21 ` Michael Tremer
2019-02-22 11:08 ` Stefan Schantl
2019-02-22 10:59 ` Stefan Schantl
2019-02-22 18:40 ` Mentalic
2019-02-20 7:19 ` Stefan Schantl [this message]
2019-03-03 14:39 ` Stefan Schantl
2019-03-03 17:33 ` Mentalic
2019-03-04 19:54 ` Mentalic
2019-03-05 9:31 ` Michael Tremer
[not found] <E1gf64O-0003zJ-Kt@smtprelay03.ispgateway.de>
2019-01-06 13:26 ` IPFire meets Suricata - Call for Tester Stefan Schantl
[not found] <79FF884C-B36B-42F5-A620-F2636E3706FC@gmail.com>
2019-02-06 9:57 ` IPFire meets Suricata - Call for tester Stefan Schantl
2019-02-06 10:43 ` Michael Tremer
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=b05929b902032400f9f7bd072c21c14ec0abbd4c.camel@ipfire.org \
--to=stefan.schantl@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