Bug #3147
closed
Adding new interface can cause issues
0%
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
Updated by Sam McLeod over 10 years ago
I have experienced this multiple times.
How did Pfsense 2.1 go stable without this even getting looked at?
Updated by Ermal Luçi over 10 years ago
Because this is behavior since pfSense inception and is not considered a blocking/new bug!
Updated by Chris Thomas over 10 years ago
Ermal,
This this need to be resubmitted as a feature request then?
Updated by Chris Thomas over 10 years ago
https://forum.pfsense.org/index.php/topic,64704.0.html
As far as I'm concerned, it's a bug. Because I have not hit 'apply' or 'save' before pfsense writes the config, thus breaking whatever interface happens to be auto-populated.
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Resolved
the only scenario I see where this can possibly be an issue is with it assigning a CARP VIP. CARP VIPs shouldn't be available to assign in the first place, and that's been fixed since (in 2.2 if not earlier), which eliminates any possibility of there being issues here AFAICT.
Updated by Chris Thomas almost 10 years ago
- File Capture.JPG Capture.JPG added
The issue affects more than just VIPs. Whatever auto-populates the 'Network Port' field after the new Interface is added (but not saved) stops working. If it's a VIP, you have to edit/save the VIP. If it's an OpenVPN tunnel, then the tunnel stops working until you take it down and bring it back up.
https://forum.pfsense.org/index.php?topic=64704.msg350841#msg350841
Updated by Chris Thomas over 9 years ago
This 'bug' appears to have finally been addressed with the changes for #3846 "Adding interface for new VLAN selects active WAN VIP address breaking connectivity".
Thanks!