<!--order=1-->


<h1>pfSense First Setup Checklist</h1>
<p>pfSense is most useful when it is treated as network infrastructure rather than just another web application. The first setup is where you establish the interfaces, management path, address plan, firewall policy, and recovery process that every later change depends on. Work from the console or a local connection until the web interface is reachable and tested.</p>

<h2>Plan the Appliance Before Installing</h2>
<p>Write down the hardware, intended WAN connection, LAN network, and any VLANs before booting the installer. A small appliance normally needs at least two network interfaces: one for the internet-facing WAN and one for the trusted LAN.</p>
<ul>
  <li>record the appliance model, storage device, and network interface MAC addresses</li>
  <li>decide which interface will be WAN and which will be LAN</li>
  <li>choose a private LAN range that does not overlap with networks you must reach remotely</li>
  <li>reserve a safe maintenance path through the local console or an out-of-band console</li>
  <li>keep the installation image and release notes for the exact release being installed</li>
</ul>
<p>Do not put the management interface directly on an untrusted network just to make the first login convenient. A firewall is easiest to repair when the person configuring it still has a local path in.</p>

<h2>Install and Assign Interfaces Carefully</h2>
<p>Use the official installer for the chosen pfSense release and confirm the image checksum when one is provided. During the first boot, pfSense presents the detected interfaces and asks you to assign them. Confirm the assignment against the MAC addresses or cable labels rather than trusting the interface names alone:</p>
<pre>
WAN  = the interface connected to the modem or upstream router
LAN  = the interface connected to the trusted switch
</pre>
<p>If an interface is wrong, the appliance can appear healthy while every client is on the wrong side of the firewall. Stop and correct the assignment from the console before connecting other equipment.</p>

<h2>Give the LAN a Deliberate Management Address</h2>
<p>Set a fixed private address on LAN and use it only for the management network. For example, a new appliance might use <code>192.168.50.1/24</code>, with clients receiving addresses from a DHCP pool that leaves room for infrastructure:</p>
<pre>
LAN address:       192.168.50.1/24
DHCP pool:         192.168.50.100 - 192.168.50.199
Infrastructure:    192.168.50.2 - 192.168.50.49
</pre>
<p>Connect a laptop directly to LAN or through the trusted switch, renew its address, and open the management URL shown by the console. Test the connection before moving the appliance to its permanent location.</p>

<h2>Finish the WebConfigurator Wizard</h2>
<p>Complete the initial wizard rather than changing unrelated settings first. Set the hostname and domain you will recognize in logs, choose the correct timezone, and configure the WAN according to the upstream service:</p>
<ul>
  <li><strong>DHCP:</strong> use this when the upstream router or ISP assigns the WAN address automatically.</li>
  <li><strong>Static:</strong> enter the address, gateway, and prefix supplied by the provider or network owner.</li>
  <li><strong>PPPoE:</strong> enter the account details supplied by the provider and confirm the required interface.</li>
</ul>
<p>Change the default administrator password to a unique, long password. Do not reuse a password from the modem, wireless access point, or another service. Keep the recovery material somewhere accessible when the web interface is unavailable.</p>

<h2>Update Before Building the Network</h2>
<p>After the initial login, check <strong>System &gt; Update</strong> and apply the current supported update for the installed release. Reboot when requested, then confirm the dashboard is healthy before adding packages or custom rules.</p>
<p>Read the release notes before a major upgrade. Treat an upgrade as a change window: export a configuration backup first, ensure console access, and avoid combining the upgrade with a new VPN, VLAN, or package installation.</p>

<h2>Set DNS and DHCP Intentionally</h2>
<p>Decide whether pfSense will be the LAN DNS resolver and DHCP server, or whether those roles belong elsewhere. Avoid creating two DHCP servers on the same broadcast domain. A simple first setup usually keeps both services on pfSense:</p>
<ul>
  <li>set the LAN DHCP range smaller than the entire subnet</li>
  <li>add static mappings for switches, access points, servers, and infrastructure nodes</li>
  <li>set a meaningful hostname for each mapping so logs remain readable</li>
  <li>confirm clients receive the pfSense LAN address as their gateway and DNS server</li>
  <li>test both forward DNS lookups and access to a known outside address</li>
</ul>
<p>If the appliance will forward DNS to an upstream resolver, document which resolver is used and whether DNS over TLS, DNSSEC validation, or local overrides are part of the design.</p>

