summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
| * | 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.
* | | | | Merge pull request #2192 from phil-davis/patch-4Renato Botelho2015-12-111-13/+3
|\ \ \ \ \
| * | | | | Internationalize console halt 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.
* | | | | Merge pull request #2193 from phil-davis/patch-5Renato Botelho2015-12-111-15/+4
|\ \ \ \ \
| * | | | | Internationalize console reset to factory defaultsPhil Davis2015-12-101-15/+4
| |/ / / / | | | | | | | | | | This is another one that was using echo EOD stuff and needed a space after "Do you want to proceed [y|n]?".
* | | | | Merge pull request #2194 from phil-davis/patch-6Renato Botelho2015-12-111-27/+12
|\ \ \ \ \ | |_|_|_|/ |/| | | |
| * | | | Internationalize more of config.console.incPhil Davis2015-12-101-27/+12
| |/ / / | | | | | | | | | | | | This code is a whole mix of some palces that use gettext() and other chunks of output that are hardcoded text between "EOD" markers. I have got rid of the "EOD" blocks where there is a question asked - those needed to have a space at the end of the question. To meet code style guide it is easy if questions are all in their own echo statements and the space " " can be visibly coded in.
* | | | Merge pull request #2195 from phil-davis/patch-8Renato Botelho2015-12-111-10/+0
|\ \ \ \
| * | | | Remove bonus debug from filter_log.incPhil Davis2015-12-101-10/+0
| |/ / / | | | | | | | | These debug blocks look like they should not be in production. if 'debug' is turned on, then they would always log_error() and return for all log lines, even good ones.
* | | | Merge pull request #2201 from phil-davis/patch-10Renato Botelho2015-12-111-1/+1
|\ \ \ \
| * | | | apinger loss_interval array key namePhil Davis2015-12-111-1/+1
| | | | |
* | | | | Merge pull request #2204 from phil-davis/patch-13Renato Botelho2015-12-111-4/+4
|\ \ \ \ \
| * | | | | dpinger help textPhil Davis2015-12-111-4/+4
| |/ / / / | | | | | | | | | | | | | | | The packet loss thresholds must still be in % ? milliseconds does not look valid. Other things are minor formatting.
* | | | | Merge pull request #2202 from phil-davis/patch-11Renato Botelho2015-12-111-4/+4
|\ \ \ \ \
| * | | | | Fix GW setting names in upgrade_configPhil Davis2015-12-111-4/+4
| |/ / / /
* | | | | gwlb array key typo loss_intervalPhil Davis2015-12-111-3/+3
|/ / / /
* | | | Write upgrade config to replace apinger by dpinger, it should fix #5624Renato Botelho2015-12-103-2/+52
| | | |
* | | | Ticket #5624: Welcome dpinger!Renato Botelho2015-12-109-383/+260
| | | |
* | | | Add rc.gateway_alarm scriptRenato Botelho2015-12-101-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | dpinger always pass 3 parameters to alert_cmd, what can make pfSctl confuse, This script will be called by dpinger when alarm goes on or off, then it's going to call pfSctl
* | | | Fix indentRenato Botelho2015-12-101-3/+3
| | | |
* | | | Simplify logic and break some long lines, no functional changesRenato Botelho2015-12-101-99/+78
| | | |
* | | | Remove calculated optionsRenato Botelho2015-12-101-87/+0
| | | |
* | | | Change apinger_default to dpinger_defaultRenato Botelho2015-12-101-32/+32
| | | |
* | | | Merge pull request #2199 from heper/patch-2Stephen Beaver2015-12-101-0/+2
|\ \ \ \
| * | | | fix #5563heper2015-12-101-0/+2
| | | | |
* | | | | Fixed #5602 by dynamically updating hte help text based on the cert selected.Stephen Beaver2015-12-103-11/+26
|/ / / /
* | | | Code style and white space in etcPhil Davis2015-12-1029-100/+131
| | | |
* | | | Fix #5598 - Nanobsd upgrade fails on GUIRenato Botelho2015-12-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | When -p is used on nanobsd, progres socket must be created on secondary partition (chroot_dir) otherwise pkg, that runs with -c chroot_dir, will not be able to find UNIX socket to connect and send events
* | | | Track nc PID and kill it on _exit()Renato Botelho2015-12-101-0/+9
| | | |
* | | | Fixed #5617Stephen Beaver2015-12-104-6/+11
| | | | | | | | | | | | | | | | Fixed #5612
* | | | Use the _title var to make the widget titlePhil Davis2015-12-103-31/+42
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | Each widget has an include file that already has the required widget title in a var like $dyn_dns_status_title $carp_status_title etc. Use that var to set the displayed title of the widget, rather than the stuff that was capitalizing the file name and then having a list of special cases... This meant the loop that includes the widget include files had to be moved higher up in the code.
* | | fix input colorJared Dillard2015-12-091-1/+1
| | |
* | | Merge pull request #2190 from phil-davis/r1Stephen Beaver2015-12-0910-90/+121
|\ \ \
| * | | Widgets format and white spacePhil Davis2015-12-0910-90/+121
| | | |
* | | | Merge pull request #2189 from phil-davis/patch-3Stephen Beaver2015-12-091-1/+1
|\ \ \ \
| * | | | OpenVPN Widget fix column header textPhil Davis2015-12-091-1/+1
| |/ / /
* | | | Merge pull request #2188 from phil-davis/log-breadcrumbsStephen Beaver2015-12-093-5/+4
|\ \ \ \
| * | | | Standardize Firewall Logs breadcrumbsPhil Davis2015-12-093-5/+4
| |/ / /
* | | | Interface Stats Widget make rows standard sizePhil Davis2015-12-091-1/+1
|/ / / | | | | | | | | | | | | | | | | | | The rows of data were taller than expected, and the name "Packets In", "Packets Out" etc. in the left column did not line up exactly horizontally with the numbers in the other columns. Seems to be because the "name" column was a "th" tag. If it is just "td" like the numbers then everything lines up and the row height is less (it then looks the same as other widgets that have this style of table). I put in the bold tag to keep the "Packets In" "Packets Out"... names bold. Is there some other fancy way that should be done with styles... somewhere, or is hardcoding a "b" tag OK? Note: This would also resolve the comments in forum topic https://forum.pfsense.org/index.php?topic=103605.0 - that is talking about the Interface Statistics Widget row spacing in 2.2.5 - where the rows are also taller than those on other widgets. Of course the poster of that thread would have to go to 2.3 to get the benefit here.
* | | fix widget header linksJared Dillard2015-12-081-5/+4
| | |
* | | change alert colors to match paletteJared Dillard2015-12-082-6/+34
| | |
* | | Added status page links to widget titlesStephen Beaver2015-12-082-3/+19
| | |
* | | Fix field description/name display of select_source package fields.jim-p2015-12-081-3/+3
| | |
* | | Fixed #5540Stephen Beaver2015-12-082-17/+43
| | |
* | | Create the required number of rows for NTP time serversPhil Davis2015-12-081-2/+2
| | | | | | | | | | | | | | | | | | | | | depending on how many are already defined in the config, making sure to always have a minimum of 1. Also I used the constant NUMTIMESERVERS that was defined up the top of this file to control the loop that limits the number saved to 10. Note: There also needs to be a limit on the number of rows of time server data allowed to be added - at the moment you can keep pressing the Add button and enter loads of them, only the first 10 are saved.
* | | pfSense-upgrade script textPhil Davis2015-12-081-3/+3
| |/ |/| | | Just a few extra words to put in this text, while I am reading it and waiting for the upgrade to complete.
OpenPOWER on IntegriCloud