NEXWALL

All releases / 26.2.1

Nexwall Firewall 26.2.1

Advanced and Collective Protection (AI) with a control page, and usage measurement for the license size.

Stable Release date:

Overview

Nexwall Firewall 26.2.1 adds Advanced Protection and Collective Protection (AI), with one page to control and watch them in Protection Services, and measures the active devices and the throughput for the license size. It keeps everything of 26.1.3: updates that work from System > Update, separate block and inspect choices in Web Protection, block pages, the content filter, files tested in the Nexwall sandbox, Threat Analytics and Traffic Analytics, the new interface (3.0, light and dark), and the installer ISO for virtual machines, USB sticks and appliances.

Version
26.2.1
Status
Stable: image and installer ISO built and tested
Platform
x86-64, UEFI boot
Base system
OpenWrt 25.12.5, kernel 6.12
Interface languages
English, Spanish, Brazilian Portuguese
Licensed features
Trial included

What is new

The first five items are new in 26.2.1; the others come from 26.1.x.

New

Advanced and Collective Protection page

Protection Services has a new page with one switch for each protection, the real state of both engines (running, degraded or stopped), a resource monitor, model and list updates with an Update now button, recent advisory events and the privacy notice.

New

Advanced Protection: behaviour scoring

The nexwall-atp service scores how each internal host talks to the internet (flows and DNS) with a model trained by Nexwall. A high score raises an advisory event; it never blocks. Models are signed, verified with the license server key before use, and the previous one is kept for rollback. The service is limited to about 3% of one core. The first models were trained on laboratory traffic (beacons, scans, floods): they do not detect other behaviours and can flag normal periodic check-ins. Treat events as indications to review, not verdicts.

New

Collective Protection

Firewalls report suspicious addresses and domains to the Nexwall server. An indicator reported by at least 3 different firewalls within 14 days is published automatically; one reported by fewer goes to Nexwall's review page and is published only when confirmed. Published indicators expire after 14 days unless seen again, and rejected ones are not published again. They are distributed as two threat-list categories (atp_ip and atp_dns) and blocked on firewalls with Collective Protection on. A report from a single firewall never blocks traffic on other firewalls by itself.

New

Report sharing is on by default

Sharing is on by default, explained in the setup wizard and on the page. Reports contain only the external address or domain, the kind of behaviour, a score and the date, signed by the firewall. Traffic content, files, user names, internal addresses and browsing history are never sent. Sharing can be switched off at any time; the firewall still receives the collective lists if Collective Protection is on.

New

Usage measurement for the license size

The firewall counts active devices (including OpenVPN remote-access users) and throughput on the internal networks, and sends only these numbers with the daily license check. IPsec and WireGuard tunnels are not measured. Nothing is blocked when a size is exceeded; the figures let Nexwall and the partner check the license size. No addresses leave the firewall.

New

Block page for blocked websites

When a rule with "Show a block page" blocks a website category, the user sees a page in Portuguese, Spanish or English (browser language) with the category, the rule and a reference code, which is also logged. The page is offered for categories the web proxy can open (up to 500,000 domains in total, smallest lists first); larger lists such as adult content keep the plain block. If the service that serves the page is down, the request fails and is never let through.

New

Content filter: School, Private and Work

Pages passing through the web proxy are scored from 0 to 100 for adult content, violence, drugs, gambling, hate speech and self-harm. A page that reaches the profile threshold is replaced by a block page showing the subject and score, or only recorded, as configured. Three profiles are provided (School strict, Private moderate, Work light), selected by the Standard, School and Restricted choices of the setup wizard; the Content filter tab lets you change threshold, subjects and where pages are read. Pages about study, health or news, and pages offering help, score lower. The filter reads text, not images, and only pages the proxy can open (unencrypted sites and decrypted categories).

New

Intelligent Threat Block: files tested in a sandbox

