Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-26 Thread Oleg A. Arkhangelsky
On Wed Jan 25, 2023 at 11:31 PM UTC, Pascal Hambourg wrote: > Maybe there is a more elegant way to stop ifup@*.service, e.g. using > systemd unit dependencies but I am not familiar enough with this topic. > > This setup causes no delay when (re)starting networking.service by hand > at boot time

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-23 Thread Oleg A. Arkhangelsky
On Mon Jan 23, 2023 at 2:55 PM UTC, Santiago Ruano Rincón wrote: > Thanks everybody for the inputs. I've applied Paul's solution, and the > generated .deb can be downloaded from here: > >

Bug#1022843: ifupdown: network down after systemctl restart

2023-01-21 Thread Oleg A. Arkhangelsky
On Fri Jan 20, 2023 at 5:26 PM UTC, Jeff King wrote: > This has the minor downside that on system startup, we'll spend time > trying to bring up allow-hotplug interfaces, even if they're not > available. So on my system, for example, with: > > allow-hotplug eth0 > iface eth0 inet dhcp > >

Bug#1022843: ifupdown: network down after systemctl restart

2022-10-29 Thread Oleg A. Arkhangelsky
Package: ifupdown Tags: patch Here is proposed patch. Since the unit type is oneshot, we can have multiple ExecStart statements. Note that we have to use '--ignore-errors'. Otherwise if we have real hotplug interface that is not present at the moment of restart, `ifup` returns non-zero and

Bug#1022843: ifupdown: network down after systemctl restart

2022-10-26 Thread Oleg A. Arkhangelsky
Package: ifupdown Version: 0.8.36 Severity: important X-Debbugs-Cc: syso...@yandex.ru Hello! (Not sure why such rather important issue is not filled yet, but anyway. Sorry if I'm creating duplicate.) My network is down after running `systemctl restart networking` on fresh installed Debian