Project

General

Profile

Feature #96

Add "All local networks" to source and destination drop down boxen in firewall rules

Added by Scott Ullrich about 9 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Rules/NAT
Target version:
Start date:
09/22/2009
Due date:
% Done:

0%

Estimated time:

Description

This would allow easily negating all local networks (internet) where usage of "floating rules" is not desirable easily.

Associated revisions

Revision 50ea0588 (diff)
Added by Sjon Hortensius over 3 years ago

bindCollapseToOptions - support multiple options targeting single section

fix #96

History

#1 Updated by Chris Buechler over 8 years ago

  • Target version changed from 3 to Future
  • Affected Version deleted (All)

#2 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Closed

#3 Updated by Jim Pingle over 8 years ago

  • Status changed from Closed to New

This isn't the same as the other ticket.

The other ticket is a list of IPs directly assigned to the router itself (Like an alias with host entries). This is a list of all locally connected networks (like an alias with network entries with appropriate subnet masks).

#4 Updated by Josh Stompro about 8 years ago

Please consider expanding this enhancement to include the following.

Automatically add aliases that correspond to the local interface networks. The source/destination drop downs under firewall rules include shortcuts for "LAN network", "WAN network", etc. If the system automatically added those as aliases "WANNetwork" = "WAN Network", it would be possible to construct an alias that includes a certain subset of local networks, and would automatically stay synchronized with interface subnet changes.

Say you had 10 local LAN interfaces/vlans, LAN01-LAN10. And you wanted to block traffic from LAN01 and LAN02 from reaching LAN03-LAN10. It would be nice to be able to construct an alias that included the networks "LAN03Network", "LAN04Network"... so only two firewall rules would be needed to block traffic from LAN01 and LAN02. This is possible now by manually entering the network info to an alias, but that needs to be updated separately when interface network settings are changes, adding an extra point of failure.

My particular use case is that I have 30 pfSense firewalls that all have slightly different local network settings, and when I set them up I go through and change the local network info on my master config image. A feature like this would save me some time since I wouldn't need to touch the aliases or firewall rules when changing local lan info.

Thanks
Josh

#5 Updated by Ermal Luçi about 4 years ago

  • Status changed from New to Resolved

(self) has been introduced as a selection.

#6 Updated by Jim Pingle about 4 years ago

  • Status changed from Resolved to New

That's not the same, this would be for all local subnets, not all IPs on the firewall. (self) was only relevant to that other ticket (#597)

#7 Updated by Anonymous about 3 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#8 Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to New
  • % Done changed from 100 to 0

Accidentally was caught by an unrelated commit message

#9 Updated by Chris Buechler over 2 years ago

  • Category set to Rules/NAT

Also available in: Atom PDF