A file that passes the antivirus can be sent to the Nexwall sandbox, where it is opened and observed. With the hold option the download waits for the verdict (15 to 300 seconds, configurable) and a file judged malicious is blocked with an explanatory page; known verdicts are answered immediately. Limits per firewall: 60 files per hour, 500 files and 500 MB per day, 20 MB per file, 2 at a time (half during a trial). Available while the license includes it; settings, status and verdicts are in Web Protection and Threat Analytics.

New

Threat Analytics and Traffic Analytics

Two analytics pages follow the Dashboard. Threat Analytics shows what was stopped (block, antivirus, sandbox and advanced layers), devices at risk, web categories, top sources and reasons, and an event table kept for 35 days, with an executive report in PDF that is free in every plan. Traffic Analytics shows total traffic, busiest hour, top application and device, traffic by hour, and ranked lists of devices, applications, remote hosts and protocols for today, 7 or 30 days. The Monitor no longer has the Daily traffic tab.

New

Interface 3.0

New design in light and dark mode, consistent across all pages. The top bar has the page path, search (Ctrl+K), language, help, the status center and the unit chip (health, serial number, version, uptime, license). Each page opens with its tabs and a one-line purpose. Policy pages have tighter tables; Firewall Rules and Zones & Policies have a summary column (rules by action, busiest zone pairs, filter tags). The Dashboard shows the protection state and traffic for today, 7 or 30 days. Rules are deleted from a menu to avoid accidents.

New

Web Protection rules: block and inspect are separate choices

In the rule editor each category can be blocked, allowed or inspected independently. Blocking is decided from the server name without opening the connection; inspecting opens a category in the web proxy for the antivirus, content filter and certificate checks (allowed categories) or the block page (blocked categories). Each column has an "inspect all" switch. A category that is blocked and not inspected costs the proxy nothing.

New

A QUIC switch in Web Protection

QUIC (HTTP/3) carries web traffic over UDP, where the proxy cannot read it. The new "Block QUIC (HTTP/3)" switch in Web Protection settings (on by default) refuses UDP port 443 for clients of web-filtering rules, so browsers fall back to HTTPS over TCP and block pages, SafeSearch, antivirus and content filter apply to all traffic. The refusal reaches the client immediately.

New

Real service state

The Application Control, Network Protection (IPS), Web Protection and antivirus pages show a badge that is green only when the service is actually running (process up and bound to what it needs) and red when it is switched on but not running. The Dashboard uses the same reading.

New

Nexwall VPN clients on the Remote Access page

The Remote Access (OpenVPN) page lists the latest Nexwall VPN clients: Windows (64-bit Intel/AMD, ARM64, 32-bit), Android, and Debian and Ubuntu packages (64-bit Intel/AMD and ARM64). The macOS client is not published yet. The clients are test builds and are not code-signed.

New

Packet loss and longer windows on WAN uplinks and Performance

Charts show packet loss instead of delivery rate. The WAN uplinks and Performance pages offer 1 hour (default), 6, 12 and 24 hours, 7 and 30 days, with current, peak and average values above each chart. For long windows each point is the highest value of its interval (lowest for free memory), so short spikes remain visible. History is kept for 7 days, or a year with a data disk.

New

Log Viewer: Web Protection tab

A new tab lists all web traffic handled by the proxy, allowed or blocked, including block pages, files stopped by the antivirus or sandbox, content blocks and refused requests, plus service messages. Intrusion prevention alerts and proxy requests are now sent to the Log Viewer.

New

Installer ISO

The release is also provided as an installer ISO. Write it to a USB stick (for example with Rufus) and boot the appliance in UEFI mode. The installer verifies its image, lists only internal disks, requires typing INSTALL before erasing a disk, and reads the written image back to compare it.

Improvements and changes

Improved

Web proxy fixes verified again

The fixes for sites whose DNS answers change (the proxy uses the address the client chose, no status 409) and for ping and ICMP errors (no proxy timeouts) were verified again on a firewall running the previous image: 6 of 6 requests with a mismatched destination returned 200 and no 409 in 23,100 log lines; 160 of 160 proxied requests succeeded with and without two ping streams (p95 13.7 ms and 14.4 ms, 400 of 400 echo replies each); ICMP port unreachable reached the client in 0.05 s.

