Skip to content

Releases: sonertari/PFFW

PFFW 7.8

13 Nov 21:27

Choose a tag to compare

This release updates PFFW with changes from UTMFW 7.8.

PFFW 7.7

08 May 13:53

Choose a tag to compare

This release updates PFFW with changes from UTMFW 7.7.

PFFW 7.6

23 Oct 19:06

Choose a tag to compare

This release updates PFFW with changes from UTMFW 7.6.

PFFW 7.5

06 Jul 14:04

Choose a tag to compare

This release updates PFFW with changes from UTMFW 7.5.

PFFW 7.4

27 Feb 19:19

Choose a tag to compare

This release updates PFFW with changes from UTMFW 7.4.

PFFW 7.3

30 Apr 14:50

Choose a tag to compare

This release updates PFFW to OpenBSD 7.3.

PFFW 7.2

31 Dec 07:58

Choose a tag to compare

This release updates PFFW to OpenBSD 7.2.

PFFW 7.1

10 May 21:43

Choose a tag to compare

This release updates PFFW to OpenBSD 7.1.

PFFW 7.0

24 Oct 14:17

Choose a tag to compare

This release updates PFFW to OpenBSD 7.0 and PFRE 7.0.

PFFW 6.9.3

12 Aug 22:23

Choose a tag to compare

This release focuses on performance:

  • Collectd as backend for status and statistics collection: We now use collectd to continuously follow log files to collect all module status and statistics. We use the collectd plugins tail and logparser, along with the notify_fifo plugin specifically developed for UTMFW. This continuous data collection greatly improves the performance of the Dashboard and the Info pages, compared to intermittent access-based data collection.

  • Memory-based file system (MFS): Frequently used files such as logs, statistics, status, rrd, graph, cache, socket, fifo, pid, and tmp files are now moved to /var/log, which is mounted as MFS by default. MFS can be enabled, disabled, and resized during installation and on the WUI. MFS greatly improves the performance of the system, especially if the disk is slow.

  • Dnsmasq instead of isc-bind: Dnsmasq is a light-weight caching DNS forwarder. Dnsmasq consumes very little system resources compared to isc-bind, especially if the upstream DNS server or the external interface is unreachable or down.

  • Cache system status and info: We now cache overall system and individual module status and info. Without such cache, the backend could be considerably overloaded, if multiple users or Views (WUI, A4PFFW, W4PFFW) request system or module status at the same time or frequently.

And variety of other fixes and improvements.