Actions
Bug #3147
closedAdding new interface can cause issues
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
08/14/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
amd64
Description
When adding a new interface on the (assign) page, it defaults to the first interface that hasn't been assigned. This change is immediately applied (although the interface is not "enabled" until ticked, obviously).
If the first interface picked happens to be a CARP VIP then this VIP will stop working until the new interface is correctly assigned and the CARP interface re-saved.
Suggestion: Maybe have an "apply" button that needs to be pressed before any new interface is actually assigned, much like most of the rest of pfsense, or perhaps when you add a new interface it defaults to something that won't potentially cause issues (say, a loopback)
Files
Actions