Book Image

pfSense 2.x Cookbook - Second Edition

By : David Zientara
Book Image

pfSense 2.x Cookbook - Second Edition

By: David Zientara

Overview of this book

pfSense is an open source distribution of the FreeBSD-based firewall that provides a platform for ?exible and powerful routing and firewalling. The versatility of pfSense presents us with a wide array of configuration options, which makes determining requirements a little more difficult and a lot more important compared to other offerings. pfSense 2.x Cookbook – Second Edition starts by providing you with an understanding of how to complete the basic steps needed to render a pfSense firewall operational. It starts by showing you how to set up different forms of NAT entries and firewall rules and use aliases and scheduling in firewall rules. Moving on, you will learn how to implement a captive portal set up in different ways (no authentication, user manager authentication, and RADIUS authentication), as well as NTP and SNMP configuration. You will then learn how to set up a VPN tunnel with pfSense. The book then focuses on setting up traffic shaping with pfSense, using either the built-in traffic shaping wizard, custom ?oating rules, or Snort. Toward the end, you will set up multiple WAN interfaces, load balancing and failover groups, and a CARP failover group. You will also learn how to bridge interfaces, add static routing entries, and use dynamic routing protocols via third-party packages.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
About Packt

Creating a floating rule

This recipe describes how to create a floating rule.

Floating firewall rules have several distinct advantages over non-floating rules:

  • They can apply to more than one interface at a time. This saves us from having to make copies of essentially identical rules on different interfaces, and is handy in a number of situations in which we want a rule to be in effect on multiple interfaces.
  • Whereas conventional firewall rules are only invoked when packets leave an interface, floating firewall rules may be invoked when traffic enters an interface (in), when it leaves an interface (out), or either direction (any).
  • In the Action drop-down menu, in addition to the PassBlock, and Reject options that are available for conventional firewall rules, there is a fourth option called Match. If this option is selected, the rule will be applied to packets matching the rule, but the pass/block status of the packets will not be affected. This option is often used for traffic shaping, as...