Improved

Protection overview shows the new engines

The protection layers in the interface include Advanced Protection and Collective Protection with their real state (running, degraded, stopped, off or not in the plan).

Improved

System > Update installs firewall fixes

Check for updates now finds the firewall packages, no longer fails the first time, and installs them. The update server index was incomplete and the image trusted a different key from the one that signs updates; both are fixed.

Improved

IPS rule count

The Dashboard shows the number of rules loaded for the chosen policy, the same as the IPS Settings tab. It previously included catalog rules that only raise alerts.

Improved

Top talkers on busy networks

With many connections the statistics window could be read as one second or less, showing rates several times too high or an empty list. The window is now at least ten seconds and measured to the millisecond.

Improved

Fewer "Unknown" in reports

Traffic to sites missing from the application catalog is listed under the site's domain instead of "Unknown". The catalog now includes a Nexwall application, so the firewall's own service traffic is classified.

Improved

Threat Analytics sandbox state

The Sandbox stage shows whether the sandbox is working, not enabled on this firewall or not in the plan. Advanced Threat Protection and Collective Defense are still marked as coming in this version (see NXW-2018).

Improved

The traffic engine no longer stops responding under load

Two causes of the traffic engine ceasing to respond were identified from core dumps of a laboratory firewall under load and are fixed: two threads waiting for each other inside two Nexwall plugins, and the capture thread ending when the kernel dropped a queued packet. A watchdog now checks the engine every minute; if it stops responding it takes the engine out of the path (traffic continues without analysis) and restarts it, with a cooldown and an hourly restart limit. By default, when the engine cannot keep up, traffic is let through, not blocked.

Improved

Sites with changing DNS answers open behind the web proxy

Some sites (streaming services and other CDNs) answer the client and the proxy with different addresses. The proxy used to refuse such intercepted connections with error 409. It now connects to the address the client chose, as it already did for plain HTTP, without caching.

Improved

Blocked internet traffic in the Log Viewer

The WAN zone logs what it rejects (at most 10 lines per minute), so the Firewall traffic tab shows blocked traffic as well as allowed.

Improved

Refusals reach the client immediately

The "port unreachable" answer to a rejected connection and the messages path MTU discovery needs were held back by the traffic engine queue. They now pass, so a browser whose QUIC is refused falls back to HTTPS in milliseconds instead of after a timeout.

Improved

The web proxy under load

The proxy could run out of open files (limit 1,024) and the antivirus connection stayed off for minutes after a burst of failures. The limit is now 16,384, up to 256 files can be scanned at once, and the scanner connection is retried after 10 seconds.

Improved

WireGuard tunnels and internet links

A tunnel no longer pins the route to its peer to whichever internet link was the default when it came up. On a firewall with two internet links, a stale route could cut off the license, updates and threat lists.

Improved

Application Control: engine switch and real state

Application Control has an engine switch, Web Protection turns the engine on when it needs it, and the Dashboard and pages show the real state of Network Protection (IPS) and Application Control. Top talkers and Traffic Analytics count the same flows.

Improved

Safe by default for the web

An unconfigured firewall starts with the Standard profile applied to the web: the profile's website categories, the Work content filter and, when the license and storage allow, the antivirus. The setup wizard can change every choice.

Improved

WAN at first start

A firewall started without the setup wizard has its WAN on the second network card (eth1), by DHCP, in the wan zone. On virtual machines the card was not yet visible when the default was decided; a later step in the same start now fixes this for unconfigured units.

Improved

YouTube and SafeSearch with Application Control

The addresses used by SafeSearch and YouTube Restricted Mode are kept out of the analysis engine and the inspection, and DNS answers them with plain addresses, so Google, Bing and YouTube open in restricted mode even when Application Control blocks streaming or social networks for the same devices.

