Pfsense
Features
pfSense most all the features in expensive commercial firewalls, and in many other cases. The following is a list of functions available in pfSense 1.2 release. All things are possible, the web interface, without anything from the command line.
In addition to these features, this page contains all the limitations of the system which we are aware. From our experience and expertise has helped thousands of our users, we understand very well the software can and can not do. Each package has a limit. Where we differ from most, is communicated clearly to them. We are also happy to help people to remove the limit. Many of the restrictions in many commercial and open source firewall. 1.2 is defined in the code, the next major release.
Firewall
* Filtering by IP source and destination IP, source port and destination for the TCP and UDP traffic
* You can restrict connections to each base line
* PfSense using p0f, an advanced passive OS / tools for detection of fingerprints network that you can start the filter system of connection. To enable machines to Linux and FreeBSD on the Internet, but block Windows machines? pfSense can do (among many other possibilities) by passively detecting the operating system.
* Ability to access or less access to traffic matching each rule.
* Policy routing highly flexible as possible by choosing a gateway to baseline (for load balancing, failover, multiple WAN, etc.)
* Nicknames can group and IP network ports. In this way, the firewall rules clear and easy to understand, especially in environments with multiple public IP addresses and multiple servers.
* Layer 2 transparent firewall state - can bridge interfaces and filter traffic between them, even for less than an IP-firewall (even though you probably want an IP address for management purposes).
* Packet normalization - Description stain pf documentation - " 'spot' is the normalization of the package so that no ambiguity in the interpretation of the final destination of the package. The scrub directive also reassembles fragmented packets, protecting some systems by a particular form of attack, and drops TCP packets invalid flag combinations.
or pfSense Standard
Can I disable or, if necessary. This leads to problems in some NFS implementations, but is safe and is required in most buildings.
* Disable filter - you can change the whole filter firewall if you want a pure murder pfSense router.
Table of State
The status table of the firewall maintains information about your network connection open. pfSense is a stateful firewall by default all rules are stateful.
Most firewalls lack the ability to precisely the status of your table. pfSense has many characteristics of granular control that your table, because the ability of PF OpenBSD.
* Table size was adjustable - there are several buildings pfSense production with the help of several hundreds of thousands of one state. The default table size is 10,000, but this increased to fly to the desired size. Every state is about 1 KB of RAM, in order to recall the memory usage when sizing your booth table. It is not set arbitrarily high.
* On a general basis for:
Limit or simultaneous client connections
Boundaries of a State or host
the new limit of connections per second
Define or state timeout
Specify the type or state
* Nature of State - pfSense offers multiple possibilities for the treatment of the state.
or hold the position - Works on all protocols. Standard for all policies.
or weaken state - works only with TCP. pfSense will generate strong first set of numbers (ISNs) on behalf of the host.
or Synproxy state - proxies incoming TCP connections for the protection of servers spoofed TCP SYN flood. This option includes the functionality of keep state and modulate state combined.
or No - Do not hold items in a state of traffic. E 'desirable, very rarely, but is available because it can be useful in certain limited circumstances.
* State table optimization options - PF offers four options for optimizing the tables of state.
or normal - the default algorithm
or high-latency - Useful for high latency links such as satellite links. Expires idle connections later than normal.
or aggressive - Expires idle connections more quickly. Better use of hardware, but can drop legitimate connections.
or conservative - trying to avoid dropping legitimate connections at the expense of increased memory and CPU.
NAT (Network Address Translation)
* Including the port range forward and use more public IP addresses
* 1:1 Nat for individual IP addresses or entire subnets.
* The exit Nat
Nat default or all outgoing traffic to IP-Wan. When several events, the default settings Nat outgoing traffic on the WAN interface IP.
Advanced outbound nat This is a standard behavior with disabilities, and allows the creation of very flexible Nat (or NAT) policy.
* Nat reflection - in some configurations, Nat thought possible, so that it can be used by public IP from internal network.
Nat Limits
PPTP and GRE * Limits - The situation on the track for pf GRE protocol can only track for a session public IP to server. This means that if you use PPTP VPN connections, but only one machine can simultaneously connect to a PPTP server on the Internet. A thousand of machines that can simultaneously connect to a PPTP server thousand, but only one at a time on a single server. The only solution is to use multiple public IP addresses on the firewall, one for each client, or to use multiple public IP addresses to external PPTP server. This is not a problem in other types of VPN connections. A solution is currently being developed.
* SIP Limits - By default, all TCP and UDP traffic, with the exception of SIP and IPsec earned the source port rewrite. More information about them is the static port documentation. Since this source port is like rewriting pf track one IP connection to remote server, and most of all SIP traffic uses the same source port, only one SIP device can connect simultaneously to a single server on the Internet. Unless your SIP devices to operate the source port rewrite (most are not), you can have multiple phones on a dedicated server, without using a public IP per device. Sipproxd The package now offers a solution to this problem in pfSense 1.2.1 and later.
* Nat reflection boundaries - Nat reflection can only use the port range of less than 500 ports and can not use the 1:1 Nat host.
Redundancy
OpenBSD carp for hardware failover. Two or more firewalls can be configured as a failover. If the interface is not the first or the primary goes offline entirely, the secondary is active. PfSense also features synchronization of configuration, so that configuration changes to automatically synchronize the primary and the second firewall.
pfsync ensures that the firewall state table is replicated to all failover configured firewalls. This means your existing connections are maintained in the event of bankruptcy, which is crucial to avoid network failures.
Limits
* Only works with static public IP does not work with DHCP, PPPoE, PPTP or Bigpond types (WAN has been resolved in a future release)
* Requires a minimum of three public IP addresses (they are resolved in a future release)
* Backup firewall idle (active-passive failover), an active active clustering is possible at this time.
* Failover is not instantaneous, which takes about 5 seconds to switch from a back-up control host. During this time no traffic, but the current situation is connected after the failover is complete. 5, second failure when failure is not evident in most environments.
Load Balancing
Outbound Load Balancing
Load balancing outgoing is used with multiple WAN connections for load balancing and failover capabilities. The traffic will be routed to the gateway or load balancing pool on a per firewall rule base.
Load balancing input
Load balancing input is used to distribute the load across multiple servers. It is often used on web servers, mail servers, and others. The server does not respond to ping requests or TCP port connections are removed from the pool.
Limits
* Pantay distributes load between all servers available - not on a non-uniform load between the servers at this time.
* Only check if the server responds to pings or TCP port connections. Unable to verify that the server returns the contents valid.
VPN
pfSense offers three options for VPN connectivity, IPsec, PPTP and OpenVPN.
IPsec
IPsec connects to any device supporting standard IPsec. This is usually used for sites on the site pfSense connection to other facilities, other open source firewall (m0n0wall, etc.), and most all commercial firewall solutions (Cisco, Juniper, etc.). This can also be used for connectivity to mobile clients.
Limits
* NAT-T is not supported, which means that customers of mobile phones behind NAT is not supported. The pfSense limits the usefulness of mobile customers IPsec. Openvpn or PPTP is a better solution.
* Only one end of an IPSec tunnel, a dynamic IP address.
* Some of the more advanced features of ipsec-tools is not yet supported, including DPD, xauth, NAT-T, and others.
Openvpn
Openvpn is a flexible, powerful SSL VPN solution that supports a wide range of client operating system. Openvpn See the website for more details about its capabilities.
Limits
* Not all options of openvpn are still supported. Support for nearly all transmission openvpn will be included in next release.
* Filter openvpn traffic is possible. Support for them is 2.0.
PPTP Server
VPN PPTP is a popular option for almost all OS have built in PPTP client, with the release of Windows from Windows 95 OSR2. See the Wikipedia articles for more information on PPTP.
The PPTP pfSense server can use a local user database or RADIUS server for authentication. Radius accounting is supported. Firewall policy to control traffic initiated by PPTP interface PPTP client.
Limits
* Due to restrictions on Nat pf, when the PPTP server is enabled, the PPTP client can not use the same public IP for outbound PPTP connections. This means that if you only have one public IP, and use the PPTP server, PPTP clients within your network does not work. Work on the use of public transport Advanced outgoing IP for your internal customers Nat. See also limited PPTP Nat on this page.
PPPoE server
pfSense offers a PPPoE server. For more information about PPPoE, see the Wikipedia entry. A database of local users can use for authentication and RADIUS authentication with optional accounting is supported.
Reporting and monitoring
RRD graphs
The RRD graphs pfSense maintain historical information on the following.
* Using the CPU
* Total flow
* Firewall Member
* Individual throughput for all interfaces
* Packets per second for all interfaces
* Wan interface gateway (s) response times Ping
* Traffic Shaper traffic code in the design of the system allowed
Real-time information
History is important, but sometimes it is important to see in real time.
SVG graphs show that the flow in real time for each interface.
Traffic Shaper for users, state -> Queues screen provides a real-time display of queue usage using AJAX updated gauges.
The other first page includes AJAX meters for displaying real-time processor, memory, swap and disk usage, the size and scale.
Dynamic DNS
A dynamic DNS client is included, allowing you to register your public IP to a number of dynamic DNS service.
* DynDNS
* DHS
* DyNS
* EasyDNS
* No-IP
* ODS.org
* Zone Change
A client is also available to the RFC 2136 dynamic DNS updates, for use with the DNS server to bind the support for this type of side effect.
Limits
* Only works on the main Wan Interface - Support multi-Wan is available in version 2.0.
* You can update a single account with a service provider. 2.0 uses unlimited account.
* Only works if pfSense is the public IP assigned to one of its interfaces. If you have a modem that gets your public IP and pfSense is a private IP, private IP address is registered with the provider. 2.0 A, with an option for your public IP genuine law and register.
Prisoners Home
Captive portal allows you to force authentication or redirection to a page by clicking on the network access. This is usually used in networks of hot spots, but is also widely used in corporate networks for an additional level of security or for Internet access without wires. For more information on captive portal technology in general, see the Wikipedia article on the subject. The following is a list of the features of pfSense captive portal.
* Maximum simultaneous connections - Limit the number of connections to the same portal for client IP. This feature prevents the rejection of services from client PCs sending network traffic on several occasions, without checking or clicking on the splash page.
* Idle timeout - Disconnect clients idle for more than the specified number of minutes.
* Hard timeout - Force a connection to all customers after the specified number of minutes.
* Access pop-up window - Option of a pop-up window to enter shutdown.
* URL Redirect - after clicking on the control through the captive portal, users can be redirected to the URL specified strongly.
* MAC filtering - pfSense using standard filters MAC addresses. If you have a subnet behind a router on a captive portal interface is enabled, all machines behind the router is enabled after a user is permitted. MAC filtering can be disabled for the event.
Authentication options - There are three authentication options available.
or No authentication - This means that only the user clicks through your portal page without credentials.
local user or manager - A local user database is configured and used for authentication.
or RADIUS authentication - This is the authentication method your ISP for businesses and groups. It can be used to extend Microsoft Active Directory and many other RADIUS servers.
* Ray of power
or forced re-authentication
or send Accounting Update
MAC radius or captive portal authentication to authenticate to a RADIUS server using the client MAC address of the user and password.
Create a redundant configuration or RADIUS server.
* HTTP or HTTPS - The portal page can be configured to use an HTTP or HTTPS.
* Pass-through IP addresses and MAC - MAC and IP addresses are white-by-pass the portal. Each machine carries out the Nat circumvented then the answer is no traffic hitting the portal. Want to exclude some machines for other reasons.
* File Manager - Allows you to upload images for use on your portal page.
Limits
* You can have only one interface simultaneously.
* "Reverse" portal, ie the acquisition of traffic from the Internet and entering your network, you can not.
* Only fully MAC and IP addresses are excluded from the portal, not the individual protocols and ports.
* It is not compatible with multi-Wan policy. We hope that this solution is 2.0.
DHCP Server and Relay
pfSense includes both DHCP server and linking functionality