Bug #14416: Update Suricata binary package build OPTION knobs for NETMAP to reflect recent upstream change. - pfSense - pfSense bugtracker

Actions

Copy link

Bug #14416

closed

Update Suricata binary package build OPTION knobs for NETMAP to reflect recent upstream change.

Added by Bill Meeks about 2 years ago. Updated about 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Package System

Target version:

Start date:

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Default

Affected Version:

2.7.x

Affected Architecture:

All

Description

Recent updates in FreeBSD ports upstream require a small change to the syntax of the NETMAP and NETMAP_V14 build OPTION knobs used to build the Suricata binary in pfSense. Instead of separate NETMAP and NETMAP_V14 knobs, there is now just the single NETMAP knob in the Makefile OPTIONS. The choice of using the new Netmap v14 API is made by adding an additional netmap_v14 parameter to the NETMAP_CONFIGURE line in the package Makefile.

Currently the FreeBSD ports upstream default for NETMAP_CONFIGURE is netmap # netmap_v14, which disables use of the new v14 API. However, we have been succesfully using the v14 netmap API in pfSense for nearly two years. Thus to continue using the v14 API (which provides multiple host stack rings for netmap), the binary package Makefile NETMAP_CONFIGURE line used for pfSense is netmap netmap_v14. This enables NETMAP and also flips on the multiple host stack rings support provided by the v14 API.