fwbuilder
open-sourceThe section your link pointed to isn't on fwbuilder's page any more, so we've brought you to the top.
GUIGUIA graphical user interface, controls such as windows, buttons and menus. It lets people use software visually rather than entering commands. firewall management application for iptables, PF, Cisco ASA/PIX/FWSM, and Cisco router ACLACLAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource., storing configs in a central file.
Summary
fwbuilder is an open-source desktop application for building and managing firewall policy across iptables, PF, Cisco ASA/PIX/FWSM, and Cisco router ACLsACLsAn access control list, a set of rules allowing or denying operations for particular users, services or network addresses. It decides who can use a resource. from a single GUI, with configuration data kept in a central file that can scale to hundreds of firewalls managed from one place. It runs locally, built from source on Linux, macOS, or Windows, rather than as a hosted service. This suits network administrators who manage rule sets across many heterogeneous firewalls and want one console instead of vendor-specific tools for each device. Its history is a concern: first committed in 2007 with 41 contributors over the years, but no commits in the past year, so treat it as dormant rather than actively maintained.
GUI firewall management application for iptables, PF, Cisco ASA/PIX/FWSM, and Cisco router ACL, storing configs in a central file.
How fwbuilder helps
Which of my firewalls are actually enforcing the same rule I think I wrote everywhere?
builds one policy in the GUI and compiles it out to iptables, PF, Cisco ASA/PIX/FWSM, or router ACL syntax per device, so the same logical rule is translated correctly for each vendor's format
Which devices will break if I change this one object definition?
objects like hosts, networks, and services are shared and referenced across rule sets in the central file, so editing one place and recompiling shows every firewall that consumed it
Can I move a rule set designed for one vendor onto a different platform?
the same abstract rule is recompiled against a different target firewall's syntax, without re-drawing the policy by hand
Where is the master copy of every firewall's policy kept?
all firewall configuration data lives in a single central file rather than scattered per-device files, so one file backs up or version-controls the whole rule base
Am I about to push a rule set that contradicts what a device already runs?
the GUI lets a rule set be reviewed and compiled before deployment, so mismatches surface as compile output rather than as a live misconfiguration on the device
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Release-note detail over time
See how much detail fwbuilder puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in fwbuilder/fwbuilder, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close 7 years issues closed, last 12 months
- Open backlog 50 of 102 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 50
- Contributors / month 0
- Commits / month 0
- Stars 296
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →