Bug #62
closed
Check vlan 1.2 -> 2.0 upgrade code and interface naming.
Added by Seth Mos over 14 years ago.
Updated about 14 years ago.
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.
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.
- 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.
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.
- Status changed from Feedback to New
- Status changed from New to Feedback
- Assignee deleted (
Seth Mos)
- 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.
- Category set to Interfaces
- Status changed from Resolved to Feedback
Mark for feedback as a reminder for me to test
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.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Ermal Luçi 
Updated by 
Updated by