OpenBSD PF Firewall Script – /etc/pf.conf File

Posted on in Categories Firewall last updated May 10, 2009

Following script will protect collocated FreeBSD / OpenBSD / NetBSD server running PF firewall. My box has 2 interface one for VPN and other for public interface. I only run http, dns and ssh on public port. Read pf, rc.conf and pf.conf man page for details. Tested on FreeBSD and OpenBSD.

Sample /etc/pf.conf

13 comment

  1. You probably don’t want to block all the other icmp types like fragmentation-needed – it breaks things in a subtle but annoying way!

  2. pass quick proto tcp from $table to $ext_if port 22 flags S/SA keep state

    and if you want ssh brute force options;

    table persist file “/etc/bruteforce.conf”
    pass quick proto tcp from $table to $ext_if port 22 flags S/SA keep state (max-src-conn 15, max-src-conn-rate 5/3, overload flush global)

  3. Hi, CMIIW but this rule:

    just makes this rules:

    a bit pointless? I’m still able to connect to any ports.

    1. here is what I have done
      ## ips ok for ssh
      table { 1.2.3.4, 5.6.7.8, 9.10.11.12 }

      # and then
      pass in on $ext_iface proto tcp from to any port 22 flags S/SA synproxy state

  4. It is ok. Simple and great.

    Normally, a client connects to the server and we handshake with them, then proceed to exchange data. by telling pf to handshake proxy between the client and server, tcp syn flood attacts from ddos become uneffective because a spoofed client cannot complete a handshake.

    As Dirk Gently says: More comments are welcome.

  5. freebsd 7.2-RELEASE – I believe it ships with pf @ OpenBSD 4.1

    notes:

    1) “$ext_if proto tcp from any to any port http flags S/SA synproxy modulate state”
    throws me a syntax error, I understand that using synproxy and modulate is redundant, ie synproxy includes modulate and keep.

    2) using synproxy with ssh ain’t happening for me, not yet sure – researching.

    3) in pf @ OpenBSD 4.1, default TCP flags are S/SA keep state

    thanks, keep up the great work.

    1. # 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.

Leave a Comment