Wiki source for ReBrandingSupport
=====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 referring to the term re-brand, we mean to replace the current product name (here: pfSense) by another name (e.g. MyFirewall).
The best way to accomplish this is to pay the developers to do it for you, because if you haven't done it before, it's extremely time consuming where we can get it done quickly. See the [[https://portal.pfsense.org/index.php/reseller-subscription
Reseller Subscription]].
pfSense uses a variable $g['product_name'] for the various instances of "pfSense". This variable is defined in /etc/inc/globals.inc and should contain the name which you 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-branded solution. Those files are listed below.
- /usr/local/www/javascript/sajax.js
- /usr/local/www/wizards/*
- /etc/motd
- /etc/rc (ascii art: you may wish to add your own ascii art file to /etc/ascii-art/your-file.txt)
- /tools/installer/conf/pfSense.lua (if you want the installer to display your product name)
- i386 boot files (boot loader, etc)
You really 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 MS DOS line endings - CR LF that is).
Also check out common overlays that can be used to automatically customize the theme and overwrite pfSense specific files. http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/tools/builder_scripts/builder_profiles Check pfsense_local.sh from pfdns/ for more information on how these overlays work. Also see this blog post which is related. http://blog.pfsense.org/?p=244
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.
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 referring to the term re-brand, we mean to replace the current product name (here: pfSense) by another name (e.g. MyFirewall).
The best way to accomplish this is to pay the developers to do it for you, because if you haven't done it before, it's extremely time consuming where we can get it done quickly. See the [[https://portal.pfsense.org/index.php/reseller-subscription
Reseller Subscription]].
pfSense uses a variable $g['product_name'] for the various instances of "pfSense". This variable is defined in /etc/inc/globals.inc and should contain the name which you 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-branded solution. Those files are listed below.
- /usr/local/www/javascript/sajax.js
- /usr/local/www/wizards/*
- /etc/motd
- /etc/rc (ascii art: you may wish to add your own ascii art file to /etc/ascii-art/your-file.txt)
- /tools/installer/conf/pfSense.lua (if you want the installer to display your product name)
- i386 boot files (boot loader, etc)
You really 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 MS DOS line endings - CR LF that is).
Also check out common overlays that can be used to automatically customize the theme and overwrite pfSense specific files. http://cvs.pfsense.com/cgi-bin/cvsweb.cgi/tools/builder_scripts/builder_profiles Check pfsense_local.sh from pfdns/ for more information on how these overlays work. Also see this blog post which is related. http://blog.pfsense.org/?p=244
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.
