> > > For a start, directly calling /etc/network/if-pre-up.d/vlan is a
> > > huge layering violation.
> > We've been calling /etc/network/if-pre-up.d/vlan for a long time, it
> > is how we setup the vlan ports of a bridge automatically:
> Sorry for not being able to post more things here now, but at least if
> that if-pre-up.d scripts are called by ifupdown itself, you don't need
> to call them explicitly.
Sorry but I don't get it, what we are doing there is call that script so
that it creates the eth0.X interface and we are able to add it to the
bridge, if there is any way for us to call ifupdown itself to do this job
just let me know and I'll gladly make the apropiate changes.
Just to make sure we are talking about the same stuff here, the thing is
that we define a bridge with vlan based ports this way:
auto br0
iface br0 inet dhcp
bridge_ports eth0.123 eth0.234 eth1.500
And the script is called so that eth0.123 eth0.234 eth1.500 is created
automatically without having any definitions for them on
/etc/network/interfaces.
Like I said, if there is some other way to do it following standards just
let me know. The way we are doing this is the way me and the vlan maintainer
agreed back on 2003, I'm sure things have changed much since then, but I
just didn't get to know some other better way to make it.
Regards.
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
