| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
disable on inactive interfaces"
This reverts commit 6310eaa2c75424da6a322a956bbf228b36222918.
|
| |
|
|
|
|
| |
and pbi_info.
|
|\ |
|
| |
| |
| | |
This is code for RELENG_2_2 pfSense 2.2.5 that will limit the number of rows in the alias info popup to 100.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use a different flag file to indicate that a package reinstall is
required after a reboot is done first. This avoids the possibility that
the user navigates in the webGUI during the time while the shutdown is
in progress and is accidentally presented with the reinstall all
packages GUI button.
Early in rc.bootup switch the flag file to use its ordinary name, so
that all subsequent code in boot scripts and webGUI will work as it
already does to handle the package reinstall and notifying the user that
a package reinstall is about to be done or in progress...
|
| |
| |
| |
| |
| |
| | |
ability to pass relative paths
Restricts them to files under their intended base directories.
|
| |
| |
| |
| | |
never ported over from the package (and is messy to do so). Ticket #5545
|
|\ \ |
|
| | |
| | |
| | |
| | | |
There is a variable cut-paste error here. Actually it never makes any difference in practice because outgoing_num_tcp and incoming_num_tcp are both set, so the logic comes out the same.
I noticed this while reviewing stuff in master for 2.3-ALPHA - might as well back-port stuff like this so that nobody who notices will worry about it in RELENG_2_2.
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
The block private networks and anti-lockout rules display in the firewall rules display with the schedule column blank. But the block bogon networks has an asterisk. That looks odd. I noticed it just now when looking at firewall rules in 2.3.
Might as well fix it here in RELENG_2_2.
|
|\ \ \ |
|
| |/ / |
|
|/ /
| |
| |
| | |
The code in RELENG_2_2 for system_usermanager_settings.php seems to work OK in RELENG_2_2 so I did not touch anything there.
But diag_authentication.php had nothing about $pconfig on initial page load. This extra code makes it select a reasonable default auth server when the page first loads. After that, each time the user does "Test", the page comes back with the previously selected auth server, user name and password (like it did already) - so that seems good.
|
|/
|
|
| |
Fix ID used by child SA disconnect button.
|
| |
|
|
|
|
| |
committed with a different name
|
| |
|
|
|
|
| |
should be an isset on the remote SPI field.
|
|
|
|
| |
the original m0n0wall BSD 2 clause.
|
|
|
|
| |
VICI, also use local-nat-t and remote-nat-t to detect when NAT-T is being used
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
for RELENG_2_2
|
|\ \ |
|
| |/
| |
| | |
and forum https://forum.pfsense.org/index.php?topic=101276.0
|
|/
|
|
| |
complications of 0 due to PHP stupidity. Upgrade config to add 1 to any configured log levels. Default to 1 as log level where none is configured by the user. Ticket #5340
|
|
|
|
|
| |
This was fixed in master for 2.3 by https://github.com/pfsense/pfsense/commit/50e6c063e6ec148917ff0bcb0bce8b0a08df5792 - in master all of these $tab_array entries, in each file that they appear in, had been modified to just use the $tab_array[] = form.
But in RELENG_2_2 that has not happened. So it seems nicer to just fix the numbering here to match what is already in the other interfaces_*.php files in RELENG_2_2.
Note that the code works OK without this "fix" - display_top_tabs() just loops through the existing array keys anyhow and so did not notice the missing number.
|
|\ |
|
| |
| |
| |
| | |
(RELENG_2_2)
|
|/
|
|
| |
mobile clients. Fixes #5323.
|
|
|
|
|
| |
as the source for user authentication when EAP-RADIUS is selected as the phase
1 authentication method for mobile IPsec. Fixes #5219.
|
|
|
|
| |
filter reload to DHCP Relay config so rules are immediately added/removed. Ticket #4558
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
This code checks if the user has somehow posted a group deletion for a group that has "system" scope. If so, then the delete is not done and an input error is displayed.
Note that in normal use the group manager page does not display a delete button for "system" groups, so normally this does not happen - only if the user manually messes with the $POST variables.
|
|/
|
|
| |
This code checks if the user has somehow posted a user deletion for a user that has "system" scope. If so, then the delete iscnot done and an input error is displayed.
Note that in normal use the user manager page does not display a delete button for "system" users, so normally this does not happen - only if the user manually messes with the $POST variables.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
I noticed this while comparing alias popup behavior between 2.2.5-DEVELOPMENT and 2.3
Might as well fix the grammar here for 2.2.5
This tip does not exist in 2.3 because the popup works more nicely there and so this text is not needed.
Therefore this change does not need to be ported forward to master.
|