PF Firewall Quad Core Gen4 SSD

Before you continue...

Truly turn-key solution

• Stateful inspection firewall
  A stateful firewall is a firewall that keeps track of the state of network connections (such as TCP streams, UDP communication) traveling across it. The firewall is programmed to distinguish legitimate packets for different types of connections. Only packets matching a known active connection will be allowed by the firewall; others will be rejected. More information can be found in this wiki.

  1. Filtering by source and destination IP, IP protocol, source and destination port for TCP and UDP traffic
  2. Able to limit simultaneous connections on a per-rule basis
  3. pfSense utilizes p0f, an advanced passive OS/network fingerprinting utility to allow you to filter by the Operating System
     initiating the connection.Want to allow FreeBSD and Linux machines to the Internet, but block Windows machines?
     pfSense can do so (amongst many other possibilities) by passively detecting the Operating System in use.
  4. Option to log or not log traffic matching each rule.
  5. Highly flexible policy routing possible by selecting gateway on a per-rule basis (for load balancing, failover, multiple WAN)
  6. Aliases allow grouping and naming of IPs, networks and ports.
     This helps keep your firewall ruleset clean and easy to understand, in environments with multiple public IPs and numerous servers.
  7. Transparent layer 2 firewalling capable - can bridge interfaces and filter traffic between them, even allowing for an IP-less firewall (though you probably want an IP for management purposes).
  8. Layer7 protocol filtering
  9. Packet normalization, so there are no ambiguities in interpretation by the ultimate destination of the packet.
     The scrub directive also reassembles fragmented packets, protecting some operating systems from some forms of attack, and drops TCP packets that have invalid flag combinations.
     
     1. Enabled in pfSense by default.
     2. Can disable if necessary. This option causes problems for some NFS implementations, but is safe and should be left enabled on most installations.
  10. Disable filter - you can turn off the firewall filter entirely if you wish to turn pfSense into a pure router.
• Granular control over state table
  The firewall's state table maintains information on your open network connections. pfSense® is a stateful firewall, by default all rules are stateful. Most firewalls lack the ability to finely control your state table. pfSense® has numerous features allowing granular control of your state table, thanks to the abilities of OpenBSD's pf.

  1. Adjustable state table size - there are multiple production pfSense installations using several hundred thousand states. The default state table size is 10,000, but it can be increased on the fly to your desired size. Each state takes approximately 1 KB of RAM, so keep in mind memory usage when sizing your state table.
  2. On a per-rule basis:
     1. Limit simultaneous client connections
     2. Limit states per host
     3. Limit new connections per second
     4. Define state timeout
     5. Define state type
  3. State types - pfSense offers multiple options for state handling.
     1. Keep state - Works with all protocols. Default for all rules.
     2. Sloppy state - Works with all protocols. Less strict state tracking, useful in cases of asymmetric routing.
     3. Modulate state - Works only with TCP. pfSense will generate strong Initial Sequence Numbers (ISNs) on behalf of the host.
     4. Synproxy state - Proxies incoming TCP connections to help protect servers from spoofed TCP SYN floods. This option includes the functionality of keep state and modulate state combined.
     5. None - Do not keep any state entries for this traffic. This is very rarely desirable, but is available because it can be useful under some limited circumstances.
  4. State table optimization options - pf offers four options for state table optimization.
     1. Normal - the default algorithm o High latency - Useful for high latency links, such as satellite connections. Expires idle connections later than normal.
     2. High latency - Useful for high latency links, such as satellite connections. Expires idle connections later than normal.
     3. Aggressive - Expires idle connections more quickly. More efficient use of hardware resources, but can drop legitimate connections.
     4. Conservative - Tries to avoid dropping legitimate connections at the expense of increased memory usage and CPU utilization.
• Network Address Translation (NAT)
  Network address translation (NAT) is a methodology of modifying network address information in Internet Protocol (IP) datagram packet headers while they are in transit across a traffic routing device for the purpose of remapping one IP address space into another. More information can be found in this wiki.

  1. Port forwards including ranges and the use of multiple public IPs
  2. 1:1 NAT for individual IPs or entire subnets.
  3. Outbound NAT
     1. Default settings NAT all outbound traffic to the WAN IP. In multiple WAN scenarios, the default settings NAT outbound traffic to the IP of the WAN interface being used.
     2. Advanced Outbound NAT allows this default behavior to be disabled, and enables the creation of very flexible NAT (or no NAT) rules.
  4. NAT Reflection - NAT reflection is possible so services can be accessed by public IP from internal networks.

  Limitations

  PPTP / GRE Limitation - The state tracking code in pf for the GRE protocol can only track a single session per public IP per external server. This means if you use PPTP VPN connections, only one internal machine can connect simultaneously to a PPTP server on the Internet. A thousand machines can connect simultaneously to a thousand different PPTP servers, but only one simultaneously to a single server. The only available work around is to use multiple public IPs on your firewall, one per client, or to use multiple public IPs on the external PPTP server. This is not a problem with other types of VPN connections. PPTP is insecure and should no longer be used.
