NEXWALL

Resolved issues

Every issue fixed in a release, with its code. Use the search box or the version filter to narrow the list.

CodeFixed inAreaDescription
NXW-103826.1.3updatesCheck for updates failed the first time
The update server lacked the package index of the kernel modules, so the check ended with an error until a partial copy was cached. The index is published.
NXW-103926.1.3updatesThe image of 26.1.2 trusted a different package key
The image was built with a key generated by the build, not the Nexwall key, so package updates signed by Nexwall would be refused. 26.1.3 is built with the Nexwall key. Firewalls on 26.1.2 must be reinstalled with 26.1.3.
NXW-104026.1.3dashboardThe IPS showed 7,645 rules on the Dashboard and 35,253 on its Settings
The Dashboard counted the alert-only rules of the catalog. It now shows the rules loaded for the chosen policy.
NXW-104126.1.3monitoringTop talkers could show a rate several times too high, or nothing, under load
The statistics window could be read as zero or one second. It is now at least ten seconds and measured to the millisecond.
NXW-104226.1.3threat-analyticsThreat Analytics said the sandbox was coming
The Sandbox stage now shows its real state: working, not enabled or not in the plan.
NXW-102426.1.2Web ProtectionYouTube and SafeSearch restricted modes were reset by Application Control
The connections to the addresses of YouTube Restricted Mode and SafeSearch were classified as YouTube or Google and reset by the rules of Application Control, so YouTube showed "offline". The addresses are now kept out of the analysis engine.
NXW-102526.1.2Web ProtectionGoogle and Bing did not open with SafeSearch on
The extra DNS resolver answered with the alias alone when its target was not cached, and some devices reported DNS_PROBE_FINISHED_NXDOMAIN. It now answers with plain addresses that are refreshed twice a minute.
NXW-102626.1.2LoggingThe Log Viewer failed on the firewall and Application Control tabs
The search showed "HTTP 400, cannot parse extract_regexp pattern". The pattern is now sent in a form the log database accepts.
NXW-102726.1.2LoggingAlerts of the intrusion prevention engine and proxy requests did not reach the Log Viewer
The extra log inputs were installed but not listed in the log service configuration, so they were never read. Enabling the Log Viewer now adds them.
NXW-102826.1.2Web ProtectionThe Certificate Maker showed as stopped in the Web Protection monitor
The monitor looked for the process by its full name, which the system cuts at 15 characters. It now finds it.
NXW-102926.1.2NetworkingA firewall started without the setup wizard had no WAN on virtual machines
The default WAN (eth1, DHCP) was decided before the network card drivers were loaded, so a virtual machine did not see the second card. It is now added later in the same start for units that were never configured.
NXW-103026.1.2engineThe traffic engine could stand still under load
Two threads of the Nexwall plugins waited for each other, and the capture thread ended when the kernel dropped a queued packet. Both are fixed and a watchdog recovers the engine if it ever stands still.
NXW-103126.1.2Web ProtectionSome sites did not open behind the web proxy (error 409)
Sites whose DNS answers differ between the client and the proxy were refused by the proxy. They now open: the connection goes to the address the client chose.
NXW-103226.1.2LoggingThe Firewall traffic tab showed only allowed traffic
What the WAN rejected was not logged. The WAN zone now logs it, at most 10 lines a minute.
NXW-103326.1.2NetworkingA refused connection gave no answer to the client
The traffic engine queue swallowed the ICMP "port unreachable" of a rejected connection and the messages of path MTU discovery. They pass now.
NXW-103426.1.2Web ProtectionThe web proxy could run out of open files and the antivirus switch off under load
The limit of open files is now 16,384, up to 256 files are scanned at once and the scanner connection is retried after 10 seconds.
NXW-103526.1.2NetworkingA WireGuard tunnel could pin its route to the wrong internet link
On a firewall with two internet links the route to the peer stayed on the link that was the default when the tunnel came up, which could cut the license and the updates. Tunnels no longer pin it.
NXW-103626.1.2interfaceA page with several explanations could freeze the browser
The explanation of each tab updated the shared description in a loop. Fixed in interface 3.0.
NXW-103726.1.2interfaceOpening the unit chip made it disappear
The panel read the system information in the wrong shape and failed. Fixed.
NXW-102026.1.0LoggingApplication Control tab of the Log Viewer was empty
Blocked traffic was logged but did not show in the Application Control tab of the Log Viewer (it did show in Firewall traffic), because of a leading space in the logged text. It shows now.
NXW-102126.1.0LoggingTraffic reports lost at every restart
The hourly traffic reports were kept in memory and disappeared when the firewall restarted, and only as many days fitted in 1% of the memory. They are now on the data disk and kept for 35 days.
NXW-102226.1.0BackupRemoving the storage deleted its partition
Removing the storage deleted the partition and everything on it. It now only detaches the storage; deleting the partition is a separate choice that must be ticked.
NXW-102326.1.0PerformanceSystem partition too small for extra packages
The writable part of the system partition was about 213 MB, which filled up when services such as the antivirus were added. The system partition is now 1 GB. Firewalls installed with an earlier image keep their size.
NXW-101726.0.0-rc4BackupCloud backup requests in the log
The Dashboard asked every few seconds for the list of cloud backups and logged an error each time on a firewall without cloud backup. The request now answers that there are none, and the Dashboard card is hidden and stops asking.
NXW-101826.0.0-rc4LoggingWarning about /etc/firewall.user
The firewall configuration pointed to a file that did not exist and logged a warning at every start; the file is now part of the image.
NXW-101926.0.0-rc4LoggingErrors of the port 80 page in the log
The page on port 80 wrote an error line for every unknown address it was asked for.
NXW-101426.0.0-rc3Network Protection (IPS)Intrusion signatures downloaded but not installed
The signature updater waited for its own lock when it started the installation step, so the signatures were downloaded but never installed and the IPS page showed no signature information. Only the commands that write take the lock now and the status always answers.
NXW-101526.0.0-rc3Setup wizardWizard skip did nothing before login
Skip wizard needed a session that does not exist on a new firewall.
NXW-101626.0.0-rc3Management APIManagement API crash on sign-out
Signing out with a session the firewall could not read stopped the request with a crash in the log.
NXW-101026.0.0-rc2Setup wizardSetup wizard hidden by an old session
A browser that still held a login of an earlier firewall at the same address went to the login page instead of the wizard of a new firewall.
NXW-101126.0.0-rc2Setup wizardNo interface in the WAN step
On a firewall whose ports were not named by the image, the wizard reported that the WAN zone had no interface.
NXW-101226.0.0-rc2Management APIWeb interface API crash
A session token without a user made the management API stop answering that request with a crash; it now answers not authorized.
NXW-101326.0.0-rc2LoggingErrors in the system log
The cron restart after an IPS change called a wrong path; the telemetry DNS check asked a question the firewall refuses; the updaters of the old application catalog service reported a 404 every day and at every start; two updates of the IPS signatures could write the same file at once. All of them are corrected or removed.
NXW-100126.0.0-rc1LicensingReinstalled firewall stayed unregistered
A firewall that was reinstalled kept its old registration on the license server and could not get its license or its downloads (IPS signatures, lists). Your reseller can now reset the device in the license panel, and the firewall registers again by itself.
NXW-100226.0.0-rc1LoggingLog Viewer did not open
Opening the Log Viewer restarted the web server under the request that asked for it and the browser reported a network error. Enabling it again no longer restarts anything, and the first time the page waits for the web server.
NXW-100326.0.0-rc1Web interfaceDNS & DHCP page failed to load
The page raised an error when an interface address was stored as 192.168.1.1/24. Addresses are now read in every form and interfaces without a usable IPv4 address are skipped.
NXW-100426.0.0-rc1Application ControlTraffic engine crash loop
A plugin of the traffic engine crashed the engine again and again right after it started. The cause was found with a symbolized backtrace and fixed.
NXW-100526.0.0-rc1Application ControlEngine using a whole CPU core
A plugin queue spun without waiting and kept the engine at 100% of a core. It now waits for work like the other plugins.
NXW-100626.0.0-rc1Application ControlEngine deadlock
A plugin could lock the engine against itself. The call path was changed so the engine no longer blocks.
NXW-100726.0.0-rc1LicensingLarge license data downloads
Downloads of big data sets from the license service were cut silently at 1 MiB and timed out after 30 seconds. They now accept up to 64 MiB and have ten minutes to complete.
NXW-100826.0.0-rc1PerformanceMemory exhaustion with very high connection limits
A fixed, very high connection tracking limit could exhaust memory on small machines under heavy load. The limit is now derived from the installed memory.
NXW-100926.0.0-rc1NetworkingBursts dropped on virtual network cards
Small default network card buffers dropped traffic bursts and kept throughput low in tests. Larger buffers and packet steering are now on by default for new installations.