Blog: Introducing Firewall#3400
Conversation
Agent-Logs-Url: https://github.com/BornToBeRoot/NETworkManager/sessions/75dd8e9e-2942-498a-b5cd-1dd7d4ddafcc Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds a new Docusaurus blog post announcing the Firewall feature, modeled after the existing “Introducing Hosts File Editor” post, and co-locates the required screenshots with the post.
Changes:
- Add a new blog post at
Website/blog/2026-04-27-introducing-firewall/index.mdwith frontmatter, intro + truncate marker, feature overview, and admin-rights note. - Add and reference two screenshots (
firewall.png,firewall-rule.png) from within the blog post directory.
Reviewed changes
Copilot reviewed 1 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Website/blog/2026-04-27-introducing-firewall/index.md | New “Introducing Firewall” blog post content and image references. |
| Website/blog/2026-04-27-introducing-firewall/firewall.png | Screenshot used in the blog post. |
| Website/blog/2026-04-27-introducing-firewall/firewall-rule.png | Add/Edit rule dialog screenshot used in the blog post. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Name**: Display name of the rule (the `NETworkManager_` prefix is added automatically and hidden in the UI) | ||
| - **Direction**: Inbound / Outbound | ||
| - **Action**: Allow / Block | ||
| - **Protocol**: Any, TCP, UDP, ICMPv4, ICMPv6, GRE, L2TP | ||
| - **Local / Remote ports**: Available for TCP and UDP; multiple ports and ranges separated by `;` | ||
| - **Local / Remote addresses**: Supports single IPs, ranges, subnets (CIDR and subnet masks), and keywords such as `LocalSubnet` or `Internet` | ||
| - **Program**: Limit the rule to a specific executable (optional) | ||
| - **Interface type**: Any, Wired, Wireless, RemoteAccess | ||
| - **Network profiles**: Domain / Private / Public (at least one must be selected) |
There was a problem hiding this comment.
The Add/Edit rule field list appears incomplete compared to the Firewall documentation: the dialog also has Enabled and Description fields. Either add those fields here (to match the “full set of fields” intent) or adjust the surrounding wording so it’s clear this is a subset of the dialog options.
There was a problem hiding this comment.
Added Enabled and Description fields to the list in commit 64ec83f. The field list now matches the complete set of options in the Add/Edit rule dialog.
…e list Agent-Logs-Url: https://github.com/BornToBeRoot/NETworkManager/sessions/f094a888-9462-4d64-9c75-2818d802284c Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
|
|
||
| ## Try it now | ||
|
|
||
| Upgrade now to the [latest version of NETworkManager](https://borntoberoot.net/NETworkManager/download) to use the new Firewall feature. |
There was a problem hiding this comment.
@copilot rewrite this to you can test this feature in the latest pre-release and change the download link: https://borntoberoot.net/NETworkManager/download#pre-release
There was a problem hiding this comment.
Done in commit 1bdc9c7. The section now reads: "You can test this feature in the latest pre-release of NETworkManager."
Agent-Logs-Url: https://github.com/BornToBeRoot/NETworkManager/sessions/0743a88b-975a-4dc4-8b30-d0a94c2c8a26 Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
|
@copilot adjust the date to today. |
Agent-Logs-Url: https://github.com/BornToBeRoot/NETworkManager/sessions/f176c3d4-01a7-49f9-85b6-4e7322f38fb4 Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Adds a blog post announcing the new Firewall feature, following the structure of the existing Hosts File Editor post.
Changes proposed in this pull request
Website/blog/2026-04-30-introducing-firewall/index.md— new post with frontmatter (slug, title, description, authors, tags, keywords),<!-- truncate -->after the intro, and sections covering theNETworkManager_prefix scoping, feature list, complete Add/Edit rule dialog fields (including Enabled and Description), and admin-rights requirement; the "Try it now" section links to the pre-release download athttps://borntoberoot.net/NETworkManager/download#pre-releasefirewall.png/firewall-rule.png— images copied fromWebsite/docs/img/into the blog post directory and referenced with relative paths (./firewall.png,./firewall-rule.png)Related issue(s)
Copilot generated summary
Copilot summary
Adds a new Docusaurus blog post under
Website/blog/2026-04-30-introducing-firewall/announcing the Firewall feature. The post covers rule scoping via theNETworkManager_prefix, available actions (add/edit/enable/disable/delete/export), the complete set of Add/Edit rule dialog fields (Name, Enabled, Description, Direction, Action, Protocol, Local/Remote ports, Local/Remote addresses, Program, Interface type, Network profiles), the read-only behaviour when not running as administrator, and a "Try it now" section pointing readers to the latest pre-release download. Both UI screenshots (firewall.png,firewall-rule.png) are co-located in the blog directory.To-Do
Contributing
By submitting this pull request, I confirm the following:
Original prompt
Create a blog post announcing the new Firewall feature in the repository
BornToBeRoot/NETworkManager.Requirements:
Website/blog/2025-09-06-introducing-hosts-file-editor/index.md.Website/docs/application/firewall.md.../img/firewall.png).../img/firewall-rule.png).Website/blog/using a date-based directory andindex.mdlike other posts (choose an appropriate date/slug for the Firewall announcement).<!-- truncate -->after the intro.Context:
NETworkManager_prefix and that admin rights are required for modifications.Links for reference:
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: Write a Blog Post announcing the new Firewall feature. See the recent commits, see the existing firewall.md docs, use the images from the docs. See the blog post about the hosts file editor as reference.
Assistant: ````markdown name=Website/blog/2026-04-27-introducing-firewall/index.md
slug: introducing-firewall
title: Introducing Firewall
description: "NETworkManager introduces the new Firewall feature. Create, edit, enable, disable, and delete Windows Firewall rules managed by NETworkManager — all from a user-friendly interface."
authors: [borntoberoot]
tags: [firewall, windows firewall, security, new feature]
keywords: [NETworkManager, Windows Firewall, Windows Defender Firewall, firewall rules, inbound, outbound, network security]
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 the common day-to-day tasks.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.
Manage rules safely (and without touching your system rules)
The Firewall view intentionally focuses on rules managed by NETworkManager only.
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.What you can do with the new Firewall feature
With the new Firewall app you can:
F5WF.msc) via a button (Windows Firewall Settings)Add / Edit rules — with the options you actually need
When creating a rule, NETworkManager exposes the most common and important fields in a clear UI, including:
You can find all details (including examples for ports and address formats) in the official documentation:
https://borntoberoot.net/NETworkManager/docs/application/firewall
Administrator privileges
Like editing the hosts file, managing firewall rules requires elevated rights.
If NETworkManager is not running as administrator, the Firewall view is read-only. U...
This pull request was created from Copilot chat.