Improved

Logs page uses the full window

The system log uses the full width and height, with search, row count and options in one row above it.

Resolved issues

No issues are listed as resolved in this version.

Known issues

15 known issues are open in this version. They are listed with their workarounds in one table, outside the notes of the version.

Open the known issues table

Component versions

The versions below make up the image. Most of them are pinned by checksum, so the image always contains exactly these versions. The signature bundle, the application catalog and the threat lists are not part of the image: they are downloaded and refreshed daily.

ComponentVersionNotes
Image26.2.1x86-64, UEFI, compressed disk image
Firmware sources4a2c55738f00c4d84c7db1bcd3b3bf63d364b4d1Commit of the public firewall repository the image is built from; the release tag follows
Base systemOpenWrt 25.12.5Linux kernel 6.12, nftables 1.1
Web interface3.1.1English, Spanish, Brazilian Portuguese
License component1.9.0Updates itself from the signed feed; knows the new license modules
Web Protection0.10.0Categories, profiles, block and inspect per category, block page, content filter, sandbox client, inspection, antivirus control, SafeSearch, YouTube and QUIC options
Web Protection services1.5.0Scanning service, proxy connector, block page, content filter and guard, licensed
Web proxySquid 7.1Inspection of encrypted traffic, one certificate authority per firewall; intercepted tunnels follow the client's destination
AntivirusClamAV 1.4.3, YARA 4.5.0Signatures downloaded by the firewall; YARA rules from the license server
Website categories2026.10.06.159 categories, 5.4 million domains (UT1, CC BY-SA 4.0); refreshed weekly
YARA rules2026.10.06.13,435 rules from open collections and Nexwall; refreshed weekly
Traffic classification engine5.2.8 (release 8)Netify Agent with Nexwall plugins
Traffic engine plugins1.0.4Five plugins, built for engine release 6
Intrusion prevention engineSnort 3.10.0.0With the Nexwall gate plugin 1.0.1
Intrusion signaturesdaily bundleCommunity, converted open rules and Nexwall Labs; 2026.10.02.1 at release
Application catalogdaily bundle2026.10.02.1 at release
Threat lists2026.10.02.312 DNS categories, 2 IP lists, country lists; rebuilt daily
Advanced Protection scorer0.3.0Behaviour scorer with signed models; advisory events only
Collective Protection listsatp_ip, atp_dnsThreat-list categories fed by reports reviewed by Nexwall; refreshed with the threat lists

Performance and recovery

Results of the laboratory tests of this release and how the firewall recovers when its traffic engine stops answering. The figures come from one small virtual machine and show how the protections add up; they are not a throughput guarantee. Size the firewall with the guidance at the end.

The lab and the method

  • Firewall: virtual machine with 4 cores and 4 GB of memory; Application Control, Network Protection (IPS), Web Protection with antivirus and inspection of encrypted traffic, category lists loaded.
  • Load: a client behind the firewall and a server on the internet side. Four parallel iperf3 streams (throughput), 100 new HTTP connections per second through the web proxy and 50 new HTTPS connections per second, simultaneously, 60 seconds per configuration.
  • A connection counts as completed when the whole answer arrives within 3 seconds (8 seconds for HTTPS).

Results

ConfigurationThroughputHTTP completedHTTPS completed
Everything off (reference)1.48 Gbps99 %99 %
Application Control only1.99 Gbps72 %48 %
Application Control and IPS1.64 Gbps46 %84 %
Plus the web proxy, no inspection1.33 Gbps30 %74 %
Plus inspection of encrypted traffic1.22 Gbps43 %69 %
Everything on, all rules on, category lists loaded1.22 Gbps97 %99 %
5 minutes, everything on (final code), load average 16 to 18780 Mbpsmost did not complete78 %
Web proxy alone, 100 HTTP connections per secondnot measured90 %not measured
  • The processor was the limit (system time above 90 % in the long test), not memory or the traffic engine: the more protections are on, the lower the throughput and the fewer new connections complete while the line is full.
  • The rows are not independent measurements: the machine and the test servers lost performance after about an hour of repeated runs, so the table is not a ranking of the features. Take the figures as indicative.
  • At the load of the long test the web proxy could not answer most HTTP connections within 3 seconds. A firewall that must carry 1 Gbps and open hundreds of connections per second with all protections on needs more than 4 cores.

