Book Image

Mastering pfSense - Second Edition

By : David Zientara
Book Image

Mastering pfSense - Second Edition

By: David Zientara

Overview of this book

pfSense has the same reliability and stability as even the most popular commercial firewall offerings on the market – but, like the very best open-source software, it doesn’t limit you. You’re in control – you can exploit and customize pfSense around your security needs. Mastering pfSense - Second Edition, covers features that have long been part of pfSense such as captive portal, VLANs, traffic shaping, VPNs, load balancing, Common Address Redundancy Protocol (CARP), multi-WAN, and routing. It also covers features that have been added with the release of 2.4, such as support for ZFS partitions and OpenVPN 2.4. This book takes into account the fact that, in order to support increased cryptographic loads, pfSense version 2.5 will require a CPU that supports AES-NI. The second edition of this book places more of an emphasis on the practical side of utilizing pfSense than the previous edition, and, as a result, more examples are provided which show in step-by-step fashion how to implement many features.
Table of Contents (15 chapters)

Configuring traffic shaping in pfSense

Traffic shaping in pfSense can be a challenge to configure, partially because of the number of options and the complexity of the shaper rules and shaper queues. It is generally recommended that you begin with the web GUI's traffic shaper wizard. You can access the wizard by clicking on Firewall | Traffic Shaper and then clicking on the Wizards tab. There are currently two wizards available: Multiple Lan/Wan and Dedicated Links. Multiple Lan/Wan can be used in a variety of scenarios in which there are one or more LAN-type interfaces, and one or more WAN interfaces. Dedicated Links, on the other hand, is designed for cases in which specific LAN/ WAN pairings do not mix with other traffic. For example, users on one subnet may have a different internet connection than users on another subnet. Therefore, there are two separate WAN interfaces...