#759469 systemd regression: "CONFIGURE_INTERFACES=no" is ignored

Package:
ifupdown
Source:
ifupdown
Description:
high level tools to configure network interfaces
Submitter:
Harald Dunkel
Date:
2025-07-12 21:19:02 UTC
Severity:
normal
Tags:
#759469#5
Date:
2014-08-27 11:07:12 UTC
From:
To:
If I set CONFIGURE_INTERFACES=no in /etc/default/networking and
disable all in /etc/network/interfaces, then the interfaces are
still brought up (even for systemd.unit=rescue).

On bringing up eth0 in a traditional IPv6 network with router
advertisement daemon the interface automatically gets an (unwanted)
global routable IPv6 address. This potentially introduces a conflict
with the configuration in /etc/network/interfaces, network-manager
(if installed) and it might have security implications (e.g. firewall
not configured yet, mac address exposed, etc.).

In Wheezy this configure option is not ignored.

I can also delete /etc/network/interfaces, and yet lo and eth0
are brought up, so I am not quite sure if this is an issue of
ifupdown. Please reassign, if necessary.


Regards
Harri

#759469#10
Date:
2015-01-25 12:12:29 UTC
From:
To:
Since this bug has security implications, would you mind to
increase the priority?

Thanx
Harri

#759469#15
Date:
2016-01-12 17:45:18 UTC
From:
To:
CONFIGURE_INTERFACES only influences whether interfaces that are "auto"
are started at boot. It doesn't change how "allow-hotplug" interfaces
are brought up. What does your /etc/network/interfaces look like?

Also, do you still have the problem with recent versions of ifupdown?

If it's still brought up when there is no /etc/network/interfaces, then
it's not ifupdown who is configuring the interface. I cannot reassign
the bug, because I don't know which package does configure your eth0,
and in any case, that package would not read /etc/default/networking
anyway.