Package: ifupdown-extra Version: 0.27 Followup-For: Bug #901612 Dear Maintainer,
We are also impacted by this bug. On boot, static routes are not added. After applying the patch mentioned in the previous comment, this works fine. We investigated the newer package in current stable (0.28) and did not find a fix for our problem in there, so it still applies to 0.28 as well. We plan to upgrade in the next few weeks. Is there any reason not to apply (a modified version of) the patch? -- System Information: Debian Release: 9.13 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-13-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown-extra depends on: ii bind9-host [host] 1:9.10.3.dfsg.P4-12.3+deb9u6 ii curl 7.52.1-5+deb9u11 ii dpkg 1.18.25 ii host 1:9.10.3.dfsg.P4-12.3+deb9u6 ii iproute2 4.9.0-1+deb9u1 ii iputils-arping 3:20161105-1 ii iputils-ping [ping] 3:20161105-1 ii net-tools 1.60+git20161116.90da8a0-1 ii netcat-traditional [netcat] 1.10-41+b1 Versions of packages ifupdown-extra recommends: ii ethtool 1:4.8-1+b1 ii ndisc6 1.0.3-3 ifupdown-extra suggests no packages. -- Configuration Files: /etc/network/routes changed [not included] -- no debconf information -- * * This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. Connectis accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
