Messages

That is correct, I upgraded from 21.1.7_1. Is there a specific reason for not automatically reinstalling the packages when going from CE to BE? I can imagine it could have negative impacts on the reliability since BE expects 21.4.2 packages to be present.

Thank you for the quick answer. I will reinstall the aforementioned packages to make sure BE is installed as intended  8)

Hey all,

Just upgraded to 21.4.2. Smooth sailing as always. However when I ran a health audit, I stumbled upon some inconsistencies.

Code Select Expand

>>> Check for core packages consistency
Core package "opnsense-business" has 67 dependencies to check.
Checking packages: ................
isc-dhcp44-relay-4.4.2P1 version mismatch, expected 4.4.2_1
Checking packages: .
isc-dhcp44-server-4.4.2P1_1 version mismatch, expected 4.4.2_1
Checking packages: ........................................
py37-ujson-4.0.2 version mismatch, expected 3.0.0
Checking packages: .....
strongswan-5.9.2_2 version mismatch, expected 5.9.2_1
Checking packages: ....... done
***DONE***

My assessment it's nothing to worry about. Maybe a difference between the FreeBSD 12 packages and the 21.4.2 packages? Can anyone confirm my assessment?

is this perhaps the same issue as: https://forum.opnsense.org/index.php?topic=20516.0   ???

Can't speak for the TS, but for me personally it's more a feature request or general questions than a specific problem I have.

And yes I had the unbound instability issues with 20.7.7 but thanks to the topic I reverted to the old unbound version weeks ago.

I have to say I'm curious about this as well. Sometimes a certain website doesn't work anymore and it's difficult to see wether it's the firewall, VPN, DoT or DNSBL. Or something completely unrelated. 

Awesome, results are all that count. Enjoy your setup.

Sounds like an IGMP snooping error. Do you have IGMP snooping enabled in your switch?

Are you using virtualization, for example Proxmox?

As I understand it our configuration should run fine now (also have Proxmox with vtnet driver). As far as the PPPoE for WAN interface, I'm not sure if that is fully working right now. According to https://docs.google.com/spreadsheets/d/1RVj8K3XOzWi-Bkjq6hUxWudu7Cxd8FFTqjLiBMzZWEM/htmlview#gid=0 it still seems to be not completely finished.

Different than stock.

This is correct. Opnsense notices a different kernel than the 20.7.3 kernel so it sees it as an "update".

Upsi, then I was too ambitious....

root@OPNsense:~ # opnsense-update -kr 20.7.3-netmap
Fetching kernel-20.7.3-netmap-amd64.txz: ......... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-20.7.3-netmap-amd64.txz... done
Please reboot.

😂😂 But does it work? 🤔

Still going strong with the test kernel. On both my em and my vtnet interface servers no crashes since I installed in 7 days ago. 

Just checking: Can I safely apply the netmap test kernel to 20.7.3?

FreeBSD 12.1-RELEASE-p9-HBSD

To doublecheck I'm providing valid testing results for you (PPPoE WAN / Suricata)
1. Only select interface: In my case LAN (vtnet) and don't select WAN (vtnet vlan 6)
2. Add public IP to home networks.

Hi @heresjody:

1- Correct. Though we have not touched pppoe+netmap yet. Use Sensei on LAN.
2- Not sure if I understood correctly. Can you elaborate?

I'm using Suricata, not Sensei. In the settings of Suricata you can add your public IP to the home network setting. Since PPPoE and netmap hasn't been touched yet thi setting is irrelevant. For now at least 😬

Kernel update worked fine with me.

   OPNsense 20.7.2-amd64
FreeBSD 12.1-RELEASE-p9-HBSD
OpenSSL 1.1.1g 21 Apr 2020

To doublecheck I'm providing valid testing results for you (PPPoE WAN / Suricata)
1. Only select interface: In my case LAN (vtnet) and don't select WAN (vtnet vlan 6)
2. Add public IP to home networks.

Correct?