Package: ifupdown
Version: 0.8.41
Severity: important

Dear Maintainer,

   * What led up to the situation?

        Bringing up a new debian 12 system with a static network-configuration 
supplied by cloud-init

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

        Logged in via console and added a static route manually. 

   * What was the outcome of this action?

        System worked as expected for that session but would not have a route 
on subseqent boots.

   * What outcome did you expect instead?

        System would work without further modification

   * Additional statments:

        This seems like an undeclared, or perhaps modified dependency. I was 
able to determine that the route command is provided by the net-tools package. 
Once that was installed then ifupdown worked as expected. Its possible that 
this command used to be provided by the current dependencies and something 
there changed? Please let me know if you need any additional details. Here's 
the output of `systemctl status networking.service` that lead me to this 
conclusion.

-- Boot 1be256fba6244cb19d698f10d0d4acca --
Jul 11 12:01:54 nbc9-d12-dev-01 systemd[1]: Starting networking.service - Raise 
network interfaces...
Jul 11 12:01:54 nbc9-d12-dev-01 ifup[780]: /bin/sh: 1: route: not found
Jul 11 12:01:54 nbc9-d12-dev-01 systemd[1]: Finished networking.service - Raise 
network interfaces.



-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug ens192
iface ens192 inet dhcp

--- /etc/network/interfaces.d/*:
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address 10.236.81.22/24
    dns-nameservers 152.3.72.100 152.3.70.100
    dns-search oit.duke.edu
    post-up route add default gw 10.236.81.1 || true
    pre-down route del default gw 10.236.81.1 || true

--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 759 Dec  9  2022 resolved

/etc/network/if-post-down.d:
total 0

/etc/network/if-pre-up.d:
total 4
-rwxr-xr-x 1 root root 344 Dec 20  2022 ethtool

/etc/network/if-up.d:
total 16
-rwxr-xr-x 1 root root 1685 Dec 20  2022 ethtool
-rwxr-xr-x 1 root root 1048 Jan 16 18:31 ntpsec-ntpdate
-rwxr-xr-x 1 root root 4663 Dec  9  2022 resolved


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown depends on:
ii  adduser   3.134
ii  iproute2  6.1.0-3
ii  libc6     2.36-9

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.3-P1-2

Versions of packages ifupdown suggests:
pn  ppp     <none>
pn  rdnssd  <none>

-- no debconf information

Reply via email to