> Personally I always added the static addresses in the up after > the ipv4 stuff. Yours seems like the correct way. Hmmm. I have to > look into it. For me it is new behaviour that ifup will handle > multiple iface eth0 entries. (I probably didn't read the manpages > right).
It seems that it is also valid to specify an ipx stanza too (although I can't imagine why anyone would :) I'm not sure that the way the vlan (and bridge) tools hook into ifupdown is entirely the right way to do it, or else maybe the ifupdown interfaces file needs to be redesigned, which is more likely... I've not used the bridge tools with an ipv6 static ip address before, but I suspect that it will break in a similar way. With bridging you have to specify things manually, but you'd still have to choose one stanza to do it in, and ifdown would delete the bridge in the wrong place again. The best approach I can think of off the top of my head would be something like: auto eth0 iface eth0 auto vlan2 iface vlan2 vlan-raw-device eth0 auto br0 iface br0 bridge_ports eth2 eth3 proto eth0 inet static address 192.168.1.1 netmask 255.255.255.0 proto eth0 inet6 static address 3ff0:1::1 netmask 64 proto eth0 ipx param1 1 param2 2 proto vlan1 inet static address 192.168.2.1 netmask 255.255.255.0 proto eth0 inet6 static address 3ff0:2::1 netmask 64 proto br0 inet static address 192.168.3.1 netmask 255.255.255.0 But I guess a bug report on vlan isn't really the best place to discuss this any further :) James
