It looks like ifupdown tries to configure the VLAN a second time when it comes across the inet6 definition in /etc/network/interfaces.
This fails as the VLAN interface was already setup in the inet definition of the same interface. It looks like a conceptual error in the interfaces(5) syntax. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/905660 Title: [ifupdown] ipv6 refuse vlan interfaces Status in “ifupdown” package in Ubuntu: Fix Released Bug description: Package: ifupdown Version: ifupdown 0.7~alpha5.1ubuntu5 Severity: normal ifupdown (0.7~beta1) correct this bug : * Accept VLAN interface names (Closes: #632902). The interfaces file: (/etc/network/interfaces) auto eth0.77 iface eth0.77 inet static address 192.168.1.50 netmask 255.255.255.0 gateway 192.168.1.1 iface eth0.77 inet6 static address 2a01:6e00:1111:1111::2 netmask 64 gateway 2a01:6e00:1111:1111::1 => IPv4 is OK with VLAN77 => IPv6 not mont with VLAN77 (IPv6 ok without VLAN) Bug with IPv6 auto : http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=632902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/905660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
