Project

General

Profile

Actions

Bug #2367

open

display negate rules in firewall_rules.php and evaluate when added

Added by Chris Buechler almost 12 years ago. Updated almost 12 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
04/10/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

the fact the negate policy routing rule isn't shown is bad as it has lead to unintended consequences (ends up passing traffic people don't realize is passed because it's hidden). They should be shown as a grayed out auto-added rule, similar to block private/bogon.

Also need to look at when and how that rule is automatically added. In some circumstances it can allow more traffic than the user intends, such as:
http://forum.pfsense.org/index.php/topic,48143.0/topicseen.html

Actions #1

Updated by Jim Pingle almost 12 years ago

  • Subject changed from display netgate rules in firewall_rules.php and evaluate when added to display negate rules in firewall_rules.php and evaluate when added
Actions #2

Updated by Seth Mos almost 12 years ago

Normally the NEGATE rules will only trigger when the destination is set to "any".

If we change the foreach($config['rules'] as $rule) to a function that returns the firewall rules it should be easier to tack on NEGATE rules, add other rules, all in a fashion that they will also show in the UI.

e.g.

return_firewall_rules() {
 $rules = array();
 $rules = $rules + add_bogon_rules();
 foreach($config['rules'] as $rule) {
  if($negate)
   $rules[] = $negate_rule;
  $rules[] = $rule;
 }
 $rules = $rules + add_v6_delegation_rules();
}

For example. The automatic rules I added for dynamic IPv6 connections need to shown as well. It's less then optimal.

Actions #3

Updated by Chris Buechler almost 12 years ago

  • Target version deleted (2.1)
Actions

Also available in: Atom PDF