Blog: Introducing Firewall

[Copilot]

Adds a blog post announcing the new Firewall feature, following the structure of the existing Hosts File Editor post.

Changes

• Website/blog/2026-04-27-introducing-firewall/index.md — new post with frontmatter (slug, title, description, authors, tags, keywords), <!-- truncate --> after the intro, and sections covering the NETworkManager_ prefix scoping, feature list, Add/Edit rule dialog fields, and admin-rights requirement
• firewall.png / firewall-rule.png — images copied from Website/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-27-introducing-firewall/ announcing the Firewall feature introduced in PR #3383. The post covers rule scoping via the NETworkManager_ prefix, available actions (add/edit/enable/disable/delete/export), the full set of Add/Edit rule fields, and the read-only behaviour when not running as administrator. Both UI screenshots (firewall.png, firewall-rule.png) are co-located in the blog directory.

To-Do

• Update documentation to reflect this changes
• Update changelog to reflect this changes

Contributing

By submitting this pull request, I confirm the following:

• I have read and understood the contributing guidelines and the code of conduct.
• I have have added my name, username or email to the contributors list or don't want to.
• The code or resource is compatible with the GNU General Public License v3.0.

Original prompt

Create a blog post announcing the new Firewall feature in the repository BornToBeRoot/NETworkManager.

Requirements:

1. Use the existing blog post about the Hosts File Editor as reference for tone/structure: Website/blog/2025-09-06-introducing-hosts-file-editor/index.md.
2. Base the content on the existing documentation page: Website/docs/application/firewall.md.
3. Include images from the docs. Specifically:
   • The main Firewall screenshot (from docs ../img/firewall.png).
   • The Add/Edit rule dialog screenshot (from docs ../img/firewall-rule.png).
   • Also include the rules image (ensure it is included in the blog post; locate the appropriate image in the repo and reference it similarly).
4. Add the new blog post under Website/blog/ using a date-based directory and index.md like other posts (choose an appropriate date/slug for the Firewall announcement).
5. Ensure the post contains frontmatter similar to the Hosts File Editor post (slug/title/description/authors/tags/keywords) and includes <!-- truncate --> after the intro.
6. Create a pull request with these changes.

Context:

• New Firewall feature recently added (see commits around PR Feature: Firewall app #3383).
• Documentation describes that NETworkManager manages only rules with the NETworkManager_ prefix and that admin rights are required for modifications.

Links for reference:

• Firewall docs: https://github.com/BornToBeRoot/NETworkManager/blob/main/Website/docs/application/firewall.md
• Hosts File Editor blog: https://github.com/BornToBeRoot/NETworkManager/blob/main/Website/blog/2025-09-06-introducing-hosts-file-editor/index.md

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:

• View firewall rules created by NETworkManager
• Add new inbound or outbound rules
• Edit existing rules (same dialog is used for Add/Edit)
• Enable / disable rules quickly
• Delete rules you no longer need
• Copy or export rule information
• Refresh the list with F5
• Open the native Windows Firewall console (WF.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:

• Direction: Inbound / Outbound
• Action: Allow / Block
• Protocol: Any, TCP, UDP, ICMPv4, ICMPv6, GRE, L2TP
• Ports: local/remote ports (available for TCP/UDP)
• Addresses: local/remote addresses (supports single IPs, ranges, and subnets — including CIDR and subnet masks)
• Program: limit the rule to a specific executable (optional)
• Interface type: Any, Wired, Wireless, RemoteAccess
• Network profiles: Domain / Private / Public (at least one is required)

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.