<h2>Start with a Small Firewall Policy</h2>
<p>pfSense filters traffic per interface. The default LAN policy is intentionally more permissive than the default WAN policy, but do not assume that a rule on one interface controls traffic everywhere. Before adding exceptions, write down who should be able to reach what:</p>
<table>
  <thead><tr><th>Traffic</th><th>Starting policy</th></tr></thead>
  <tbody>
    <tr><td>LAN to internet</td><td>Allow only as broadly as the network requires; record exceptions.</td></tr>
    <tr><td>WAN to firewall management</td><td>Block. Manage from LAN or a secured VPN instead.</td></tr>
    <tr><td>WAN to LAN</td><td>Block unless a specific published service has a documented destination.</td></tr>
    <tr><td>Guest to trusted LAN</td><td>Block, then allow only the DNS, DHCP, and internet paths guests need.</td></tr>
    <tr><td>IoT to trusted LAN</td><td>Block by default and add narrowly scoped exceptions.</td></tr>
  </tbody>
</table>
<p>Use aliases for groups of hosts and ports, give rules useful descriptions, and place specific exceptions above broad rules. After every change, inspect the rule hit counters and the firewall log instead of assuming the intended rule matched.</p>

<h2>Keep Management Off the WAN</h2>
<p>Do not enable the WebConfigurator or SSH on WAN as a shortcut for remote administration. Use one of these paths instead:</p>
<ul>
  <li>manage from the trusted LAN</li>
  <li>connect through a site-to-site or road-warrior VPN</li>
  <li>use a local or out-of-band console for recovery</li>
</ul>
<p>If temporary WAN access is unavoidable during a controlled migration, restrict it to a known source address, use HTTPS, set an expiry or removal time, and verify the rule is gone afterward. A forgotten management exception is an exposure, not a convenience.</p>

<h2>Back Up the Configuration</h2>
<p>Export the configuration after the initial setup and again before every significant change. A configuration backup contains sensitive material, including encrypted secrets and sometimes private keys, so store it like a credential:</p>
<ul>
  <li>keep an encrypted copy outside the appliance</li>
  <li>record which pfSense version produced the backup</li>
  <li>keep a recent backup available during upgrades</li>
  <li>test that a spare appliance or documented recovery process can use it</li>
</ul>
<p>A backup that has never been restored is only an assumption. Periodically verify that the file can be retrieved and that the organization knows who can decrypt it.</p>

<h2>Review Logs and Health</h2>
<p>Before handing the appliance over to routine operation, check the dashboard, interface status, gateway monitoring, DHCP leases, DNS service, and firewall logs. Look for:</p>
<ul>
  <li>WAN gateway flapping or packet loss</li>
  <li>unexpected DHCP servers or duplicate addresses</li>
  <li>repeated blocked connections that indicate a missing rule or an unwanted device</li>
  <li>services listening on an interface where they are not needed</li>
  <li>disk, memory, temperature, or certificate warnings</li>
</ul>
<p>Save a short network diagram with the interface assignments, subnets, VLANs, gateways, VPNs, and the location of the latest configuration backup. The diagram is part of the firewall, because it is what lets the next person troubleshoot it safely.</p>

<h2>First-Setup Handoff Checklist</h2>
<ul>
  <li>verify WAN and LAN assignments against the physical interfaces</li>
  <li>confirm the LAN address, DHCP range, gateway, and DNS behavior</li>
  <li>apply the current supported update and record the installed version</li>
  <li>change the default administrator password and keep recovery material safe</li>
  <li>confirm WAN management is disabled or narrowly controlled for a documented reason</li>
  <li>review firewall rules, aliases, NAT, and interface-specific policies</li>
  <li>export and protect a configuration backup</li>
  <li>test a client, a blocked path, DNS, gateway monitoring, and console recovery</li>
</ul>
<p>The goal is not to add every available package or rule on day one. It is to make the appliance predictable: the interfaces are known, the management path is protected, the policy is explainable, and recovery does not depend on guessing.</p>

<h2>Related Firewall Guide</h2>
<p>For the packet-filter concepts behind interface rules, state, NAT, tables, and validation, see the site's <a href="categories.php?cat=Firewalls&amp;article=Deep%20Dive%20into%20OpenBSD%27s%20%60pf%60%20Firewall">OpenBSD pf — The Packet Filter</a> guide.</p>

<h2>References</h2>
<ul>
  <li><a href="https://docs.netgate.com/pfsense/en/latest/" target="_blank" rel="noopener">Netgate pfSense Documentation ↗</a></li>
  <li><a href="https://docs.netgate.com/pfsense/en/latest/install/index.html" target="_blank" rel="noopener">pfSense Installation and Upgrade Guide ↗</a></li>
  <li><a href="https://docs.netgate.com/pfsense/en/latest/backup/index.html" target="_blank" rel="noopener">pfSense Backup and Recovery ↗</a></li>
  <li><a href="https://docs.netgate.com/pfsense/en/latest/firewall/index.html" target="_blank" rel="noopener">pfSense Firewall and NAT ↗</a></li>
</ul>