You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Website/blog/2026-04-30-introducing-firewall/index.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ tags: [firewall, windows firewall, security, new feature]
7
7
keywords: [NETworkManager, Windows Firewall, Windows Defender Firewall, firewall rules, inbound, outbound, network security]
8
8
---
9
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.
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
11
12
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
13
@@ -25,7 +25,7 @@ Every rule created via NETworkManager is stored with a `NETworkManager_` prefix
25
25
26
26
- View firewall rules created by NETworkManager
27
27
- Add new inbound or outbound rules
28
-
- Edit existing rules (the same dialog is used for both Add and Edit)
28
+
- Edit existing rules
29
29
- Enable or disable rules quickly
30
30
- Delete rules you no longer need
31
31
- Copy or export rule information
@@ -54,9 +54,7 @@ You can find all details (including examples for port and address formats) in th
54
54
55
55
## Administrator privileges
56
56
57
-
Like editing the hosts file, managing firewall rules requires elevated rights.
58
-
59
-
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.
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.
0 commit comments