Bug#882777: ifupdown: ifup -a tries to bring up an interface that already is up

2019-04-24 Thread Dimitris Aragiorgis
Hi, I bumped into this issue as well. Upgrading from jessie to strech the networking service that calls `ifup -a` fails because the interface is already configured. I think this commit is to blame: https://salsa.debian.org/debian/ifupdown/commit/87ca29628d452d7eaa124a943ffb2382743f19e0 What if

Bug#882777: ifupdown: ifup -a tries to bring up an interface that already is up

2017-12-13 Thread Ralf Jung
Hi, >> The relevant bits of the /etc/network/interfaces.d/* looks as follows: > [...] >> pre-up ip tunnel add $IFACE mode gre local 51.X.X.X remote 185.X.X.X >> ttl 255 > [...] > > The problem with jessie was that it ignored any errors from > pre/post-up/down commands. This was fixed in

Bug#882777: ifupdown: ifup -a tries to bring up an interface that already is up

2017-11-26 Thread Guus Sliepen
On Sun, Nov 26, 2017 at 06:09:29PM +0100, Ralf Jung wrote: > The following command: > > /sbin/ifup -a --read-environment > > tries to bring up some GRE tunnels on my system that are already up. > Obviously, > this fails. One consequence of that is that the systemd "networking" unit is > alw

Bug#882777: ifupdown: ifup -a tries to bring up an interface that already is up

2017-11-26 Thread Ralf Jung
Package: ifupdown Version: 0.8.19 Severity: normal Dear Maintainer, The following command: /sbin/ifup -a --read-environment tries to bring up some GRE tunnels on my system that are already up. Obviously, this fails. One consequence of that is that the systemd "networking" unit is always mar