Bug#804396: if IPv6 configuration fails, then IPv4 is not configured

2018-06-14 Thread Harald Dunkel
> > If /etc/network/interfaces defines 2 protocols for one interface, > > then a tiny problem for one protocol can affect both. > > This is by design. Recent versions of ifupdown will even exit with an > error code if there is an error while configuring any part of an > interface. Then we have a

Bug#804396: if IPv6 configuration fails, then IPv4 is not configured

2016-12-08 Thread Noah Meyerhans
On Sat, Jan 09, 2016 at 08:29:39PM +0100, Guus Sliepen wrote: > > If /etc/network/interfaces defines 2 protocols for one interface, > > then a tiny problem for one protocol can affect both. > > This is by design. Recent versions of ifupdown will even exit with an > error code if there is an error

Bug#804396: if IPv6 configuration fails, then IPv4 is not configured

2016-01-09 Thread Guus Sliepen
tags 804396 + wontfix thanks > If /etc/network/interfaces defines 2 protocols for one interface, > then a tiny problem for one protocol can affect both. This is by design. Recent versions of ifupdown will even exit with an error code if there is an error while configuring any part of an interface

Bug#804396: if IPv6 configuration fails, then IPv4 is not configured

2015-11-07 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: ifupdown Version: 0.7.54 Severity: wishlist If /etc/network/interfaces defines 2 protocols for one interface, then a tiny problem for one protocol can affect both. Sample config to show: auto eth0 iface eth0 inet6 static