How the firewall recovers by itself

The traffic engine (Application Control) and the intrusion prevention engine read the packets the firewall hands them. If a reader stops answering, new connections it was asked to inspect stop progressing while others continue. A watchdog detects this and corrects it without intervention:

  1. Every minute it takes three samples of each engine queue, 10 seconds apart.
  2. A queue is stalled when packets wait in all three samples and either the verdict counter did not move, or at least 64 packets wait and fewer than 10 verdicts per second are given. A reader that keeps up but is busy because the machine is overloaded is not restarted.
  3. On a stall it saves a report (queue state, memory, processes; the newest 10 are kept in /root/nfq-stall) and takes the engine's queue rules out of the path, so traffic flows without analysis until the engine is back. With the "block" overload choice, and for the IPS, the rules are left alone.
  4. It then restarts the engine that owns the stalled queue: at most 6 restarts per hour, with 90 seconds between two; beyond the limit it only reports.
  5. It records the event in the log (tag nexwall-nfq-watchdog), raises an alert (Status center, Dashboard) and writes a metric. The engine restores its rules when it starts again.

Other protections that fail open

  • When the engine cannot keep up, the default is to let traffic through (setting "when the engine is overloaded" in Application Control), not to block it.
  • If the web proxy stops answering, the guard removes the redirect and web traffic flows without inspection until the proxy is back.
  • If the antivirus engine is down, files are delivered unscanned (fail open) and the pages and the Dashboard show the antivirus as not running.
  • Settings are in /etc/config/netifyd (section watchdog): enabled, restart, max_restarts, backlog, min_rate, failsafe and core (a core dump of a stalled engine for analysis).
  • Sizing: 2 GB of memory is the minimum; use 8 GB when the antivirus, inspection, IPS and Application Control all run on a busy network. On 4 GB the system can stop the antivirus engine under heavy load.

What was tested

  • Stress and soak: the load above in eight configurations, one 5-minute soak with everything on, and a ramp up to 1,500 new connections per second.
  • Recovery: the watchdog was tested with 31 automatic cases (frozen counter, slow backlog, fast backlog that is only load, cooldown, hourly limit, failsafe) and triggered five times under load in the laboratory (before the speed rule was added; a 5-minute soak at load 16 to 18 afterwards caused no restart). Each time it took the engine out of the path and restarted it, and traffic kept flowing.
  • Web Protection, on a real client: block page on HTTPS and HTTP, SafeSearch for Google, Bing and DuckDuckGo, YouTube restricted mode, content filter (a normal page passes, an adult page is blocked), antivirus (an EICAR test file is blocked, a clean file passes), inspection with the firewall certificate, QUIC refusal, and sites whose DNS answers differ.
  • Logging: every event above reached the Log Viewer (Firewall traffic, Application Control, Web Protection, system).

Not tested

  • Intrusion detection with real attack signatures (the probes sent raised no alerts, so the IPS alert path was not exercised).
  • Runs longer than 5 minutes, hardware appliances, and more than one client at a time.
  • The installer ISO was started in UEFI and reached its language menu; installing to a disk from this exact build is checked separately.

Release track

