From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021231 Description of problem: 8021Q VLAN subinterfaces __should__ not have 0.0.0.0/32 ip address set!!! Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Just try using vlan subinterfaces as implemented in initscripts-7.06-1 on a router running dynamic routing protocols reflecting or (re)distributing default route. 2. 3. Additional info: Aditionaly think that trunk ports are in a native vlan (default 1) and frames are not tagged whithin that vlan! Many managed switches (3Com, allied telesyn, maybe a lot other) do not support other management vlan but vlan 1. Maybe you will want to manage those switches from network, not only using a serial port - that's an example. Having 0.0.0.0/32 ip set on a interface will cause dynamic routing daemons to redistribute this as somekind of default route if redistribute static option is enabled (bgpd, ospfd, ripd, gated, etc). +++802.1q vlan subinterfaces should be able to have aliases (e.g.: eth7.901:0). A realy working 802.1Q VLAN interfaces support patch (last applied on initscripts-7.01, I'll prepare one for 7.06-1 as soon I'l rebuild glib2 on my system, it seems I don't have it static as required) can be found at http://www.ac.tuiasi.ro/mituc/devel/initscripts/initscripts-vlans-1.3.2.patch .
Created attachment 89949 [details] 802.1Q VLAN subinterfaces support It should require some more checks to tell more about what's happening when an error occurs, but it works fine (tested in production for almost 6 months).
Well, I took a closer look and it's seems I was terrible wrong about this. ip add add 0.0.0.0/32 dev device does nothing, anyway it should not be there, ip -o link set dev ${PHYSDEV} up it's enough. Moreover vlan interfaces are now treated as normal interfaces so aliases are added if any.