| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 24b82516e0baac87316245427e870a36fbcda4ac)
|
|
|
|
| |
(cherry picked from commit 587995fb57f91894d1f8eb6b296a9fe2fa111fac)
|
|
|
|
|
|
|
|
| |
While looking at some privilege stuff, I noticed that various
capitlization looked inconsistent down the list. This makes the list
look more consistent.
(cherry picked from commit 48157a04dde7b3a56776417cdc7b5e457a660733)
|
|
|
|
|
|
| |
client does
(cherry picked from commit 19d905bcaecfed47abdf5e3854f54684d19c3b8f)
|
|
|
|
|
|
|
|
| |
Part of Redmine #6997
This implements the similar behaviour as for the DHCPv4 server in Pull
Request https://github.com/pfsense/pfsense/pull/3271
(cherry picked from commit 756da4bdc633c309070ce9f78faae18fecde135a)
|
|
|
|
| |
(cherry picked from commit 9ca5d4abf949e088d6f1966003a6bf957f3cbdf6)
|
|
|
|
| |
(cherry picked from commit cfc10a3364fee9ab220b9ada5584bfbe62ba800c)
|
|
|
|
| |
(cherry picked from commit 1a6bda5b389df05d6dac024e8445d3a00e01e823)
|
|
|
|
|
| |
This field is currently validated to allow only an IPv4 address to be entered, so it may as well be consistent client-side so the user knows that only an IPv4 address is allowed.
(cherry picked from commit ff3d11c85450284d8949234f90af7a6c6681199e)
|
|
|
|
|
|
|
|
|
| |
If the user has input invalid values into range from and to, then there
is no point checking any IPv6 VIPs to see if they fall in the range.
None of them would be "in range" because the specified range is not even
valid.
(cherry picked from commit 3707ffc4157408b498d3b84d64918d4e41b5a123)
|
| |
|
|
|
|
|
|
|
| |
1) Allow setting a memory_limit up to 768M (Suhosin)
2) Remove old workarounds. Memory limits on config.inc will be new defaults
(cherry picked from commit 7edcc54b2e9d1de51d5e6d0aedade89bc2cf0699)
|
| |
|
|
|
|
|
|
|
|
|
| |
The usage of require() and require_once() throughout the system is
inconsistent, and "bugs" come up now and then when the order of
"requires" is a bit different and some require() happens after the
include file is already included/required.
It seems to me that there is no harm at all in always using
require_once().
|
|
|
|
| |
(cherry picked from commit cb6c20a997eeb77b3529e157cd512fabb4ff69f0)
|
|
|
|
| |
(cherry picked from commit e4c7d45fc7a294817325354e13f4d5bc4987739e)
|
|
|
|
| |
(cherry picked from commit b68e48f20c6ae99786e67372f802d16aacf22de3)
|
| |
|
|
|
|
|
|
| |
As per what was done for https://github.com/pfsense/pfsense/pull/2765 -
do it to the rest of them.
Seems to work OK.
|
|
|
|
| |
If there are non-default advanced settings, then the relevant fields are displayed on page load.
Advanced button behavior is standardized as described in redmine #5994
|
|
|
|
|
| |
This reverts commit a32bed49516f3df3d104a5026a5b2c74451f348f, reversing
changes made to 9ec9978267a5d1985d6da8ba35d52b7174239d2f.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This prevents problems when Save is translated to other languages.
Note: This is the only remaining place I could find with this issue.
There are other pieces of code that do:
```
if ($_POST['save'] == gettext("Save"))
```
which also works, but looks a bit ugly.
I left those alone, since they do work OK in any language.
|
|/
|
|
|
|
| |
The text of a Form_Button is not translated internally. Some Form_Button
calls already had the button text enclosed in gettext(), this does it
for the remaining ones.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
such here in DHCPv6 server. Ticket #3029
|
| |
|
| |
|
|
|
|
| |
actions separately and only perform the required task. Fixes #5910
|
|
|
|
| |
COntrol panels via jQuery for more control
|
| |
|
| |
|
|
|
|
| |
Fix DHCPv6 GUI to work with PD length != 64
|
|
|
|
|
|
|
| |
Import patch from @Robert-Nelson to enable DHCPv6 Server/RA to
interfaces configured to track DHCP-PD
This patch only works for PD with length 64
|
| |
|
| |
|
|
|
|
| |
address, otherwise DHCPd will silently fail
|
|
|
|
| |
order
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Following bugs and improvements on DHCPv6 DDNS area, obtained from
PR #1638 from @Robert-Nelson:
- Use correct domain (ddnsdomain) instead of (domain)
- The option "deny client-updates" wasn't being set so forward entries
weren't being added. Allow user to chose between allow, deny or ignore
- Implement reverse DNZ zone information (PTR)
|
|
|
|
| |
config format changes.
|
|
|
|
| |
breadcrumb separator.
|
| |
|
|
|
|
| |
more consistent.
|
| |
|