First boot

At the firewall’s first boot, we need to set up the bare minimum for accessing the web interface, where the configuration will be finalised.

VLANs do not need setting up at this time.

  • Assign vtnet0 (or em0) as the WAN interface. Set the IP address to your first failover IP address (ex.
  • Assign vtnet1 (or em1) as the LAN interface.
  • Press 2 to set the WAN interface’s IP address.

Next, we need to set up a temporary route to give us access to the web interface.

  • From the main menu, press 8 to enter the shell.
  • Add a route to the primary IP address' gateway: $ route add -net -iface vtnet0 making sure you substitute your own gateway IP (and set the iface as em0 if you are using an E1000 network card).
  • Set the route as default: $ route add default (substituting your own gateway address).
  • Ping an external host to confirm internet access ($ ping

Temporarily disable the firewall

Before the firewall is properly configured, the firewall will need disabling so you have access to the web interface. This is a temporary measure until we have given ourselves permanent access with a firewall rule, but it does mean that this section of the guide must be completed quickly (to reduce the amount of time the web interface is open to the internet). If you do not have a static IP address at home, you may want to set this to the IP of your own VPN service (which you could set up on the router by following this guide).

In the pfSense console, temporarily disable the firewall: $ pfctl -d.

If you need to pause setup for any meaningful length of time, the firewall can be enabled from the console using $ pfctl -e.

First connection to the web interface

  1. Navigate to the web interface (in this example,
  2. Log in with the default username and password (admin and pfsense).
  3. Skip the first-login wizard.
  4. Change the password for the default user (just in case):
    1. From the “System” menu, choose “User Management”.
    2. Edit the “admin” user.
    3. Change the password.

Later, you should disable the administrative user and add your own.

Finalise configuration for the WAN interface

  1. From the “System” menu, select “Routing”.
  2. Under the “Gateways” tab (which is selected by default), add a new gateway.
  3. Fill in the form:
    • Interface: WAN
    • Address family: IPv4
    • Name: OVH_Primary
    • Gateway:
    • Default gateway: (checked)
    • Show advanced
    • Weight: 1
    • Use non-local gateway: (checked)

Configuration changes restart the pf firewall, so you will need to stop it again to finish the configuration.

Next, we need to set the correct address for the interface.

  1. From the “Interfaces” menu, select “WAN”.
  2. Fill in the form:
    • MAC address: 02:01:01:e4:44:44 (the virtual MAC address we created earlier).
    • IPv4 address:
    • IPv4 upstream gateway: OVH_Primary (the gateway we just created)
    • Block bogon networks: (checked)

Once again, this will enable the firewall, so you will need to disable it again in order to whitelist a management IP address.

Whitelist a management IP

  1. From the “Firewall” menu, select “Aliases” and click “Add”.
  2. Fill in the form:
    • Name: Management
    • Description: Addresses to allow full access to the web interface
    • Type: Host(s)
    • IP or FQDN: (your home IP address)
  3. Click “Save”.
  4. From the “Firewall” menu, “Rules”, choose the “WAN” tab, and click “Add”.
  5. Fill in the form:
    • Action: Pass
    • Interface: WAN
    • Source: Single host or alias
    • Source address: Management
    • Destination: This firewall (self)
    • Log packets that are handled by this rule
    • Description: Permit remote access to the web interface
  6. Click “Save”, and apply the rule. This will restart the firewall (undoing step 1, and resecuring the router).

Configuring the LAN and OPT1 interfaces

  • The LAN interface should be static IPv4 with an IPv4 address of (or another sensible reserved range, documented here). There should not be an upstream gateway.
  • The OPT1 interface should be static IPv4 with an IPv4 address of (or, as above, another sensible reserved range). There should not be an upstream gateway.

Disable hardware checksum offload

Checksum offloading is broken in some hardware, particularly some Realtek cards. Rarely, drivers may have problems with checksum offloading and some specific NICs. This will take effect after a machine reboot or re-configure of each interface.

The network cards in SoYouStart machines do not appear to support hardware checksum offloading (this may need confirming from other sources, but the card in mine certainly doesn’t).

  1. From the “System” menu, select “Advanced” and then go to the “Networking” tab.
  2. Check “Disable hardware checksum offload”.
  3. Reboot the system (“Halt system” under the “Diagnostics” menu).