How to Re-Brand the pfSense Software

Note: The information contained herein is meant for developers who want to create their own custom pfSense ISO image.

What does it mean to re-brand a software or any kind of product? Basically if refereing to the term re-brand, we mean to replace the current product name (here: pfSense) by another name (e.g. fooBar).

Replacing the pfSense manually is kind of daunting because the string occures in many files. To solve this issue the CVS HEAD version of pfSense introduces a variable $g['product_name']. This variable is defined in /etc/inc/globals.inc and should contain the name which u are going to use to replace the default 'pfSense' name.

Although, there a a few files which need to be edited manually if you do want a 100% re-branding solution. Those files are listed below.

• /etc/rc
• /etc/rc.firmware_auto
• /etc/rc.initial
• /etc/rc.reboot
• /etc/rc.shutdown
• /usr/local/www/javascript/sajax.js
• /etc/motd
• /etc/rc (ascii art: u may wish to add your own ascii art file to /etc/ascii-art/your-file.txt)
• /scripts/lua_installer
• /tools/installer/conf/pfSense.lua (if you want the installer to display your product name)

You realy should be aware of the fact, that some of the files mentioned above are important files required to run the pfSense system. So make sure you don't mess with them (i.e. use an appropriate editor and do not introduce M$ DOS line endings - CR LF that is).

Though pfSense is based on a BSD license which allows you to basically do anything with the code as long as you follow the license it is suggested to support the project with donations in case you sell solutions based on pfSense.

Also keep in mind that the pfSense logo and the name pfSense is not released under the BSD license. Usage in any commercial context is strictly prohibited without prior written consent of Scott Ullrich or Chris Buechler. Email coreteam@pfsense.com for further information.