iflib_netmap_config entries in dmesg

[binaryanomaly]

I'm seeing these in dmesg on 21.7.:

Code: [Select]

055.723348 [ 853] iflib_netmap_config       txr 2 rxr 2 txd 2048 rxd 2048 rbufsz 2048

(did not appear on 21.1 only UP/DOWN)
which might be related to my SR-IOV NIC issues.
Would anyone know what it is and by what it may be caused?

Code: [Select]

ixv1: link state changed to DOWN
ixv1: link state changed to UP
ixv1: link state changed to DOWN
ixv1: link state changed to UP
ixv1: link state changed to DOWN
ixv1: link state changed to UP
055.451495 [ 853] iflib_netmap_config       txr 2 rxr 2 txd 2048 rxd 2048 rbufsz 2048
055.452924 [ 853] iflib_netmap_config       txr 2 rxr 2 txd 2048 rxd 2048 rbufsz 2048
ixv0: link state changed to DOWN
ixv0: link state changed to UP
055.723348 [ 853] iflib_netmap_config       txr 2 rxr 2 txd 2048 rxd 2048 rbufsz 2048
ixv0: link state changed to DOWN
ixv0: link state changed to UP

Edit:
What is the intel driver version used in 21.7?
3.3.24 seems to be the most recent.

[tuto2]

Hi,

I'm not sure what kind of issues you are facing with your NIC, as such I'm unsure whether these messages are related.

In any case, those messages are simple initialization routines excuted when netmap is compiled into the kernel and when a device is attached to the generic network-interface library iflib. It's function is to announce alignment with the hardware-specific settings.

The reason you didn't see it in 21.1 is because it's been backported from FreeBSD relatively recently, appearing since 21.7.

Cheers,

Stephan

[binaryanomaly]

Thanks a lot Stephan for your helpful explanation.

The issue I'm currently facing is that with SR-IOV the VF interface I expose to the OPNsense VM gets kind of burned during boot/initialization and shortly thereafter stops working. The entries in dmesg are what I see when this is happening.

I worked around this by exposing 2 VF interfaces and after OPNsense has booted up I switch from one to the other. That way it then works but I don't understand why this behavior is occuring.

I have not yet found out what is causing the problems with the VF interface that is active during boot/initialization and was wondering whether these messages could give a clue as I do not see anything helpful in the logs otherwise. Seems that this is also not the case.
It is an OPNsense and maybe BSD specific issue that I was not able to reproduce with a Debian VM.

Thanks for your help anyway.

[franco]

Can you share your OPNsense version information. You may be running development version with has the bad Suricata 6 running as far as IPS/netmap is concerned.


Cheers,
Franco

[binaryanomaly]

Edit updated now to:

OPNsense 21.7.r2-amd64
FreeBSD 12.1-RELEASE-p19-HBSD
OpenSSL 1.1.1k 25 Mar 2021

This is Suricata version 5.0.7 RELEASE running in SYSTEM mode

Behavior is the same.

before:

OPNsense 21.7.r1-amd64
FreeBSD 12.1-RELEASE-p18-HBSD
OpenSSL 1.1.1k 25 Mar 2021

This is Suricata version 5.0.6 RELEASE running in SYSTEM mode

[franco]

Yes, supposedly that is the good version of Suricata. And this was ok on 21.1 kernels?


Cheers,
Franco

[binaryanomaly]

No, it wasn't working with 21.1 as expected either. I wanted to see if there's an improvement with 21.7 but there's not.

As I do not see much helpful log output on 21.1/7 I was wondering if the additional info that is outputted on 21.7

Code: [Select]

c055.723348 [ 853] iflib_netmap_config       txr 2 rxr 2 txd 2048 rxd 2048 rbufsz 2048
Could give any hints regarding the potential root cause of the issue but it seems this is just additional information being outputted with 21.7.

So 21.1 and 21.7 behave the same with the exception of this additional info line in dmesg in 21.7.