| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
(cherry picked from commit 260f60a9b60d42be7a274b29a8c217c2b4b53507)
|
|
|
|
|
| |
Now that Form_IpAddress() supports a range of types of input, this can be specified as HOSTV4.
(cherry picked from commit 4890b6ecb6e2928b4f5c7d4e485c39a9def42a0b)
|
| |
|
|
|
|
|
|
|
|
| |
Script changes to allow no-release option of dhcp6c. These changes to be
used in conjunction with pfSense/FreeBSD-ports/net/dhcp6c recent change
from PR #231
(cherry picked from commit 505635302a3d555eb6f82cb552c99c7ecb813f46)
|
|
|
|
| |
(cherry picked from commit e8517c7c16b8a845333c7d0e91f552144e6b5560)
|
|
|
|
|
| |
Where it is known what sort of IP address is required, we can specify it in the call to Form_IpAddress. That will make the hover text reflect what is really required as input, and make the client-side regex pattern also match only the allowed chars.
(cherry picked from commit 41fc88ec13a54817cb893a737d941e441ffd12f5)
|
| |
|
| |
|
| |
|
|
|
|
| |
Original PR to master was #3055
|
| |
|
| |
|
|
|
|
| |
Notice: Use of undefined constant min - assumed 'min'
Notice: Use of undefined constant max - assumed 'max'
|
|
|
|
|
|
| |
setting custom expirey date
(cherry picked from commit d85d82b7686d5899948e6ec4b1587e74937820cf)
|
| |
|
|
|
|
| |
(cherry picked from commit 7e653b50c4a25b045121c026cd09ac4e567c0c42)
|
|
|
|
| |
(cherry picked from commit a6a344d8dfad5f2b8199a0cef6c8f401f5e06db8)
|
|
|
|
| |
(cherry picked from commit b48f9816cd34bfee40825612a33f16215989a937)
|
|
|
|
| |
hostap interfaces. Fixes #6067
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Word smithing to remove a bunch of personalization ("You").
|
|/
|
|
| |
More accurate section title.
|
|
|
|
|
|
| |
As per what was done for https://github.com/pfsense/pfsense/pull/2765 -
do it to the rest of them.
Seems to work OK.
|
|\ |
|
| |
| |
| |
| |
| | |
Error: Duplicate ID btnadvppp.
<a class=btn btn-default btn-info href=interfaces_ppps_edit.php id=btnadvppp>
|
|/
|
|
|
| |
This reverts commit a32bed49516f3df3d104a5026a5b2c74451f348f, reversing
changes made to 9ec9978267a5d1985d6da8ba35d52b7174239d2f.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At this point $iface is an undefined var. So the last test of this "if" statement is useless.
That code fragment was introduced in commit https://github.com/pfsense/pfsense/commit/e4d40f41aafe00353c0069b457a0b1b0d6c20987
I think that code fragment came from a similar thing that is inside a "foreach $iface" loop in interfaces_pps_edit.php
https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/interfaces_ppps_edit.php#L300
and was pasted into the condition here back in 2011 without being changed.
What I have done to the test here seems what would have been intended. Any better ideas are welcome.
|
|/
|
|
|
|
|
| |
1) The var $iface is not set at lines 2457 or 2464. It is a var that was used higher up local to build_ipv6interface_list() - it is not relevant to the single fields track6-prefix-id--hex and track6-prefix-id-max
2) When the user selects a different track6-interface then trigger update_track6_prefix() which will update the help text track6-prefix-id-range.
Related to forum https://forum.pfsense.org/index.php?topic=107962.msg601309#msg601309
This pull request does not directly address the reported issue of the track6-prefix-id not "taking". It just fixes up some code issues that I noticed.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Correct the Enable Checkbox Var Names
|
|
|
|
|
|
| |
Lease requirements and requests typically contain large lists of options. Set the field width to use the available section space.
Apply a few tweaks for better clarity and consistency between DHCP and DHCPv6.
Include a more information link specific to each advanced panel.
|
| |
|
| |
|
| |
|
|
|
|
| |
interface, we don't want to handle disable separately from everything else, as that discards all the changes other than disabling the interface. Everything else with handling bringing down of interfaces is still handled correctly. semi-related to Ticket #2453
|
| |
|
| |
|