Bug #802
closed
Interface reassignment with VLANs after config restore to diff hardware doesn't work
Added by Chris Buechler over 14 years ago.
Updated over 13 years ago.
Category:
Backup / Restore
Description
When you have a configuration with VLANs and restore it to hardware with different NICs than the original hardware, the interface reassignment is inadequate as you can't re-assign the parent VLAN interface. The work around is to change the interface names in the config.xml before restoring.
This is probably also applicable for systems with a VAP wireless configuration.
Though I suppose technically since it only really works with ath at the moment, the similar issue with the VAP configuration has significantly lower priority.
Two options:
- Either make the code OO similar to the shaper one. Which would only keep the real/parent interface saved only in one place
- Make all FreeBSD interfaces have a name of eth#
There's an easier option there, simply detect VLANs with a missing parent interface upon config restore and prompt for reassignment no differently than is now done for physical interfaces. Could just be an addition to the same reassignment screen.
Yeah but this goes all back to wlan interfaces, ppp, possibly others.
And that means defining rules in code for this.
Not that is not doable just to confirm this!
- Status changed from New to Feedback
- Status changed from Feedback to New
Changing back to new. I have a configuration file here that will utterly wreack havoc if someone wants to take a look.
Forward to me to take a look.
- Status changed from New to Feedback
I restored a config with vlans to a VM and it worked fine - I had to go to the VLANs tab and reparent the VLANs one by one, then I was able to reassign the interfaces properly and save/apply/reboot and it came up.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by Ermal Luçi 
Updated by 
Updated by 
Updated by