OpenGFW merits a lab evaluation if you need programmable Linux traffic filtering and can maintain the integration yourself. Our recorded command checks provide limited setup evidence; they do not establish a working firewall deployment.
What the project claims
The OpenGFW README lists IP/TCP reassembly, protocol analyzers, an Expr-based rule engine and rules reloadable with SIGHUP. Its analyzer list includes HTTP, TLS, QUIC, DNS, SSH, SOCKS4/5, WireGuard, OpenVPN and Trojan detection. It also claims detection of some fully encrypted traffic, IPv4 and IPv6 support, flow-based multicore balancing and connection offloading. These are upstream capability statements, not results from our run.
The README lists NFQueue as the only current I/O implementation. Machine-learning classification and the web UI are marked work in progress. The supplied command source registers 10 analyzers and one DNS modifier, but those implementation counts do not measure detection accuracy or production readiness.
What our recorded run establishes
Our stored run began on October 6, 2026, at 05:33:10.045 UTC, using commit 581518071fbe72519887fc92250df31d86b4386c. Its recorded configuration was 3 CPUs, 8 GB of memory and the golang:1.24-bookworm image. No new execution was performed for this correction.
| Recorded step | Duration | Supported observation |
|---|---|---|
| Install | 28.987 seconds, rounded to 29 | Exit zero; the retained tail records a Go 1.27.0 toolchain download |
| Build | 37.085 seconds, rounded to 37 | Exit zero; the retained tail is vet-exit:0 |
| Test | 18.225 seconds, rounded to 18 | The recorded go test command exited zero |
The install label does not prove that an OpenGFW CLI was installed. Likewise, the build label and retained vet result do not independently prove compilation of a runnable binary. The image's Go 1.24 label does not establish the executed toolchain version: the install tail explicitly records go: downloading go1.27.0 (linux/amd64).
The parser's stored test totals are 10 successful package results, zero failed package results and 11 package results without tests. The visible tail contains five distinct successful package paths, then repeats them beneath a summary heading. Without complete-log reconciliation, neither the parser total nor the repeated lines establish ten unique tests. Packages marked [no test files] are not failed tests.
The checkout metrics record 74 files, about 8,345 source lines and 0.3 MB. The dependency metric records 119 entries. The harness also records two CI workflows and no detected Dockerfile, Compose file or top-level tests directory. These are checkout observations, not evidence that official container distribution or tests elsewhere are absent. No audit result was supplied.
The run provides no recorded installed-binary check, live NFQueue workload, throughput measurement or detection-accuracy evaluation. The 18-second command duration is not a network performance benchmark.
Runtime setup needs separate verification
The supplied command source requires one rules-file argument and reads a separate configuration file. It uses YAML configuration and loads rules through ExprRulesFromYAML. Configuration search paths are the working directory, $HOME/.opengfw and /etc/opengfw; --config selects an explicit file.
The code constructs NFQueue I/O and exposes queue buffers, worker settings, TCP buffering limits, UDP stream limits and optional GeoIP and GeoSite paths. An operator must arrange for the intended traffic to reach the queue and verify the resulting behavior. Our run does not establish that integration.
The supplied README extract has no worked build, configuration, rules or queue-wiring example. That limits what this review can demonstrate from the README; it does not justify claiming that all project documentation lacks examples. A useful next step is an isolated deployment check covering binary execution, configuration loading, queue integration and a known allow/block rule before routing consequential traffic through it.
Maintenance matters more than the command timings
The maintainers say they do not plan to actively continue developing OpenGFW themselves. They also say they will keep the repository available, accept pull requests and publish releases as appropriate. That is a limited maintenance commitment, rather than a declaration that no further changes will occur.
The supplied v0.4.3 release entry describes a fix for QUIC ClientHello detection when a handshake is fragmented across multiple packets. The release extract displays October 4 without a year, so it does not independently establish the existing draft's full release date. The recorded checkout's commit date is October 4, 2026; that is a separate observation.
The run records MPL-2.0 as the license. The linked issue discusses a possible move to AGPLv3; a proposal in an issue is not evidence of a completed license change. Neither star counts nor the number of visible issues establishes maintenance capacity or deployment reliability.
Choose an alternative by the job
AdGuard Home is relevant when DNS-level ad and tracker blocking is sufficient. Its README provides automated and alternative installation methods and explains a practical limitation: DNS filtering cannot block advertising that shares a domain with the content you want.
Zeek is relevant when the task is network traffic analysis and security monitoring. Its README describes protocol analyzers and a scripting language for site-specific monitoring policies. That supports a monitoring alternative, not a claim that it duplicates OpenGFW's inline filtering behavior.
How to read the scores
These are editorial suitability ratings, not benchmarks. Across each category, 1 means little supporting evidence or a major stated constraint; 2 means useful evidence with substantial gaps; 3 means adequate evidence for the intended task with material limits; 4 means strong evidence with minor limits; and 5 requires comprehensive evidence for that category. Missing evidence lowers confidence, not proof of product quality. Community scores assess the documented maintenance commitment, not popularity.
OpenGFW's command results justify further investigation. Adoption still depends on a working deployment you verify and a maintenance burden you are willing to take on.

