Project

General

Profile

Actions
Copy link

Bug #62

closed

Check vlan 1.2 -> 2.0 upgrade code and interface naming.

Added by Seth Mos about 15 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
2.0
Start date:
08/26/2009
Due date:
% Done:

0%

Estimated time:
4.00 h
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Check vlan 1.2 -> 2.0 upgrade code and interface naming. Also check deleting vlans and interface assignment.

I ran into weird issue trying to debug this and got ifconfig exit status messages in the system logs that need to be looked at.

Actions
Copy link
 #1

Updated by Seth Mos about 15 years ago

  • Assignee set to Seth Mos
Actions
Copy link
 #2

Updated by Jim Pingle about 15 years ago

You might sync and try again.

I fixed a couple bugs in the automatic vlan hardware detection today that could have led to vlan interfaces disappearing or never being created since the system believed (incorrectly) that the network card did not support vlans.

Actions
Copy link
 #3

Updated by Ermal Luçi about 15 years ago

  • Status changed from New to Feedback

AFAIK this should be all resolved.
I forgot to reference commits to this that's why you cannot see them here.

Actions
Copy link
 #4

Updated by Seth Mos almost 15 years ago

Perry did a upgrade from a 1.2 install and it complained about missing interfaces.

Seems the upgrade code made it refer to the old vlanx naming.

Actions
Copy link
 #5

Updated by Scott Ullrich almost 15 years ago

  • Status changed from Feedback to New
Actions
Copy link
 #6

Updated by Ermal Luçi almost 15 years ago

  • Status changed from New to Feedback

Patched.

Actions
Copy link
 #7

Updated by Ermal Luçi almost 15 years ago

  • Assignee deleted (Seth Mos)
Actions
Copy link
 #8

Updated by Seth Mos almost 15 years ago

  • Status changed from Feedback to Resolved

I just checked in the code that properly upgrades the vlan configuration in 054 to 055.

It now creates a config.xml that properly parses, it also updates the interfaces section in the config.xml to the new values corresponding to the right interface.

I tested this with 2 dummy vlans and that worked as it should on a upgrade. I consider this resolved but would like some feedback with regards to upgrades on existing config codes.

Actions
Copy link
 #9

Updated by Chris Buechler almost 15 years ago

  • Category set to Interfaces
  • Status changed from Resolved to Feedback

Mark for feedback as a reminder for me to test

Actions
Copy link
 #10

Updated by Jim Pingle almost 15 years ago

I did a test upgrade on a fully VLAN test box (LAN and WAN) using an image which included the new VLAN upgrade code and it worked perfectly. Box came back online and the interfaces were working as they should.

Actions
Copy link
 #11

Updated by Chris Buechler over 14 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF