ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #pfsense
Learn how to deploy PfSense’s captive portal for guest Wi‑Fi in a small office—step‑by‑step GUI configuration, a worked example, and the trade‑offs to consider.
Step‑by‑step guide to configure pfSense HA with CARP, including prerequisites, VIP configuration, XMLRPC sync, verification, and failover recovery.
When extending a corporate network with pfSense, choosing the right VPN backend—WireGuard, OpenVPN, or IPsec—depends on performance, client support, and regulatory constraints. This guide compares features, trade‑offs, and walks through a WireGuard setup between pfSense and an Ubuntu client.
Stop managing dozens of identical firewall rules. Learn how to use pfSense Aliases to group IPs, ports, and networks into scalable, easy-to-audit configurations.
A practical pfSense OpenVPN remote-access build: certificate setup, UDP server settings that avoid subnet conflicts, scoped firewall rules on the OpenVPN interface, and clean client exports.
Determine how changing the DNS mode from Forwarder to Resolver influences the ability of DHCP static mappings to resolve hostnames locally. Because the GUI enforces mutual exclusivity, enabling the Resolver grays out the Forwarder and does not automatically migrate existing static hostname entries, leaving uncertainty about whether the Resolver will use thos
Goal I want pfSense to tolerate TCP retransmissions (retries) on a connection without tearing down the state entry or causing the application to re-issue writes, while still keeping stateful inspection strict enough to be meaningful. Context and constraints pfSense uses the pf stateful engine: once a packet matches a pass rule, subsequent packets in the flow
I'm specifically looking for a definition of what the following mean: TCP:RA, TCP:FA ,TCP:PA, TCP:S, TCP:SEC The context is that I'm looking at some pfSense logs which are showing rejected packets by the default deny rule. My understanding is that this can happen from asymmetric network traffic where perhaps a connection is closed before a packet acknowledgi
pfSense's documented build path runs through pfSense-Tools on a FreeBSD host, producing installable ISO and memstick images from source. Repeatability hinges on matching the host FreeBSD release to the pfSense branch being built — for the current CE 2.7.x line the docs point at a specific FreeBSD 14.x release, though the exact pairing should be confirmed aga