mrkeyoor.comAsk

HyNetworks/OpenGFWtested 06 Oct 2026commit 5815180

OpenGFW review

Consider OpenGFW for a Linux research or lab deployment when you can own its configuration and maintenance.

  • Install 29 s
  • Build 37 s
10/10tests passed
  • 119 packages
Self-Hostedevaluationupdated 26 Oct 2026
+6stars / 7d

OpenGFW is an open source Linux network filtering and analysis engine with protocol analyzers and expression-based rules. Its README lists NFQueue as the only I/O implementation and warns that the project is in very early development. The maintainers say they do not plan to continue active development themselves, while remaining open to contributions and releases.

Verdict

Consider OpenGFW for a Linux research or lab deployment when you can own its configuration and maintenance. Our October 6, 2026 run at commit 5815180 records successful step exits, but does not establish ten individual passing tests, an installed CLI or working live filtering. The maintainers' stated pause in active development and the README's early-stage warning are stronger adoption constraints than these command timings. Before placing it in a traffic path, verify the binary, configuration and filtering behavior in an isolated environment.

We ran it

Lab card: what happened when we ran OpenGFW
Lab card from our sandbox run
Screenshot of OpenGFW (github.com/HyNetworks/OpenGFW)
github.com/HyNetworks/OpenGFW
Install✓ · 29s119 packages
Build✓ · 37s
Tests✓ · 18s10 passed · 0 failed of 10 (go test)
Repo74 files~8,345 lines of source · 0.3 MB · 2 CI workflows

Answers from our run

Does OpenGFW build from source?

Dependencies installed in 29 seconds (119 packages), and the build succeeded in 37 seconds. We cloned commit 5815180 into a clean Debian container with 3 CPUs and no project-specific setup.

Do OpenGFW's tests pass?

Yes. The project's own test command finished in 18 seconds and reported 10 passed, 0 failed (go test).

Who should not use OpenGFW?

Operators who require a commitment to active development from the maintainers.

What are the alternatives to OpenGFW?

AdGuard Home, Zeek. Consider OpenGFW for a Linux research or lab deployment when you can own its configuration and maintenance.

Setup2/5The October 6, 2026 run at 5815180 records successful step exits, but the retained build tail shows only vet success. Binary installation and NFQueue deployment remain unverified.
Docs2/5The supplied README explains features and maintenance limits but contains no worked setup or rule example. Command source clarifies configuration behavior; wider documentation completeness is unknown.
Community2/5Maintainers welcome contributions and intend to accept pull requests and publish releases, but explicitly plan no active development themselves. Contributor capacity and adoption are not established.
Maturity2/5The README calls the project very early stage and marks the web UI and machine-learning classifier work in progress. The recorded zero-exit test command does not establish runtime filtering reliability.

Who it’s for

Linux network researchers evaluating protocol analysis and filtering code.
Lab operators exploring the README's stated uses, including ad blocking, parental controls and VPN abuse prevention.
Contributors prepared to manage NFQueue integration, configuration and ongoing maintenance.

Who it’s NOT for

Operators who require a commitment to active development from the maintainers.
Deployments requiring an implemented packet backend beyond NFQueue, according to the supplied README.
Readers expecting a finished web interface or machine-learning classifier: the README labels both work in progress.
Teams requiring verified live filtering, throughput or detection accuracy before adoption: our recorded run does not establish those results.

Setup reality

In our recorded run on October 6, 2026, at commit 581518071fbe72519887fc92250df31d86b4386c, the harness's install step exited successfully after 28.987 seconds, its build step after 37.085 seconds, and its go test step after 18.225 seconds. The rounded stored measurements are 29, 37 and 18 seconds. The dependency metric records 119 entries; it is not a count of installed applications or audited packages.

The install tail says go: downloading go1.27.0 (linux/amd64). The recorded image was golang:1.24-bookworm, with 3 CPUs and 8 GB of memory. The image label does not establish which toolchain executed later commands. The build tail contains only vet-exit:0, so this record does not independently demonstrate a compiled or installed OpenGFW binary.

The test parser reports 10 successful package results, zero failed package results and 11 package results without tests. The retained tail repeats successful package lines under a summary heading. These figures are not a verified count of unique individual tests or exhaustive package coverage. The supported result is that the recorded test command exited zero.

The supplied command source accepts one rules-file argument, reads YAML configuration, and constructs NFQueue I/O. It searches the current directory, $HOME/.opengfw and /etc/opengfw, or accepts --config. The supplied README extract contains no worked setup or rule example; that does not establish that the entire repository or external documentation lacks examples.

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.

Alternatives

ProjectWhat it isPick it when
AdGuard Home gh↗A network-wide DNS server for blocking ads and tracking domains.Choose it when DNS-level ad and tracker blocking meets your needs. Its README provides installation methods and explains that advertising sharing a domain with content cannot be blocked at the DNS level.
ZeekA network traffic analysis and security monitoring framework with protocol analyzers and a scripting language.Choose it when your main task is traffic analysis and site-specific monitoring policies. The supplied source supports that role; it does not establish Zeek as a drop-in replacement for OpenGFW's NFQueue filtering.

What people are saying

  1. [velocity-scout] HyNetworks/OpenGFW

Sources

  1. OpenGFW README
  2. OpenGFW v0.4.3 release
  3. OpenGFW command configuration source
  4. OpenGFW license discussion

More self-hosted reviews