Actions
Feature #2239
closed
Use Firewall Alias in Static Routing setup
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/27/2012
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
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.
Updated by Jim Pingle over 12 years ago
Mostly done in RELENG_2_0 in c9e04cd59054cf839af96cdf71cfc4cf58ccabaf and in master in f898c1a98213ec6b2497608c181ba3bb149a234b
Still has a few considerations to handle:
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?
Updated by Chris Buechler about 11 years ago
- Status changed from New to Resolved
Actions