• Traffic Shaper
  Traffic shaping (also known as "packet shaping") is the control of computer network traffic in order to optimize or guarantee performance, lower latency, and/or increase usable bandwidth by delaying packets that meet certain criteria. More specifically, traffic shaping is any action on a set of packets (often called a stream or a flow) which imposes additional delay on those packets such that they conform to some predetermined constraint (a contract or traffic profile).

  For more information on pfSense trafficshaping capabilities see PFSenseDocs.
• Captive portal
  Captive Portal allows you to force authentication, or redirection to a click through page for network access. This is commonly used on hot spot networks, but is also widely used in corporate networks for an additional layer of security on wireless or Internet access. For more information on captive portal technology in general, see the Wikipedia article on the topic. The following is a list of features in the pfSense Captive Portal.

  1. Maximum concurrent connections - Limit the number of connections to the portal itself per client IP. This feature prevents a denial of service from client PCs sending network traffic repeatedly without authenticating or clicking through the splash page.
  2. Idle timeout - Disconnect clients who are idle for more than the defined number of minutes.
  3. Hard timeout - Force a disconnect of all clients after the defined number of minutes.
  4. Logon pop up window - Option to pop up a window with a log off button.
  5. URL Redirection after authenticating or clicking through the captive portal, users can be forcefully redirected to the defined URL.
  6. MAC filtering - by default, pfSense filters using MAC addresses. If you have a subnet behind a router on a captive portal enabled interface, every machine behind the router will be authorized after one user is authorized. MAC filtering can be disabled for these scenarios.
  7. Authentication options - There are three authentication options available.
     1. No authentication - This means the user just clicks through your portal page without entering credentials.
     2. Local user manager - A local user database can be configured and used for authentication.
     3. RADIUS authentication - This is the preferred authentication method for corporate environments and ISPs. It can be used to authenticate from Microsoft Active Directory and numerous other RADIUS servers.
  8. RADIUS capabilities o Forced re-authentication
     1. Able to send Accounting updates.
     2. RADIUS MAC authentication allows captive portal to authenticate to a RADIUS server using the client's MAC address as the user name and password.
     3. Allows configuration of redundant RADIUS servers.
  9. HTTP or HTTPS - The portal page can be configured to use either HTTP or HTTPS.
  10. Pass-through MAC and IP addresses - MAC and IP addresses can be white listed to bypass the portal. Any machines with NAT port forwards will need to be bypassed so the reply traffic does not hit the portal. You may wish to exclude some machines for other reasons.
  11. File Manager - This allows you to upload images for use in your portal pages.
  12. Voucher support
  13. Multi-interface capable
  14. Multi instance Captive Portal
  15. Multiple Captive Portal RADIUS authentication sources (e.g. one for users, one for cards)

  Limitations

  "Reverse" portal, i.e. capturing traffic originating from the Internet and entering your network, is not possible.
  Only entire IP and MAC addresses can be excluded from the portal, not individual protocols and ports.
• 802.1Q VLAN support
  VLANs are virtual LAN segments of a managed switch, and when pfSense is plugged into a trunk port it can utilize VLANs to have multiple virtual interfaces, one for each available VLAN. In this manner, you can have pfSense talk to a large number of networks without the need for more physical interfaces.

  More information about VLAN's in pfSense is available in the PFSenseDocs.
• Virtual Private Network
  A virtual private network (VPN) extends a private network across a public network, such as the Internet. It enables a computer to send and receive data across shared or public networks as if it is directly connected to the private network, while benefiting from the functionality, security and management policies of the private network.
  More information can be found in this wiki.

  pfSense® offers three options for VPN connectivity, IPsec, OpenVPN, and PPTP:

  1. IPsec
     IPsec allows connectivity with any device supporting standard IPsec. This is most commonly used for site to site connectivity to other pfSense® installations, other open source firewalls (m0n0wall, etc.), and most all commercial firewall solutions (Cisco, Juniper, etc.). It can also be used for mobile client connectivity.
  2. OpenVPN
     OpenVPN is a flexible, powerful SSL VPN solution supporting a wide range of client operating systems. See the OpenVPN website for details on its abilities.
  3. PPTP
     PPTP is a popular VPN option because nearly every OS has a built in PPTP client, including every Windows release since Windows 95 OSR2. See this Wikipedia article for more information on the PPTP protocol. The pfSense PPTP Server can use a local user database, or a RADIUS server for authentication. RADIUS accounting is also supported. Firewall rules on the PPTP interface control traffic initiated by PPTP clients.

     Limitations

     Because of limitations in pf NAT, when the PPTP Server is enabled, PPTP clients cannot use the same public IP for outbound PPTP connections. This means if you have only one public IP, and use the PPTP Server, PPTP clients inside your network will not work.The work around is to use a second public IP with Advanced Outbound NAT for your internal clients. See also the PPTP limitation under NAT on this page.
