| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
as character
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically if the directory exists it will suck in the files to extend these pags.
/usr/local/pkg/firewall_nat/input_validation
/usr/local/pkg/firewall_nat/pre_write_config
/usr/local/pkg/firewall_nat/htmlphpearly
/usr/local/pkg/firewall_nat/htmlphplate
/usr/local/pkg/firewall_rules/input_validation
/usr/local/pkg/firewall_rules/pre_write_config
/usr/local/pkg/firewall_rules/htmlphpearly
/usr/local/pkg/firewall_rules/htmlphplate
|
|
|
|
| |
but not everywhere followed.
|
|
|
|
| |
web browser auto-complete from covering up the alias list popup.
|
|
|
|
| |
needed fixed. Still needs changes in filter.inc - Ticket #1243
|
|
|
|
| |
their expansion on Port Forwards and Outbound NAT screens. Will allow users with large proxy arp subnets used only with 1:1 to still load those pages in a reasonable time. Resolves #1119
|
| |
|
| |
|
| |
|
|
|
|
| |
Ticket #570
|
|
|
|
|
|
| |
When we change the source address on a NAT Port Forward rule that had
an associated rule, we need to change the associated rule source address
as well
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
usr/local/www/diag_smart.php
usr/local/www/firewall_rules_edit.php
usr/local/www/interfaces.php
usr/local/www/load_balancer_pool_edit.php
usr/local/www/pkg_mgr_settings.php
|
| |
| |
| |
| | |
not been saved since the associated rule was created.
|
|/ |
|
|
|
|
| |
other than the first with a filter rule.
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
same VPNs to the list available on other types of NAT rules.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 1baff2e5d32ebb5a71b07f38d9f97e3c4788e3be.
Lot of syntax errors
Conflicts:
usr/local/www/firewall_nat_edit.php
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
affecting 64-bit. Ticket #459
|
|
|
|
| |
for further calls to this client-side function.
|
|
|
|
| |
bad deletions might happen. Reported-by: http://forum.pfsense.org/index.php/topic,25091.0.html
|
|
|
|
| |
clear.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New features available are:
* Now you can disable a rule
* You can define "no rdr" rules
* Source type, address and port, with an option "not" for exceptions
* Destination type, address and port, with an option "not" for exceptions
Implemented by: Carlos Eduardo Ramos <carlos.ramos@bluepex.com>
Renato Botelho <renato.botelho@bluepex.com>
Vinicius Coque <vinicius.coque@bluepex.com>
Reviewed by: cmb and efonne
Sponsored by: BluePex Security Solutions
|
|
|
|
| |
and loads them into a pf persist table instead of importing the addresses directly into a traditional alias. This allows for using huge tables of addresses that would otherwise break the GUI and/or fail to load into pf. Part of ticket #512
|
|
|
|
| |
defined as network.
|
|
|
|
| |
edit page.
|
|
|
|
|
|
|
|
| |
Fix associated nat rules.
Now both the filter rules and the nat ones contain a associated-rule-id tag which helps link the items together.
The API to use for this is in itemid.inc.
All the issues should be solved now.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Multiple NAT rules can be assigned the same filter rule
-> Fixed, added assigned-nat-rule-id to filter rules to keep track of the assignment
2) when removing the link (i.e. switching to "pass" or "none", the linked rule isn't deleted (should it be? probably yes)
-> Fixed, when a NAT rule's association is removed, the filter rule is deleted. Added a "create new associated filter rule" option to the
dropdown if there is none selected.
3) The destination IP and port of linked rules can be edited in firewall_rules_edit.php and shouldn't be. Source should be editable but not
destination, since that should strictly be tied to the NAT rule.
-> Fixed, you cannot edit the destination for the filter rules that are linked to NAT rules, this has been disabled both by JavaScript and
PHP.
4) If you edit the source in a linked firewall rule, it gets overwritten when you edit the NAT rule. The NAT rule should never touch the
firewall rule source after the rule exists.
-> Fixed, previously the old rule was deleted and a new one created, now it only updates the old rule and doesn't touch the source.
Also added crosslinking from the NAT rule to the filter rule and back, so you can jump to edit the filter rule from the NAT rule and
vice-versa.
|
|
|
|
| |
only on port side and other aliases in ip specifications and similar. Introduce a new function is_portoralias to ressemble the is_ipaddroralias to check for the cases.
|
| |
|
| |
|
|
|
|
| |
host/network aliases for the src/dst. Checking if a valid alias is entered end if it is a correct one for this box seems like to much overhead and work for this. (For firewall_nat_edit.php)
|