| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
| |
is_unqualified_hostname as well."
This reverts commit 3d5fb131796ba6d9c5d53efe77080d7ddb334f22.
|
| |
|
|
|
|
|
| |
Fixed a bug regarding a leading space in $ZoneID that causes an AWS 505 error. Also adds support for updating DNS if TTL changes.
(cherry picked from commit a4bda7563136a7b47a1d090cededdb1b1a076019)
|
|
|
|
| |
Ticket #6184
|
|
|
|
| |
information widget
|
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 09c7fae46d2757815c1e4e5ead7c9896783e7013)
|
|
|
|
|
|
|
| |
- Uninstall all packages on current system before upgrade using
pre_upgrade_command script
- Create a file containing all packages previously installed and
reinstall them on first boot after upgrade
|
|
|
|
| |
upgrade or config restore. Fixes #6180
|
| |
|
|
|
|
| |
(cherry picked from commit e1f5381f4ecae20922a379b75820af1c9e57927e)
|
| |
|
|
|
|
| |
Similar thing to https://github.com/pfsense/pfsense/commit/13dab3538fe8b6c1688142c89a017520ad0aaac6 should be done here in upgrade_130_to_131()
|
| |
|
|
|
|
| |
S.M.A.R.T. actions in Hyper-V guests. Ticket #6147
|
| |
|
| |
|
|
|
|
| |
#6222
|
| |
|
| |
|
| |
|
|
|
|
| |
Remove these cron jobs on full install if not using ramdisk.
|
| |
|
|
|
|
| |
(cherry picked from commit 69b8328d8596392d9d6049f304dd6da6ecbe1622)
|
|
|
|
|
|
|
| |
in 2.3 installations that were upgraded from 2.2.* when the apinger to
dpinger params conversion code in upgrade_130_to_131() was not so good.
(cherry picked from commit f8f2eae491ac44ac5cdbd1fd3d38d7c2c36f48f8)
|
|
|
|
| |
and also for pfSense-upgrade
|
|
|
|
|
| |
A maybe "better" version to try.
(cherry picked from commit 0a02fc5eefb265e0684d4447bf0a7c2a9687a188)
|
|
|
|
|
|
| |
Forum: https://forum.pfsense.org/index.php?topic=110243.0
This is a trial - make sure it really works before committing.
(cherry picked from commit 6fb36cdd74dd005a9a2bc799889978b4897e6dcf)
|
|
|
|
|
| |
TRB should be TBR for "Token Bucket Regulator".
(cherry picked from commit e643627c833ce12fa00a682c66929aaad95760eb)
|
|
|
|
|
|
|
|
|
|
| |
If ramdisk is enabled keep a copy of the alias tables to restore at boot time. Otherwise unpredictable behavior may occur due to some aliases not being available when the firewall rules load.
Because alias tables are typically somewhat static, the following strategies are employed to keep write cycles to a minimum for SSD and flash drive type devices friendliness.
1) Back up during reboot/shutdown only if a backup copy of the alias table does not already exists. This is typically during the reboot when ramdisk is first enabled.
2) Update the backup copy only when the alias table is updated with a new download, typically 1 or more days, as configured in the firewall alias.
(cherry picked from commit 03afdafaab503af22ce5c98ad06b9f6bbc459974)
|
|
|
|
| |
(cherry picked from commit 642c6023fea2957bb646b1290371ead508f5cc67)
|
| |
|
|
|
|
| |
(cherry picked from commit d1db3f366180e8df8042dbeb92fa12e5a661d23c)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) The previous "down" value was being converted to msec and put into
"loss_interval". It should go into "time_period".
2) loss_interval must always be at least latencyhigh - make it so if
latencyhigh is big.
3) alert_interval must always be at least probe interval - make it so if
the probe interval is high.
4) The time_period for averaging the results must be at least 2 probe
intervals plus loss_interval (ensuring there should always be 2 probe
results by the time_period expiry) - make it so.
These various conditions taken from the validation code in
system_gateways_edit.php
Note: I have explicitly put the necessary default dpinger parameter
values here, rather than calling return_dpinger_defaults() because at
this point in any future conversion we want to use these particular
numbers, not what the defaults happen to be in pfSense 2.4 or 3.0 or...
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Redmine #6134
Forum: https://forum.pfsense.org/index.php?topic=109781.0
Originally broken by commit: https://github.com/pfsense/pfsense/commit/d18f3f6e09b86359395cd78db2e19f721818b992
(cherry picked from commit ebcd8a306c3e89ff3767bfaea03320fa211d8429)
|
|
|
|
|
|
| |
Correct units in conversion comments.
(cherry picked from commit 515887c3779519c37465aef55b22c8bd906d6f05)
|
|
|
|
| |
Update firewall rule separators positions when adding an easyrule block.
|
|
|
|
| |
I noticed this while looking at other stuff in notices.inc
If this log_error() call ever happened, it would not have done anything useful.
|
|
|
|
| |
Remove "you" personalizations.
|
|
|
|
| |
Remove "you" personalizations.
|
|
|
|
| |
last one received. Fixes #6086
|
|
|
|
| |
getUserEntry fall back to a format that will allow it to function. Net result is that now userHasPrivilege() will respect remote groups as well as local groups, which fixes #6088
|
|
|
|
| |
inbound when PPTP client is in use, as that's unnecessary.
|
|
|
|
|
|
| |
- Distribute only a single pfSense-repo package containing all templates
- Create a symlink pointing to selected repo
- Do not limit it only to pfSense-repo and pfSense-repo-devel
|