https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236819
Bug ID: 236819
Summary: [tcpdump] capsicum-related changes broke reading IPsec
ESP decryption keys from a file
Product: Base System
Version: 11.2-STABLE
Hardware:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724
ncrog...@gmail.com changed:
What|Removed |Added
Version|12.0-STABLE |CURRENT
--- Comment #2 from
On Tue, 26 Mar 2019 11:28:50 +0100 Gerrit Kühn
wrote about unbound error messages:
> Any idea what the error messages might mean? Or are they somewhat bogus
> (with all the 0s in there)?
Duh, it's all my fault: I forgot that I had the monitoring system not only
check the port availability, but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317
--- Comment #48 from Peter Vanek ---
(In reply to Piotr Pietruszewski from comment #47)
Hello Piotr,
Thanks for details; The mininum we can do is to run this on out platform.
My colleague is going to reproduce on default kernel issue /
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221317
--- Comment #47 from Piotr Pietruszewski ---
(In reply to Peter Vanek from comment #46)
Hello Peter,
Port of rS343621 is available for review on Phabricator (
https://reviews.freebsd.org/D19711 ). Since our validation team is currently
Hello,
I set up a pretty basic unbound service on FreeBSD 11.2 (based on the
default "local" service) that works fine for me as far as I can see (all
names are resolved etc.).
However, in the unbound logfile I see these messages repeated every minute:
---
Mar 26 11:08:37 unbound[66291:0] error:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206932
--- Comment #10 from hippi-vik...@protonmail.com ---
Hi Vincenzo,
Sorry for the late reply! I was stress-testing the firewall and so far it seems
tha above was just a one-off issue unrelated to load or Suricata. I continued
to see the same
