Hello,
First of all I think that bringing interfaces up without their prior
declaration isn't a good idea, but well, okay, let's skip this for a
while.
Vlan package is going to be dropped, and in its absence there's nothing
to bring those interfaces up unless you try to configure these vlans on
y
> > > 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 a
Hello,
On Sat, 19 May 2012 13:23:08 +0200
Santiago Garcia Mantinan wrote:
> > 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 automat
Hi!
Last upload was trying to get in sync with Ubuntu, I didn't see any problems
with that, but let's see your concerns...
> 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
Package: bridge-utils
Version: 1.5-3
Severity: important
Me and Andrew Shadura, the ifupdown maintainer, have been looking at the
latest bridge-utils upload, and we have several concerns about it.
For a start, directly calling /etc/network/if-pre-up.d/vlan is a huge
layering violation.
Anyway,
5 matches
Mail list logo
