| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Add write_config function option to only write the config. Sometimes syncing firewall is not necessary or desirable. ex: changing log display options.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
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.
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | | |
This is another one that was using echo EOD stuff and needed a space after "Do you want to proceed [y|n]?".
|
|\ \ \ \ \
| |_|_|_|/
|/| | | | |
|
| |/ / /
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
| | | | | |
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
The packet loss thresholds must still be in % ? milliseconds does not look valid.
Other things are minor formatting.
|
|\ \ \ \ \ |
|
| |/ / / / |
|
|/ / / / |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \ |
|
| | | | | |
|
|/ / / / |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixed #5612
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
|\ \ \ |
|
| | | | |
|
|\ \ \ \ |
|
| |/ / / |
|
|\ \ \ \ |
|
| |/ / / |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/
|/|
| | |
Just a few extra words to put in this text, while I am reading it and waiting for the upgrade to complete.
|