`
`Home |pfSense Overview
`
`Take A Tour
`of pfSense
`
`®
`
`pfSense software is a free, open source customized distribution of FreeBSD
`specifically tailored for use as a firewall and router that is entirely managed via
`web interface. In addition to being a powerful, flexible firewalling and routing
`platform, it includes a long list of related features and a package system allowing
`further expandability without adding bloat and potential security vulnerabilities to
`the base distribution.
`
`Our History
`
`The pfSense project was started in September 2004 by Chris Buechler and Scott
`Ullrich, with a growing development team. Chris is a long time contributor to the
`m0n0wall project. m0n0wall is a great embedded firewall, but one of the great things
`about its design is also a limitation to expandability. m0n0wall runs entirely from
`RAM, the entire OS and all applications are loaded into RAM at boot time. This is a
`great design for embedded systems, for performance and reliability reasons. However
`m0n0wall is not capable of being installed into a normal file system on a hard drive.
`Hence many desirable functions can't be reasonably implemented.
`
`See this blog post for background on the name behind pfSense software.
`
`Rubicon Communications, LP Ex. 1030
`Rubicon Communications, LP vs. LEGO A/S
`IPR2016-01187
`
`1
`
`
`
`Legal
`
`pfSense is Copyright 2004-2016 Rubicon Communications, LLC (Netgate)
`Current logo is Copyright 2005-2016 Electric Sheep Fencing, LLC
`
`pfSense is a federally registered trademark of Electric Sheep Fencing LLC. Any
`unauthorized use of this trademark is prohibited by state and federal law and
`international treaties. Refer to our Trademark Usage Guidelines for how to properly
`use the marks.
`
`All rights reserved.
`
`LICENSE
`
`pfSense is open source and distributed under the Apache 2.0 license.
`
`Contributor License Agreements
`
`We look forward to your patches. Before we can accept them, you must sign and
`submit (via electronic submission, postal mail, email) a Contributor License
`Agreement. The preferred method is to electronically submit an Individual
`Contributor License Agreement (ICLA) or Corporate Contributor License Agreement
`(CCLA) at the pfSense portal or if you need, you can send in a filled out PDF of the ICLA
`or a CCLA.
`
`The purpose of this agreement is to clearly define the terms under which intellectual
`property has been contributed to the pfSense project and thereby allow us to defend
`the project should there be a legal dispute regarding the software at some future
`time. From the individual contributor agreement: "This license is for Your protection
`as a Contributor as well as the protection of ESF; it does not change your rights to use
`your own Contributions for any other purpose."
`
`2
`
`
`
`Contact Us
`
`Sales & Customer Service
`
`To contact us with sales questions or comments, you can reach us by email at
`sales@pfsense.org or by phone at 1 (512) 900-2546.
`
`Support & Services
`
`If you have any questions, please email support@netgate.com or look over our
`support frequently asked questions.
`
`pfSense Project
`
`To contact us for submitting patches, inquiring about contributing to the project,
`notifying us of problems with any of our web sites, or any other non-support issue
`email coreteam@pfsense.org.
`
`To contact us for security issues, use security@pfsense.org.
`
`Mail Address
`
`7212 McNeil Dr #204
`Austin, TX 78729
`
`Direct Access to the pfSense Team
`Commercial Support Available
`
`3
`
`
`
`NEED TRAINING?
`
`NEED DOCUMENTATION?
`
`About Us
`
`pfSense Overview
`Features
`Careers
`Legal
`Security Information
`Contact Us
`
`Support & Services
`
`Commercial Support
`Video Library
`Documentation
`
`4
`
`
`
`Professional Services
`pfSense University
`Gold Membership
`
`How To Buy
`
`Product Family
`Direct From Netgate
`Locate A Partner
`Become A Partner
`
`Patrons
`
`Netgate
`NYI
`Become a Patron
`
`Copyright © 2004-2017 Rubicon Communications, LLC (Netgate). All Rights Reserved.
`Privacy Policy | Terms and Conditions
`
`5
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
