Messages

1

Development and Code Review / Re: make "clean-all" equivalent

« on: May 18, 2022, 01:03:37 pm »

Hello Franco,
yes, I'm in "tools" directory.

I have already built the components (ports, src, plugins ecc. with "make dvd" or other "make ...").
Suppose that somethings went wrong during the build process or there is a new OPNSense version, so I need to run a new "make" of OPNSense.
What is the correct way to perform a new "make"?

Regards,
Daniele

2

Development and Code Review / make "clean-all" equivalent

« on: May 18, 2022, 09:41:30 am »

Hello,
I need to rebuild OPNSense after an upgrade.
What are the correct steps to clean the build environment (a sort of "make clean-all") before a new make dvd?

Is it enough "make clean-obj"?

Regards,
Daniele

3

Development and Code Review / Re: Building 22.1.6

« on: May 10, 2022, 09:49:03 am »

Thank you Franco,
I wait for the 22.1.7.
In the while, what is the build directive to use the tag 22.1.6?
PRODUCT_VERSION=22.1.6   ?

Regards,
Daniele

4

Development and Code Review / Building 22.1.6

« on: May 09, 2022, 01:34:41 pm »

Hello,
I'm trying to build Opnsense 22.1.6, and I'm facing some problems I didn't meet with Opnsense 21.1.x.

1. I run "make update" and "make dvd" (or make vm), the build completes successfully, but there aren't the packages.
I must run "make packages" and then I have all packages compiled.
Is it normal?

Furthermore the packages are *.pkg instead of *.txz.
Is it normal?

2. The tool chain uses pkg-1.17.5_1.pkg, while in the Opnsense 22.1.6 there is pkg-1.16.3_1.txz.
If I try to install a package built on my environment on an Opnsense 22.1.6 I get the following message
...
Installed packages to be UPGRADED:
   pkg: 1.16.3_1 -> 1.17.5_1

Should I upgrade the pkg in the Opnsense 22.1.6 machine?
Is it possible to use the 1.16.3_1 in the build system?

3. If I create my own private repository from the compiled version, it produces version "opnsense 22.1.6_10" instead of "22.1.6".
If I configure the "Mirror" filed to point on an Opnsense system and click on "Check for updates", it requires to perform an upgrade to the "22.1.6", even if the system is already the "22.1.6".
Why there is this diffence?

I followed this guide https://github.com/opnsense/tools/blob/master/README.md to prepare the build system, as I did for Opnsense 21.1.x.

Thanks in advance,
Daniele

5

Hardware and Performance / Weird packet loss with qemu

« on: April 29, 2022, 05:17:20 pm »

Hello,
we are experiencing a weird behavior in our performance tests.

We have OPNSense 22.1.6 virtualized with qemu. VM with 4 core, 3 NIC 1G with virtio (LAN, WAN, Management).
We are testing bidirectional traffic between WAN and LAN and we have a packet drops problem.
We notice these weird things:
1) the percentage of drop does not depend on the throughput, from 30Mbps to 700Mbps (Imix410 bidirectional) we have always more or less the same results:
~ 0,06% - 0,12% packet drops on both sides (LAN and WAN).
2) If we enable Suricata IDS we have 0 packet drops!!
That's sound very strange to me.

Does someone has any ideas on what's happening?

Note:
- we have Dpdk acceleration on the host.
- With OPNSense 21.6 and previous versions we had terrible performance, we couldn't go over 140Mbps Imix 410 without IDS and ~ 80Mpbs with IDS, with much more packet drops.
- The OPNSense configuration is very basic: no service active, no NAT, no rule on firewall (except for a "pass all" rule on WAN), no VLAN, no IPS.

Thanks in advance!