summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Set language early on a common place included everywhere. This fix some tar ↵Renato Botelho2015-12-142-9/+12
| | | | warnings 'Failed to set locale'
* Fix remaining copy/paste message from last commitRenato Botelho2015-12-141-1/+1
|
* Add icon on retrieving gw widgetRenato Botelho2015-12-141-1/+1
|
* Remove dead code, we only have UTF-8 todayRenato Botelho2015-12-141-60/+0
|
* Merge pull request #2219 from BBcan177/patch-1Renato Botelho2015-12-141-1/+1
|\
| * Update pfsense-utils.incBBcan1772015-12-131-1/+1
| | | | | | | | | | | | | | | | | | When installing packages, an extra line break is added by the "\r" ... echo "\r{$status}"; The $status string typically contain a trailing "\n" as required. This allows to print a message in two steps. Writing configuration... done. 1) print "Writing configuration..." 2) print "done" after the command completes.
* | fix traffic shaper tree font colorJared Dillard2015-12-131-1/+1
|/
* Merge pull request #2214 from BBcan177/patch-3Renato Botelho2015-12-131-2/+2
|\
| * Mod to Services Status WidgetBBcan1772015-12-121-2/+2
| |
* | Merge pull request #2209 from NOYB/Status-System_Logs-Sortable_TableRenato Botelho2015-12-131-24/+28
|\ \
| * | Put newest at top/bottom text with Forward/Reverse Display radio buttons for ↵NOYB2015-12-111-3/+3
| | | | | | | | | | | | better clarity and more concise section description.
| * | Correct tbody end tag.NOYB2015-12-111-1/+1
| | |
| * | Status - System Logs - Sortable TableNOYB2015-12-111-21/+25
| | |
* | | Merge pull request #2208 from ExolonDX/branch_01Renato Botelho2015-12-131-26/+23
|\ \ \
| * | | Tidy up "status_queues.php"Colin Fleming2015-12-111-26/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove duplicate BODY Tidy up BR tag correctly Add COLPSAN statement to "interface" row Wrap BGCOLOR in a STYLE statement (should really be defined as a CLASS statement) Remove FONT tag Remove NAME statement in DIV tag Use double quotes for consistency
* | | | be more conciseJared Dillard2015-12-121-1/+1
| | | |
* | | | clean up webGUI feature help textJared Dillard2015-12-121-2/+2
| | | |
* | | | remove icon- color classesJared Dillard2015-12-121-24/+0
| |_|/ |/| |
* | | remove icon colors and add text colorsJared Dillard2015-12-121-23/+7
| | |
* | | Fixed #5620 change css classes from icon- to text-Jared Dillard2015-12-125-18/+18
| | |
* | | Merge pull request #2210 from phil-davis/logsStephen Beaver2015-12-117-7/+7
|\ \ \ | |_|/ |/| |
| * | Logs filename changesPhil Davis2015-12-127-7/+7
|/ /
* | Rename of files to better match their position in the memory structureStephen Beaver2015-12-1134-240/+257
| |
* | Don't allow log specific setting to override grepreverse option.NOYB2015-12-111-2/+2
| |
* | Add few comments for clarityNOYB2015-12-111-18/+38
| | | | | | | | | | | | | | Include table header titles in raw mode (time and message). In raw mode give all horizontal space not being consumed by the time field to the message filed. Provides more space so fewer entires to consume multiple vertical line space. Change table message field header title form "Log Message" to "Message" Include a write_config description.
* | Spelling CorrectionNOYB2015-12-111-1/+1
| | | | | | | | | | s/formated/formatted/ Thanks Phil
* | Status - System Logs - Manage LogNOYB2015-12-113-27/+277
| | | | | | | | | | | | | | Build up th manage log section with options to override the "General Logging Options" settings on an individual log basis. Remove over exuberant gettext's. Set/adjust filter form field widths to be better fitting for the field types. Open/Close filter form based on filtering state.
* | link to proper license information locationJared Dillard2015-12-112-2/+2
|/
* Use default values for latencylow and losslow when they are not defined by ↵Renato Botelho2015-12-111-6/+19
| | | | user. Reported by grandrivers at https://forum.pfsense.org/index.php?topic=103818.msg579069#msg579069
* Convert latency to ms before use it to compare with value defined in gateway ↵Renato Botelho2015-12-111-3/+3
| | | | conf
* Merge pull request #2207 from phil-davis/patch-2Renato Botelho2015-12-111-31/+89
|\
| * Gateway advanced parameter validationPhil Davis2015-12-111-31/+89
|/ | | | | | | | | | | | | This does what I can think of so far: 1) Make sure low latency < high latency, low loss < high loss 2) Loss interval must be at least latencyhigh otherwise every packet that was high latency would be counted as lost before it came back. (see note below) 3) averaging time period must be at least 2 times probe interval - it is not much of an "average" if it averages less than 2 probes :) 4) alert interval must be at least probe interval - there is no point recalculating the average latency and loss more often than once every probe interval. 5) Criteria for showing or hiding the advanced options on page load fixed up to account for all the fields now in the advanced section. 6) Additional information - I have written some stuff that I think is now helpful. Note: Currently the default loss interval is 500 and latencyhigh is also 500. This makes no sense to me. If a probe comes back in > 500ms then the thread that is waiting for the reply will have given up (loss interval has expired). So any packets with an RTT > 500ms will be considered lost. Therefore there will be no packets recorded with an RTT > 500ms. Therefore the average latency can never exceed latencyhigh. It seems to me that "loss interval" needs to be reasonably higher than "latencyhigh" in any sensible configuration. Thoughts?
* Change quality rrd delay variable again to match same unit apinger used so ↵Renato Botelho2015-12-111-1/+1
| | | | we don't break current database. Ticket #5624
* Fix parameter orderRenato Botelho2015-12-111-2/+2
|
* Add template to rrd updateRenato Botelho2015-12-111-2/+2
|
* Actually call bc to do the math, ticket #5624Renato Botelho2015-12-111-1/+1
|
* Convert delay to milliseconds for RRD graph, ticket #5624Renato Botelho2015-12-111-0/+3
|
* Merge pull request #2206 from phil-davis/r002Renato Botelho2015-12-114-13/+13
|\
| * Random stuff in tools folder treePhil Davis2015-12-114-13/+13
| | | | | | | | White space and text or comment typos only - nothing functional.
* | Remove unused function create_gateway_quality_rrd()Renato Botelho2015-12-111-35/+0
| |
* | Implement RRD gateway qualiry support after move to dpinger. Fixes #5624Renato Botelho2015-12-111-0/+37
| |
* | Use $ values for vardb_pathRenato Botelho2015-12-111-5/+5
|/
* Merge pull request #2205 from phil-davis/patch-2Renato Botelho2015-12-111-1/+5
|\
| * Only ask Proceed with upgrade question oncePhil Davis2015-12-111-1/+5
| | | | | | | | | | | | | | | | | | | | | | On nanoBSD there is a "Proceed with upgrade?" question warning about the duplicate slice. After answering "y" to that, the system does the duplicate slice, which takes some minutes. Then it asks again "Proceed with upgrade?" after displaying all the packages it will install. That is a bit annoying at the console - I answer "y" and go off to make a cup of tea, only to come back and find that it is waiting asking again. On nanoBSD a reboot is known to be required anyway, because even if it is some little package that gets upgraded, and not the core OS, the partition is always switched. So we can say that in the first warning and then skip asking "Proceed with upgrade?" a second time. What do you think? Should it ask a 2nd time after displaying the packages to be installed? Or is it OK to skip that confirmation prompt? Also, I moved the call to setup_nanobsd_env inside the "if nanobsd" - it worked like it was because setup_nanobsd_env returns without doing anything if the system is not nanobsd, but it just looked odd and there seems no point calling it when not nanobsd.
* | Merge pull request #2185 from phil-davis/factory-default-interfaces-20151208Renato Botelho2015-12-112-0/+63
|\ \
| * | Automatically choose some interface combinationsPhil Davis2015-12-082-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | on factory default boot. This allows the system to switch interfaces from the newer ones in the default config (e.g. em0 em1) back to the interfaces used by: Alix - vr1 vr0 APU - re1 re2 that match the WAN and LAN labels printed on many existing devices. It means these devices can boot the default config and this will automatically detect that there is no em0/em1 and will instead select whatever exists out of vr1/vr0 or re1/re2. This avoids the user having to use the serial cable to do interface assignment when starting a brand new image, or when resetting to factory defaults. It could easily be extended to other common interface combinations. For me, this (or similar) would be very beneficial. At remote sites it is really good if it is possible to do reset to factory defaults, or put a fresh CF/SD card in, and the system boots without needing to connect a serial cable and do interface assignment.
* | | Merge pull request #2182 from NOYB/write_config_only_optionRenato Botelho2015-12-111-1/+7
|\ \ \
| * | | Write Config Only OptionNOYB2015-12-071-1/+7
| | | | | | | | | | | | | | | | Add write_config function option to only write the config. Sometimes syncing firewall is not necessary or desirable. ex: changing log display options.
* | | | Merge pull request #2191 from phil-davis/patch-3Renato Botelho2015-12-111-13/+3
|\ \ \ \
| * | | | Internationalize console reboot scriptPhil Davis2015-12-101-13/+3
| | | | | | | | | | | | | | | | | | | | This file previously had to have a space after "Do you want to proceed [y|n]?" to make the prompt for user input nice. That made it one of the few exceptions to the code style guide, where lines are not supposed to have blank space at the end. Might as well have 1 less exception to the rule by internationalizing it, which removes the literal "EOD" echo output stuff.
OpenPOWER on IntegriCloud