PF (firewall)

From Wikipedia, the free encyclopedia

PF (Packet Filter, also written pf) is a BSD licensed stateful packet filter, a central piece of software for firewalling. It has been noted for its clean design and clear rule syntax[citation needed] and is comparable to iptables, ipfw and ipfilter. As of 2007, pf is the only of these that supports both IPv4 and IPv6, and can filter IPv6 network traffic. PF is developed on OpenBSD, but has been ported to many other operating systems.

Contents

[edit] History

PF was primarily written by Daniel Hartmeier. It appeared in OpenBSD 3.0, which was released on 1 December 2001.[1]

PF was originally designed as replacement for Darren Reed's IPFilter, from which it derives much of its rule syntax. IPFilter was removed from OpenBSD's CVS tree on 30 May 2001 due to perceived problems with its license. Specifically, Reed distributed some versions of his software with the license clause, "[D]erivative or modified works are not permitted without the author's prior consent."[2] While the FreeBSD and NetBSD projects apparently consulted with Reed and received such consent, the OpenBSD team decided to replace the software rather than continuing to redistribute it.

The OpenBSD team's decision became the subject of wrangling among the parties involved, degenerating largely into a flame war and failing to bring about mutual or public understanding. OpenBSD project leader Theo de Raadt wrote, "[S]oftware which OpenBSD uses and redistributes must be free to all... for any purpose... including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia."[3] (Reed was based in Australia at the time.) Reed authored a FAQ stating his own position, including, "[Can I] use IPFilter and fix any problems... or add new features? Of course. Next person who asks will get brick'd."[4]

[edit] Features

PF has since evolved quickly and has now several advantages over other available firewalls. The filtering syntax is similar to IPFilter, with some modifications to make it clearer. Network Address Translation (NAT) and Quality of Service (QoS) have been integrated into PF, QoS by importing the ALTQ queuing software and linking it with PF's configuration. Features such as pfsync and CARP for failover and redundancy, authpf for session authentication, and ftp-proxy to ease firewalling the difficult FTP protocol, have also extended PF.

One innovative feature is PF's logging. Logging is configurable per rule within the pf.conf and logs are provided from PF by a pseudo-network interface called pflog. Logs may be monitored using standard utilities such as tcpdump, which in OpenBSD has been extended especially for the purpose, or saved to disk in a modified tcpdump/pcap binary format using the pflogd daemon.

[edit] Ports

Apart from its home platform OpenBSD, PF is also installed by default in FreeBSD starting with version 5.3, in NetBSD from version 3.0, and appeared in DragonFly BSD from version 1.2. Core force, a firewalling and security product for Microsoft Windows is also derived from OpenBSD's PF.

[edit] Annotated example pf.conf file

## Macros

# The internal interface (connected to the local network).
int_if="xl0"

## Options

# Set the default policy to return RSTs or ICMPs for blocked traffic.
set block-policy return

# Ignore the loopback interface entirely.
set skip on lo0

## Translation rules

# NAT traffic on the interface in the default egress interface group (to
# which the interface out of which the default route goes is assigned) from the
# local network.
nat on egress from $int_if:network to any -> (egress)

## Filtering rules

# Default deny rule, with all blocked packets logged.
block log all

# Pass all traffic to and from the local network, using quick so that later
# rules are not evaluated if a packet matches this. Some rulesets would restrict
# local traffic much further.
pass quick on $int_if all

# Permit all traffic going out, keep state so that replies are automatically passed;
# many rulesets would have many rules here, restricting traffic in and out on the
# external (egress) interface.
pass out keep state

[edit] See also

[edit] Notes and references

[edit] Books

[edit] External links