On Wed, 2016-03-30 at 10:26 -0400, Lennart Sorensen wrote: > On Wed, Mar 30, 2016 at 03:11:03PM +0100, Dimitri John Ledkov wrote: > > > > Hi, > > > > On Sat, 12 Mar 2016 13:49:57 +0100 Tom H <firstname.lastname@example.org> wrote: > > > > > > You don't need vlan; iproute2's ip can do it: > > > > > > ip link add link eth0 name vlan9 type vlan id 9 > > > or > > > ip link add link eth0 name eth0.9 type vlan id 9 > > > > > > > > I know that. vlan package is needed for the ifupdown hooks to parse > > vlan stanza from /etc/network/interfaces and hence configure vlan id. > > Or am I missing something? > Currently the vlan package provides such hooks. No reason one could > not add such hooks to the iproute2 package or even extend ifupdown to > handle it itself. Using the vlan package is certainly not efficient > compared to using the ip command for the job. This is also true for > bridge-utils as far as I know, where I think iproute2 can also completely > replace that. I agree with this. Debian-installer should not create a network configuration that depends on tools that have been deprecated for over a decade. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest.
Description: This is a digitally signed message part