| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
| |
bandwidthd explodes on using single quotes in config... sigh
|
| |
|
|
|
| |
These are dealt with by uninstall_package() and delete_package_xml() from pkg-utils.inc.
|
|
|
| |
Fix indentation.
|
|
|
| |
Only write upgraded config if there was something actually upgraded.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Update copyright headers
- Fix code style and indentation
- Provide input validation for most of the configuration options
-- Check for IPv4 configured on selected interfaces
-- Check for PPPoE type interfaces
-- Require relevant options to be filled in when PostgreSQL is enabled (also check that the hostname is valid)
-- Require sane numeric input for graphs options
-- Limit Sensor ID to sane chars
- PostgreSQL DB password is now base64-encoded to deal with special chars and not break config.xml
- The filtering moved to advanced options, also base64-encoded
- The stats interface(s) are now a multiselect instead of asking users to type subnets directly
- Upgrade function provided to preserve the old settings
- Use {start,stop,restart}_service() functions instead of calling the rc script directly
- Probably other small things...
|
|
|
|
|
|
|
|
| |
- Fix copyright header and indentation
- Reorder the GUI and split into logical sections
- Improve descriptions
- Move the menu entry to Diagnostics section, to match other similar packages (ntop, ntopng, darkstat etc.)
- Add another menu entry to access bandwidthd graphs directly from menu
- Add input validation
|
|
|
| |
This function does nothing but return.
|
| |
|
|
|
|
| |
Thanks to charliem https://forum.pfsense.org/index.php?topic=78175.msg428321#msg428321 for this patch to make bandwidthd find the right library environment on 2.2 full install.
I also tested on 2.1.4 full install in a VM, as this change does change the way bandwidthd is run in the 2.1.n series - it works.
|
| |
|
|
|
|
|
| |
I installed bandwidthd on a 2.2 nanoBSD Alix2D13. The new path to the executable has an extra "/local" in it, and it needs an LD_LIBRARY_PATH to know where to find some of its libraries.
With this, it installs, runs and comes up again after a reboot.
These changes should all be backward-compatible and make no difference to what happens when installed on older 1.2 2.0 and 2.1 series systems.
|
|
|
|
|
|
| |
- Replace http by https
- *.pfsense.com -> *.pfsense.org
- www.pfsense.org/packages/config -> packages.pfsense.org/packages/config
|
| |
|
|
|
|
|
| |
Forum: http://forum.pfsense.org/index.php/topic,68477.0.html
Allows users to put "0" in various fields and have it come through validly into the bandwidthd conf file.
Previously bare "0"s would appear in the conf file, which were wrong.
|
| |
|
| |
|
|
|
|
| |
This helps some people whose browser does not find index.html automagically, and does not harm anything for others.
http://forum.pfsense.org/index.php/topic,49165.msg362705.html#msg362705
|
| |
|
|
|
|
|
| |
Check for the case where a user specifies the interface subnet to listen on in the "subnet" box, which is actually not required. In this case, do not put the subnet into the config twice. It fixes a GUI data entry confusion that is reported from time to time in the forum, e.g.
http://forum.pfsense.org/index.php/topic,49165.msg320801.html#msg320801
http://forum.pfsense.org/index.php/topic,66354.0.html
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Improve the documentation of options on the GUI, including what happens when output_cdf is on.
|
| |
|
|
|
| |
legend.gif and logo.gif were missing from the report/graph page. They need to be put in /var/bandwidthd/htdocs
|
|
|
| |
The Access Bandwidthd tab takes the user completely out of the pfSense WebGUI interface when clicked. This behaviour is not user-friendly. IMHO it is better to open the Bandwidthd UI in a new tab.
|
|
|
| |
Make the code that starts bandwidthd check for the correct dirs and symlinks, leave them alone if they are already there, and put them in place if they are missing. This fixes some places where some commands were generating "already exists" warnings, and generally makes sure that whatever someone does at the command line to mess with bandwidthd dirs and links, they will be put back when bandwidthd starts.
|
|
|
| |
Make bandwidth on nanobsd write graph files and cdf log files to /var/bandwidthd rw memory filesystem, so it can run with /usr mounted read-only
|
|
|
|
| |
The split function is deprecated in PHP 5.3. For this simple use, the explode function does the same thing.
http://forum.pfsense.org/index.php/topic,55187.0.html
|
|
|
| |
and default values, and some field description text.
|
| |
|
| |
|
|
|
|
|
| |
future versions of pfsense.
Previously, promiscuous mode was always stuck on - the bandwidthd default is "promiscuous true" and the code assumed the default was "false". This fix always specifies promiscuous mode explicitly so that it does not matter what the default is, the setting will always follow whatever the user has selected in the GUI check box. See forum thread http://forum.pfsense.org/index.php/topic,50878.0.html
|
| |
|
|
|
|
| |
can't specify a proper custom config path.
|
|
|
|
| |
generating an invalid configuration file.
|
| |
|
| |
|
| |
|
| |
|
| |
|