Call for testing: netmap on 20.7

[Voodoo]

Okay thanks, im looking forward to the netmap merge 21.1/21.7. Running suricata in a opnsense kvm would be awesome.

[mb]

We'll be posting a status update about the upstream project - hopefully this week.

[Voodoo]

I just read your blog post, gives a nice insight, im gonna link it for others: https://www.sunnyvalley.io/post/status-on-the-netmap-improvement-efforts-for-opnsense-20-7/

Btw in your plans page there is a typo "DnyDNS" should be "DynDNS" ?

[mb]

Hi @Voodoo, thanks for the heads-up.

Yes, here's the latest updated netmap status:

https://www.sunnyvalley.io/post/status-on-the-netmap-improvement-efforts-for-opnsense-20-7/

Speaking with @franco, some good news: it looks like OPNsense team will be able to provide a test kernel and start landing the bug-fixes with 20.7.1 or 20.7.2.

As mentioned in the blog post, we need more testing with regard to some drivers. Any help in that regard would be much appreciated.

We can't start fixing a problem if we don't know there is a problem.

[hfvk]

I really love OPNsense and Sensei, absolutely great work!

I am wondering that are there any possibilities that we will get em driver support for the upcoming 20.7.1 or 20.7.2 releases?

I am running a 20.1 setup with igb and em NICs and using also VLANS. I am wondering how long should I postpone the upgrade due to em driver issues especially since from my understanding we are not receiving updates to the 20.1 anymore.

I would believe that the em issue affects quite many setups.

[mb]

Hi @hfvk,

Thanks for your feedback. Much appreciated.

The issue is specific to em(4). If yours is igb(4), than you're on the safe side, you can go ahead and upgrade to 20.7 ;)

[hfvk]

Hi @mb,

Thank you for the reply.

How about systems running on em(4) NICs? Is there any estimate at this point when we could expect to get the fix to OPNsense 20.7? I am just planning how to push the updates to the systems.

I have both igb(4) and em(4) systems  ;)

[mb]

Hi @hvfk,

We have witnessed two em(4) systems behaving differently.

Run

Code Select Expand

pciconf -l

If your Chip ID is 0x100e8086, you should be fine. We also have at least one other report that it's working.
If on the other hand, the chip id is, 0x10d38086 than it's a no go.

Speaking with @franco, I would expect 20.7.1 or 20.7.2 introducing improvements.

[hfvk]

Hi again,

Well, my chip seems to be chip=0x156f8086.

So, I think I'll just select one test system with this chip and see what happens. I will report you back  :)

[mb]

So, I think I'll just select one test system with this chip and see what happens. I will report you back  :)

Yup, sounds good  :D

[hfvk]

But wait, should I have had this problem already on 20.1 since it is running FreeBSD 11.2?

[mb]

if you've been using it with VLANs, yes I would expect so

[hfvk]

I upgraded my test system and it seems that on 0x156f8086 em(4) is working fine.

OPNsense 20.7-amd64
FreeBSD 12.1-RELEASE-p7-HBSD
OpenSSL 1.1.1g 21 Apr 2020

I will continue monitoring the system and I will post back if I detect any issues.

[heresjody]

I just upgraded from 20.1.9_1 to 20.7. OPNsense is running as a VM within Proxmox, network driver is vtnet. WAN is PPPoE on VLAN, IPTV_WAN is on VLAN. Surricata is enabled (IPS). Ovpnc1 is a VPN.

Networks are working fine, just a couple of messages which don't seem to have a negative impact.

Code Select Expand


2020-07-31T23:08:03 kernel: 683.727786 [ 320] generic_netmap_register Emulated adapter for pppoe4 activated
2020-07-31T23:08:03 kernel: 683.727620 [1130] generic_netmap_attach Emulated adapter for pppoe4 created (prev was NULL)
2020-07-31T23:08:03 kernel: pppoe4: permanently promiscuous mode enabled
2020-07-31T23:08:03 kernel: 683.725852 [1035] generic_netmap_dtor Emulated netmap adapter for pppoe4 destroyed
2020-07-31T23:08:03 kernel: 683.725821 [1130] generic_netmap_attach Emulated adapter for pppoe4 created (prev was NULL)
2020-07-31T23:08:03 kernel: 683.708925 [ 320] generic_netmap_register Emulated adapter for ovpnc1 activated
2020-07-31T23:08:03 kernel: 683.708692 [1130] generic_netmap_attach Emulated adapter for ovpnc1 created (prev was NULL)
2020-07-31T23:08:03 kernel: ovpnc1: permanently promiscuous mode enabled
2020-07-31T23:08:03 kernel: 683.701541 [1035] generic_netmap_dtor Emulated netmap adapter for ovpnc1 destroyed
2020-07-31T23:08:03 kernel: 683.701510 [1130] generic_netmap_attach Emulated adapter for ovpnc1 created (prev was NULL)
2020-07-31T23:08:03 kernel: 683.623629 [ 83] vtnet_free_used 1 sgs dequeued from TX-0 (netmap=0)
2020-07-31T23:08:03 kernel: vtnet0: permanently promiscuous mode enabled


If you need any more information, or need me to do something to help troubleshoot, please let me know.

[guyp2k]

Hi again,

Well, my chip seems to be chip=0x156f8086.

So, I think I'll just select one test system with this chip and see what happens. I will report you back  :)

Are the following supported?

em0@pci0:1:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00
em1@pci0:2:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00
em2@pci0:3:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00
em3@pci0:4:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00
em4@pci0:5:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00
em5@pci0:6:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00