| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
A comment on the original PR says that it's not clear if the rule for this needs to be IPv6 or IPv4 with protocol IPv6, and users get confused. I've tried to clarify it here. I've also tried to "de-mystify" it, because it's not that tunneling needs special rules, it's just that any traffic needs rules and tunneled traffic is handled as IPv6 for rules purposes, so it needs an IPv6 rule. But the user may want other rules, or selective rules, so I'[ve tried to be clear this isn't about some "special" IPv6 rule, but rather, just that any traffic desired to pass, will need one or more IPv6 rules permitting it.
(cherry picked from commit 3509ad4f9215ff46d7a8684e0559bb93c1bd7a78)
|
|
|
|
| |
(cherry picked from commit 16fbe9b7ee1abfb8b9504a8d1e90dcd7592f9fe2)
|
|
|
|
| |
(cherry picked from commit a0052ea3a5fe74246795d90bcacadd025801134a)
|
|
|
|
| |
(cherry picked from commit a075265e0a076419813622e0d69556915b6f40f2)
|
|
|
|
|
|
|
| |
* Move the help message to be on the group as a whole not just the IP input field
* Clarify the IP field (label states "IP address and explains tunelling, but whgat address should be entered and should it be IPv4, IPv6 or either? This isn't made clear.
* Group title uses the term "tunneling" and this is probably the most commonly understandable term, so keep it consistent and don;'t switch to "encapsulation" halfway through. (We use the term "encapsulation" in the help text already so it's there for purists)
(cherry picked from commit 5e391e58439fa189518370fa8d16ffd2e8a1002d)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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().
|
|
|
|
|
|
| |
Use apostrophe instead of quote.
(cherry picked from commit d3706c81f7f77d21635c335d19e6626a4f7b568b)
|
|
|
|
| |
(cherry picked from commit f489cfdbd4705578ee290b9df5bafe86efddbca8)
|
|
|
|
| |
(cherry picked from commit 542d14be063e0a90b9182ee3dac9dc3fdb52d04d)
|
|
|
|
| |
(cherry picked from commit 9f563e371d0ce630f551de19c4263fe5c1686de6)
|
| |
|
|
|
|
| |
Thanks Phil.
|
|
|
|
| |
Remove a bunch of "you" personalizations.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Define the 'success' 'info' etc style of calls to print_info_box()
|
| |
|
|
|
|
| |
was the reason they were added, it was never finished and it's not being used
|
| |
|
| |
|
|
|
|
| |
are all pages and the "WebCfg" prefix implies they are pages.
|
| |
|
|
|
|
|
| |
Any GUI script that loads the guiconfig.inc file will have access to
the autoloader.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
All system_advanced_* pages had made-up lement names instead of hte correct config system names.
All (several hundred) have been corrected, and tested where possible.
|
| |
|
|
|