Project

General

Profile

Bug #802

Interface reassignment with VLANs after config restore to diff hardware doesn't work

Added by Chris Buechler about 9 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Backup / Restore
Target version:
Start date:
08/07/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

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.

Associated revisions

Revision 66bcba1b (diff)
Added by Ermal Luçi over 8 years ago

Ticket #802. During a config restore detect if the vlan interfaces need reassignment too. This might be problematic for other type of interfaces on 2.0!

History

#1 Updated by Erik Fonnesbeck about 9 years ago

This is probably also applicable for systems with a VAP wireless configuration.

#2 Updated by Erik Fonnesbeck about 9 years ago

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.

#3 Updated by Ermal Luçi about 9 years ago

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#

#4 Updated by Chris Buechler about 9 years ago

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.

#5 Updated by Ermal Luçi about 9 years ago

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!

#6 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Feedback

Committed patch.

#7 Updated by Scott Ullrich over 8 years ago

  • 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.

#8 Updated by Ermal Luçi over 8 years ago

Forward to me to take a look.

#9 Updated by Jim Pingle about 8 years ago

  • 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.

#10 Updated by Chris Buechler about 8 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF