| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
|\ \ \
| | | |
| | | | |
Validate rule Advanced Options numeric entries, it should fix #3510
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes sure the user puts in ordinary positive integers like "1" and "42" in these advanced options fields. It prevents everything else, including dodgy-looking possibilities like "007" which might actually work OK, but it is safer to allow just plain "7".
Note 1: The tests in function is_aoadv_used($rule_config) had to be changed back from using empty() to use $var != "" because if the user enters "0" in one of those fields and presses save, they get an error message, but the Advanced Options block on the GUI is closed (the "0" was considered empty()). That seemed rather confusing - the user would have had to click on the Advanced Options "Advanced" button again to open up that block and see the "0" they had entered.
Note 2: I have prohibited 2 things that "pf" allows into the ruleset without generating an error:
(max 0)
(tcp.established 0)
Both of these seem (IMHO) to have no valid use case. They would prevent states from ever happening, and so would effectively be block rules, which could be implemented easily as block rules.
|
| | | |
|
|\ \ \
| | | |
| | | | |
firewall_virtual_ip , allow deleting last ip-alias if interface uses same the subnet. (while CARP-ip is present)
|
| | |/
| |/|
| | |
| | | |
the subnet. (while CARP-ip is present)
|
|\ \ \
| | | |
| | | | |
Update services.inc
|
| | | |
| | | |
| | | | |
Added CURL setops from dyndns.class
|
| | | |
| | | |
| | | | |
IPv4 ONLY
|
| | | |
| | | |
| | | | |
Prepared to make $hosttocheck configureable
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Update dyndns.class
|
|/ / / /
| | | |
| | | | |
IPv4 ONLY? YEAH ;)
|
|\ \ \ \
| |/ / /
|/| | | |
Update services.inc
|
| | | | |
|
| | | |
| | | |
| | | | |
Added missing usepublicip with dyndnsCheckIP
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix OpenVPN XML section name
|
|/ / / /
| | | |
| | | | |
Forum https://forum.pfsense.org/index.php?topic=73479.0
|
|\ \ \ \
| | | | |
| | | | | |
Add all advanced options to rule table hover text
|
| |/ / /
| | | |
| | | | |
Bug #3512
|
| | | |
| | | |
| | | |
| | | | |
elegant solution but works. Probably dhcpv6 client should solve this by itself and generate and event for it. For now just bump dhcpv6 client again to have the prefix interface reconfigured.
|
|/ / /
| | |
| | |
| | | |
subnet. It should fix #3513
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Make Firewall Rules Advanced Options open if used
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Currently, if there are some settings defined in Firewall Rules Edit, Advanced Features, Advanced Options, the Advanced Options section is left minimized when the Firewall Edit screen is displayed. This makes it easy for a user to not notice that there are some Advanced Options settings.
This change makes the Advanced Options section be displayed if any of the settings are defined, in the same way it is done for all the other Advanced Features sections.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
syntax errors correction
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| |/ / /
| | | | |
Return GWG IP protocol (version) when no gateway IP
|
| | | |
| | | |
| | | | |
Tested this making a new rule, and editing existing IPv4, IPv6 and IPv4+Ipv6 rules, and switching the IP version on an existing rule. Seems to work!
|
| | | |
| | | |
| | | | |
While I notice this also, for a plain gateway, the current IP address is also listed in the dropdown list text, like "WAN_DHCP - 10.42.11.1". If there is no IP address currently, it might say "WAN_DHCP - dynamic". But for some DHCP gateways that have not had any non-default manual settings done, it can say "OPT1_DHCP -". This gets rid of the silly-looking "-"
|
| | | |
| | | |
| | | | |
Now return_gateway_groups_array() always returns at least the IP version 'ipprotocol' of each GWG, even if all its members are down at present. It is better to use this to check what IP version the GWG is. The previous check was using the IP address of the first member of the GWG to deduce 'ipprotocol'. That would fail if the WAN was DHCP and was down.
|
| | | |
| | | |
| | | | |
This is a resubmit of an older pull request I had closed. It came up again in the forum, with a user setting up a VM environment and wondering why he cannot make policy-routing rules to a gateway group. The gateway group names did not display because all his WANs were down at the time and so the existing code was too dumb to determine the IP protocol (version 4 or 6) when none of the WANs in the gateway group actually have an IP address yet.
|
|\ \ \ \
| | | | |
| | | | | |
Add UEFI support to Network Boot options.
|