Feature #2239

Use Firewall Alias in Static Routing setup

Added by Warren Baker about 2 years ago. Updated 8 months ago.

Status:Resolved Start date:02/27/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Affected version: Affected Architecture:

Description

It would be nice to have the ability to use Firewall aliases in the Static routes section.
The alias would automatically be expanded and the relevant routes would then be added.

Associated revisions

Revision c9e04cd5
Added by Jim P about 2 years ago

Add alias support to static routes (needs some testing) Ticket #2239

Revision f898c1a9
Added by Jim P about 2 years ago

Add alias support to static routes (needs some testing) Ticket #2239

Conflicts:

etc/inc/filter.inc
etc/inc/util.inc
usr/local/www/system_routes_edit.php

History

#1 Updated by Jim P about 2 years ago

Mostly done in RELENG_2_0 in c9e04cd59054cf839af96cdf71cfc4cf58ccabaf and in master in f898c1a98213ec6b2497608c181ba3bb149a234b
Still has a few considerations to handle:
  • What happens when an alias changes? (until that is fixed, edit/save on the alias should pick up new values, but old orphaned values may not be removed)
  • Needs more testing on add/remove. Did basic testing before committing but the more scenarios we can test the better
  • Currently hostnames are only skipped in the backend. We may want to warn or reject aliases containing hostnames.
  • Anything else?

#2 Updated by Chris Buechler 8 months ago

  • Status changed from New to Resolved

Also available in: Atom PDF