Bug 98180

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b)
Gecko/20030516 Mozilla Firebird/0.6

Description of problem:
VLANs work with bonded interfaces, but the ifup scripts don't handle them very
well.  Here are some of the changes that need to be made.

ifup specifically looks for VLANs of type eth[0-9][0-9]*\....  That needs to
change to probably look for [a-zA-z]+[0-9][0-9]*\.... (at the very least, it
should be expanded past just eth to maybe (eth|bond)).

VLANs should be processed after all other interfaces are brought up.  This
ensures that if a VLAN is placed on a bonded interface, the bonded interface is
configured and up (as much as it can be) before the VLAN is brought up on it. 
If a VLAN is brought up before the bonded interface has its slaves enslaved, the
bonded interface has no MAC address and the VLAN picks up a zeroed MAC address
that never gets updated.  Currently, VLANs are processed in the normal flow,
which means they are usually brought up right after the interface they're
applied on.

Version-Release number of selected component (if applicable):
7.14-1

How reproducible:
Always

Steps to Reproduce:
1. Setup bonded interfaces bond0 on eth0, eth1
2. Setup vlan on bond0.1, for example
3. boot box 

Actual Results:  Everything comes up, but vlan on the bonded interface has no
MAC address information.

Expected Results:  Everything comes up and vlan on the bonded interface has MAC
address of bonded interface it is attached to.

Additional info:

This can obviously be done by setting ONBOOT=no in the vlan ifcfg file, and then
sticking the ifup commands in /etc/rc.local, but it doesn't really need to be
that way.