Suricata 6.0.3 process never stops under FreeBSD 13-p3

[Carlos Lopez]

> On 22 Jul 2021, at 17:20, Carlos Lopez <clopmz at outlook.com> wrote:
> 
> 
>> On 22 Jul 2021, at 17:16, mike tancsa <mike at sentex.net> wrote:
>> 
>> On 7/22/2021 9:41 AM, Carlos Lopez wrote:
>>> 
>>> 
>>>> On 22 Jul 2021, at 15:37, mike tancsa <mike at sentex.net
>>>> <mailto:mike at sentex.net>> wrote:
>>>> 
>>>> On 7/21/2021 3:33 AM, Carlos Lopez wrote:
>>>>> Good morning,
>>>>> 
>>>>> I have installed Suricata 6.0.3 under FreeBSD 13-p3 host from source
>>>>> using the following compìle options:
>>>>> 
>>>>> ./configure --prefix=/opt/suricata --sysconfdir=/etc
>>>>> --localstatedir=/var --disable-gccmarch-native --enable-profiling
>>>>> --enable-profiling-locks --enable-netmap --enable-pie --enable-rust
>>>>> --enable-gccprotect --disable-suricata-update.
>>>>> 
>>>>> All works ok except when I try to stop suricata process:
>>>>> 
>>>> I have the same problem, but also have a problem with the daemon no
>>>> longer generating alerts. It will work for a few min to hours and then
>>>> it just stops.  Apart from the graceful shutdown, does it actually work
>>>> for you for any long period of time ?
>>>> 
>>>>    —Mike
>>>> 
>>> 
>>> Hi MIke,
>>> 
>>> In my case, Suricata triggers alerts, detects anomaly traffic, show
>>> statistics, etc … all It seems to work ok, except when I am trying to
>>> stop the daemon.
>>> 
>>> I am using virtue Nic drivers and autofp as a runmode option.
>>> 
>>> IMO problem is related to this
>>> issue: https://redmine.openinfosecfoundation.org/issues/4478
>>> <https://redmine.openinfosecfoundation.org/issues/4478>
>>> 
>> Thanks, that sure sounds like the problem I am seeing in issue 4478. It
>> looks like both netmap and non netmap modes shows the problem :(  What
>> nic drivers are you using ? I was testing both in a VM and on actual
>> hardware and had the same results on RELENG_12 and RELENG_11 using igb NICs
> 
> 
> 
> Sorry Mike. I using Q35 hardware and virtio nic drivers (vtnet) under a RHEL 8 KVM host.
> _______________________________________________

Please, any idea regarding this issue? has anyone had this problem?