From: Matthias Fischer <matthias.fischer@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>,
"IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Fwd: Advance Notification of Suricata 7.0.10
Date: Mon, 24 Mar 2025 23:50:19 +0100 [thread overview]
Message-ID: <cb5e7583-1860-4438-acc9-9aa673f133a4@ipfire.org> (raw)
In-Reply-To: <62541C60-39E7-4E13-BC17-F647A1BF39F7@ipfire.org>
Yep. I'll pick it up.
On 24.03.2025 19:07, Michael Tremer wrote:
> @Matthias: Are you free tomorrow to pick this one up?
>
>> Begin forwarded message:
>>
>> From: Jason Ish <jish@oisf.net>
>> Subject: Advance Notification of Suricata 7.0.10
>> Date: 24 March 2025 at 16:12:12 GMT
>> To: Jason Ish <jish@oisf.net>, Victor Julien <vjulien@oisf.net>
>>
>> Hello everyone,
>>
>> Last Tuesday, March 18, we released Suricata 7.0.9 which unfortunately contained an AF_PACKET regression affecting many users.
>>
>> If your configuration used a BPF filter and did not also tune the “default-packet-size” configuration parameter, Suricata would fail to start. A workaround is to set the “default-packet-size” to the default of 1514. This issue is tracked in the following ticket: https://redmine.openinfosecfoundation.org/issues/7618
>>
>> Suricata 7.0.10 will be released tomorrow, Tuesday, March 25 to address this issue.
>>
>> Sorry for the inconvenience.
>>
>> Regards,
>> The OISF Team
>>
>>
>> To unsubscribe from this group and stop receiving emails from it, send an email to oss-advisories+unsubscribe@openinfosecfoundation.org <mailto:oss-advisories+unsubscribe@openinfosecfoundation.org>.
>
>
prev parent reply other threads:[~2025-03-24 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMYRET9hs1M7d97FgsFEWS4XhoKjyyPyJOF20GBMZcRJ_FAtmg@mail.gmail.com>
2025-03-24 18:07 ` Michael Tremer
2025-03-24 22:50 ` Matthias Fischer [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=cb5e7583-1860-4438-acc9-9aa673f133a4@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@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