• Dynamic Domain Name System
  Dynamic DNS (DDNS) is a method of automatically updating a name server in the Domain Name System (DNS), often in real time, with the active DNS configuration of its configured hostnames, addresses or other information. For more information see this wiki.

  1. Dynamic DNS
     A Dynamic DNS client is included to allow you to register your public IP with a number of dynamic DNS service providers.
     1. Custom - allowing defining update method for providers not specifically listed here.
     2. DNS-O-Matic
     3. DynDNS
     4. DHS
     5. DNSexit
     6. DyNS
     7. easyDNS
     8. freeDNS
     9. HE.net
     10. Loopia
     11. Namecheap
     12. No-IP
     13. ODS.org
     14. OpenDNS
     15. Route 53
     16. ZoneEdit
  2. A client is also available for RFC 2136 dynamic DNS updates, for use with DNS servers like BIND which support this means of updating.
• High Availability
  The Common Address Redundancy Protocol or CARP is a protocol which allows multiple hosts on the same local network to share a set of IP addresses. Its primary purpose is to provide failover redundancy, especially when used with firewalls and routers. In some configurations CARP can also provide load balancing functionality. For more information see this wiki.

  1. Hardware failover
     CARP from OpenBSD allows for hardware failover. Two or more firewalls can be configured as a failover group. If one interface fails on the primary or the primary goes offline entirely, the secondary becomes active.
  2. Configuration synchronization
     pfSense® includes configuration synchronization capabilities, so you make your configuration changes on the primary and they automatically synchronize to the secondary firewall.
  3. Synchronized State Table
     pfsync ensures the firewall's state table is replicated to all failover configured firewalls. This means your existing connections will be maintained in the case of failure, which is important to prevent network disruptions.

  Limitations

  Only works with static public IPs, does not work with stateful failover using DHCP, PPPoE, or PPTP type WANs
• Load Balancing
  Load balancing is a computer networking method for distributing workloads across multiple computing resources, such as computers, a computer cluster, network links, central processing units or disk drives. Load balancing aims to optimize resource use, maximize throughput, minimize response time, and avoid overload of any one of the resources. For more information see this wiki.

  1. Load Balancing Outbound
     Outbound load balancing is used with multiple WAN connections to provide load balancing and failover capabilities. Traffic is directed to the desired gateway or load balancing pool on a per-firewall rule basis.
  2. Inbound Load Balancing
     Inbound load balancing is used to distribute load between multiple servers. This is commonly used with web servers, mail servers, and others. Servers that fail to respond to ping requests or TCP port connections are removed from the pool.
• DHCP Server and Relay
  The Dynamic Host Configuration Protocol is used by computers for requesting Internet Protocol parameters, such as an IP address from a network server.
  The protocol operates based on the client-server model. For more information take a look at this wiki.

  1. pfSense® includes both DHCP Server and Relay functionality.
• Reporting & Monitoring
  1. RRD Graphs
     The RRD graphs in pfSense maintain historical information on the following:
     1. CPU utilization
     2. Total throughput
     3. Firewall states
     4. Individual throughput for all interfaces
     5. Packets per second rates for all interfaces
     6. WAN interface gateway(s) ping response times
     7. Traffic shaper queues on systems with traffic shaping enabled
  2. Real Time Information
     Historical information is important, but sometimes it's more important to see real time information.
     SVG graphs are available that show real time throughput for each interface.
     For traffic shaper users, the Status -> Queues screen provides a real time display of queue usage using AJAX updated gauges.
     The front page includes AJAX gauges for display of real time CPU, memory, swap and disk usage, and state table size.
     
• Package Manager
  1. Packages
     pfSense® is equiped with a package manager that gives you access to many additional features, such as:
     1. VOIP, through the Freeswitch package
     2. Intrusion detection with the Snort package
     3. High Availability package
     4. Internet Proxy, uses the Squid package
     5. and many more...

  Note / Limitations regarding packages

  Some packages require a hard drive to work properly, this includes all packages that require to write to the drive, such as a proxy.
  Packages can complicate upgrading as they may be depended on a specific version (more on upgrading can be found here).
  Most packages can be installed on a Flash Based version, but we recommend to use a flash storage of minimal 1GB.

For information about pfSense® CE see www.pfsense.org

Screenshot(s)

Firewall

Traffic Graph

Setting

High quality enclosure, build with the best materials available.