2026-11-18 · 4 min · Mark Bacsko

BitNinja Linux Agent 3.17.13: Reload-Ready Port Rules

BitNinja Linux Agent 3.17.13 applies port filter changes without a restart, fixes WAF3 HTTP/3 issues and makes malware scans faster and more stable.

BitNinja Linux Agent 3.17.13: Reload-Ready Port Rules

BitNinja Linux Agent 3.17.13 is now available on the frequent (beta) release channel. This release makes Linux server protection easier to manage day to day: port filter and SMTP captcha changes now apply on a module reload without a full service restart, WAF3 gets several HTTP/3 and transparent proxy fixes, and malware scanning becomes more stable and faster when AI scanning is used.

Below is a full rundown of what's new, what's improved and what's fixed in this version, so server owners and hosting providers know exactly what to expect.

What's new in BitNinja Linux Agent 3.17.13

Port filter changes apply without a restart

The IpFilter module now applies [port_filter] changes, such as greylist and blacklist port bypasses for mail ports, on a module reload and when you run --reloadiptables. You no longer need a full service restart for these settings to take effect, and ports you remove from the configuration are cleaned up as well.

SMTP captcha port changes apply on reload

In the same spirit, the CaptchaSmtp module now applies additional[] port changes on module reload and --reloadiptables. Redirections for ports that are no longer configured are removed automatically, so your mail ports always match your configuration.

Reserved ports for WAF Pro

At startup the agent now reserves the WAF Pro ports 60300, 60301, 60414 and 60415 in net.ipv4.ip_local_reserved_ports, while keeping any reservations you already have. This prevents other processes from accidentally grabbing ports the WAF needs.

WAF3 improvements and fixes

The web application firewall (WAF3) received several fixes that improve compatibility and reliability:

  • Correct HTTP/3 HEAD responses: HEAD requests over HTTP/3 no longer return Content-Length: 0 when the original response has no Content-Length. Clients such as pdf.js no longer mistake files for empty ones.
  • Cleaner response headers: the Via: 1.1 Caddy response header has been removed.
  • Stable transparent proxy after CSF reloads: a race with the IpFilter reload could make the transparent proxy fall back to DNAT after a CSF reload. This is now fixed.
  • Safer HTTP/3 rollout: HTTP/3 is enabled and advertised only after a successful HTTP/3 probe. If the probe fails, the WAF stays on HTTP/1.1 and HTTP/2 and logs the reason, so visitors keep a working connection.

Malware detection: more stable and faster

  • Worker crash fixed: a crash that could happen when SQLite VACUUM ran inside an open scan transaction (a regression in 3.17.12) has been fixed.
  • Malware source file collection removed: the agent no longer collects malware source files.
  • Faster AI scans: SQLite queries have been optimized for servers that use AI scanning.

Better diagnostics

The agent framework now adds memory usage, peak usage, the memory limit and cache sizes to out-of-memory crash reports, and logs per-module memory peaks periodically. This makes it quicker to find the root cause if a server runs short on memory.

Bundled module versions

  • BitNinja-WAF3: 1.1.4

Who should update and how

BitNinja Linux Agent 3.17.13 is a frequent (beta) release. Servers subscribed to the frequent/beta channel can pick it up now. If you run the stable channel, these changes will reach you once the version is promoted to stable.

For update instructions, release channels and configuration details, see the official documentation at doc.bitninja.io.

Summary of changes

AreaChange
IpFilterPort filter changes applied on reload, removed ports cleaned up
CaptchaSmtpadditional[] port changes applied on reload
WAF3HTTP/3 HEAD fix, Via header removed, transparent proxy fix, probe-based HTTP/3
MalwareDetectionCrash fix, source file collection removed, faster AI scan queries
FrameworkRicher out-of-memory crash reports and memory peak logging
SystemWAF Pro ports reserved at startup

FAQ

Do I need to restart BitNinja to apply port filter changes?

No. From version 3.17.13, [port_filter] changes and CaptchaSmtp additional[] port changes apply on a module reload or with --reloadiptables.

Will HTTP/3 break on servers where it isn't supported?

No. WAF3 now enables and advertises HTTP/3 only after a successful probe. Otherwise it stays on HTTP/1.1 and HTTP/2 and logs why.

Is BitNinja Linux Agent 3.17.13 a stable release?

Not yet. It is released on the frequent (beta) channel.

Which WAF3 version is included?

This release bundles BitNinja-WAF3 1.1.4.

Keep your Linux servers protected

BitNinja combines a WAF, IP reputation filtering, brute-force and login protection, and malware detection in one agent to keep your Linux servers secure with minimal maintenance. Learn more about BitNinja server security at bitninja.com, compare plans on our pricing page, and follow the BitNinja blog for future release notes. The documentation helps you get the most out of version 3.17.13.

← All postsPricingSolutions