Development history of this release, from the first image to the stable release.

  1. From 26.1.3 to 26.2.1

    Advanced Protection and Collective Protection (AI), with their control page, signed model distribution, shared indicators with review and usage measurement; license component 1.9.0; web interface 3.1.1; web proxy fixes verified again.

  2. From 26.1.2 to 26.1.3

    Package update path corrected (complete index and Nexwall key in the image); corrections to defects found after the publication of 26.1.2 (IPS rule count, Top talkers window, Threat Analytics stages, unknown applications); Nexwall application added to the catalog.

  3. From 26.1.0 to 26.1.2

    All changes of 26.1.1 (block page, content filter, sandbox client, Threat Analytics and Traffic Analytics, new dashboard and charts, Log Viewer tabs, default WAN) and the changes made after laboratory testing: traffic engine stall fixes, interface 3.0, new rule model, web proxy fixes under load and for changing DNS answers, VPN client downloads and the installer ISO.

Requirements

  • x86-64 processor and UEFI firmware with Secure Boot off.
  • At least two network interfaces (internal network and internet).
  • 2 GB of memory without Web Protection; 4 GB or more with the antivirus and inspection of encrypted traffic; 8 GB recommended when the antivirus, inspection, IPS and Application Control all run on a busy network (on 4 GB the system can stop the antivirus engine under heavy load).
  • A disk of 16 GB or more: the firewall creates its data storage (logs, reports, antivirus signatures, swap file) at first start. Smaller disks work without the signature store, the swap file and the space for a second system copy.
  • Internet access to updates.nexwall.com.br, license.nexwall.com.br and services.nexwall.com.br (updates, licenses, categories, rules, threat feeds, registration) and to the ClamAV mirrors (antivirus signatures).

Installing and upgrading

  • The release is an installable disk image for virtual machines and appliances. Verify its SHA-256 first: sha256sum on Linux, or Get-FileHash -Algorithm SHA256 in PowerShell on Windows. The result must match the Downloads table.
  • After the first start the internal interface answers on 192.168.1.1. Change the administrator password at the first login.
  • The administration guide is at https://docs.nexwall.com.br.
  • Firewalls running 26.0.0-rc4 or earlier cannot be upgraded in place: the disk layout changed (1 GB system partition, 64 MB boot partition). Install the image on a test machine or a new disk and compare. Restoring a configuration backup taken on an earlier build was not tested.
  • To inspect encrypted traffic, install the firewall's inspection certificate on the devices (Web Protection, Inspection). Without it, browsers show a warning for inspected sites.
  • The antivirus needs the data storage and downloads its signatures after it is switched on, which takes a few minutes. Choosing a profile in the setup wizard switches it on when the firewall is licensed and has storage.
  • A reseller's licenses are applied to firewalls from a pool and can be moved to another firewall; a change reaches the firewall at its next license check (about once a day).
  • The LAN -> WAN and DROP DEFAULT rules, packet steering and larger network card buffers are part of the default configuration. A firewall installed earlier keeps its settings: add the two rules by hand and keep DROP DEFAULT at the end of the list.
  • A firewall reinstalled while assigned to a customer needs its device reset by the reseller before it can get its license again.
  • A firewall running 26.1.2 cannot install package updates (its image trusts another key). Install 26.2.1 from the ISO or the image and restore the configuration from a backup.

Downloads

FileSizeSHA-256
NEXWALL-Installer-26.2.1.iso456.1 MB (456,130,560 bytes)1c389cc8bb9c6234e24557adb9f6e00ae2c8a83cbb29bee4c192a996feb9464b
nexwall-26.2.1-x86-64-generic-squashfs-combined-efi.img.gz107.0 MB (106,986,911 bytes)a6d7add4d1dd1728c5d219fb8cc34de99234fc88ebca7289206f3d0e6be77830

Check the file before you use it: the SHA-256 of the downloaded file must equal the value above.

Open source and licenses

Nexwall Firewall is built on open source software, among them OpenWrt, the Linux kernel, nftables, Snort 3, Netify Agent and nDPI, dnsmasq, banIP, adblock and VictoriaMetrics. The firewall and the operator tools are published under their original licenses; the license texts and notices ship with the image and are available on request. The Nexwall threat lists are built from open sources whose licenses allow redistribution, and the notice that lists them is part of every bundle.