Package: ifupdown
Version: 0.8.44
X-Debbugs-CC: [email protected], [email protected]
Control: tags -1 + moreinfo
Control: submitter -1 [email protected]

Hi Mike,

On Fri, Nov 07, 2025 at 08:05:11AM -0600, [email protected] wrote:
> mike@RPI2:~> uname -a
> Linux MikesPI 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 
> (2025-09-16) aarch64 GNU/Linux

Is this on pure Debian or a derivative? What version of ifupdown?

> apt install ifupdown over wrote /etc/network/interfaces replacing this:
> 
> #   /etc/network/interfaces  Sun 7 Apr. 2024 18:26   mc
> source /etc/network/interfaces.d/*
> 
> auto lo eth0
> # iface lo inet loopback
> iface eth0 inet static
>   address 192.168.1.2
>   netmask 255.255.255.0
>   gateway 192.168.1.1
>   broadcast 192.168.1.255
>   dns-nameservers 192.168.1.1
> 
> with this:
> 
> # interfaces(5) file used by ifup(8) and ifdown(8)
> # Include files from /etc/network/interfaces.d:
> source /etc/network/interfaces.d/*
> 
> without even backing up the original.
> I'd suggest that is  but in your install script.

We have the following in postinst:

    if [ "$1" = "configure" ] ; then
      # We don't need loopback interface definition anymore as
      # ifupdown handles loopback interface on its own from now
      if [ ! -f /etc/network/interfaces ] ; then
        if [ -z "$2" ]; then
          echo "Creating /etc/network/interfaces."
          echo "# interfaces(5) file used by ifup(8) and ifdown(8)" > 
/etc/network/interfaces
          echo "# Include files from /etc/network/interfaces.d:" >> 
/etc/network/interfaces
          echo "source /etc/network/interfaces.d/*" >> /etc/network/interfaces
        else
          report_warn "/etc/network/interfaces does not exist"
        fi
      fi
    fi

[ -z "$2" ] is true if we're installing for the first time, not upgrading
which I gather was also true in your case?

[ ! -f /etc/network/interfaces ] should protect an existing config file
here.

This being an on an embedded plantform I wouldn't discount random bitflip
as being the underlying cause ;-) but really we need more clues. Can you
reproduce the problem?

--Daniel

Attachment: signature.asc
Description: PGP signature

Reply via email to