|
| 1 | +--- |
| 2 | +slug: introducing-firewall |
| 3 | +title: Introducing Firewall |
| 4 | +description: "NETworkManager introduces the new Firewall feature. View, add, edit, enable, disable, and delete Windows Firewall rules managed by NETworkManager — all from a user-friendly interface." |
| 5 | +authors: [borntoberoot] |
| 6 | +tags: [firewall, windows firewall, security, new feature] |
| 7 | +keywords: [NETworkManager, Windows Firewall, Windows Defender Firewall, firewall rules, inbound, outbound, network security] |
| 8 | +--- |
| 9 | + |
| 10 | +NETworkManager introduces a new feature, the `Firewall`. You can now manage Windows Firewall rules created by NETworkManager directly from within the app — no more jumping between MMC snap-ins for day-to-day tasks. |
| 11 | + |
| 12 | +This is especially useful if you frequently spin up local services (lab environments, dev boxes, game servers, small internal tools) and need a quick and repeatable way to open or block ports, restrict traffic to specific IP ranges, or scope rules to profiles like **Domain**, **Private**, or **Public**. |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +<!-- truncate --> |
| 17 | + |
| 18 | +## Manage rules safely (and without touching your system rules) |
| 19 | + |
| 20 | +The Firewall view intentionally focuses on rules managed by NETworkManager only. |
| 21 | + |
| 22 | +Every rule created via NETworkManager is stored with a `NETworkManager_` prefix in the Windows Firewall rule display name. This makes it easy to distinguish "your" rules from system-managed or third-party rules — and it allows NETworkManager to filter the list so you only see what it owns. |
| 23 | + |
| 24 | +## What you can do with the new Firewall feature |
| 25 | + |
| 26 | +- View firewall rules created by NETworkManager |
| 27 | +- Add new inbound or outbound rules |
| 28 | +- Edit existing rules |
| 29 | +- Enable or disable rules quickly |
| 30 | +- Delete rules you no longer need |
| 31 | +- Copy or export rule information |
| 32 | +- Refresh the list with `F5` |
| 33 | +- Open the native Windows Firewall console (`WF.msc`) via the **Windows Firewall Settings** button |
| 34 | + |
| 35 | +## Add / Edit rules — with the options you actually need |
| 36 | + |
| 37 | +When creating or editing a rule, NETworkManager exposes the most common and important fields in a clear dialog: |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | +- **Name**: Display name of the rule (the `NETworkManager_` prefix is added automatically and hidden in the UI) |
| 42 | +- **Enabled**: Whether the rule is active right after creation |
| 43 | +- **Description**: Optional description of the rule |
| 44 | +- **Direction**: Inbound / Outbound |
| 45 | +- **Action**: Allow / Block |
| 46 | +- **Protocol**: Any, TCP, UDP, ICMPv4, ICMPv6, GRE, L2TP |
| 47 | +- **Local / Remote ports**: Available for TCP and UDP; multiple ports and ranges separated by `;` |
| 48 | +- **Local / Remote addresses**: Supports single IPs, ranges, subnets (CIDR and subnet masks), and keywords such as `LocalSubnet` or `Internet` |
| 49 | +- **Program**: Limit the rule to a specific executable (optional) |
| 50 | +- **Interface type**: Any, Wired, Wireless, RemoteAccess |
| 51 | +- **Network profiles**: Domain / Private / Public (at least one must be selected) |
| 52 | + |
| 53 | +You can find all details (including examples for port and address formats) in the [official documentation](https://borntoberoot.net/NETworkManager/docs/application/firewall). |
| 54 | + |
| 55 | +## Administrator privileges |
| 56 | + |
| 57 | +Managing firewall rules requires elevated rights. If NETworkManager is not running as administrator, the Firewall view is **read-only**. Use the **Restart as administrator** button to relaunch NETworkManager with the required privileges. |
| 58 | + |
| 59 | +## Try it now |
| 60 | + |
| 61 | +You can test this feature in the [latest pre-release of NETworkManager](https://borntoberoot.net/NETworkManager/download#pre-release). |
| 62 | + |
| 63 | +If you find any issues or have suggestions for improvement, please open an [issue on GitHub](https://github.com/BornToBeRoot/NETworkManager/issues). |
0 commit comments