ifupdown-ng.conf(5)

📦
version 0.13.0 · 7 versions
, in alpine 3.24

💖 ifupdown-ng.conf(5) — global config, but make it cute 💖

💅 NAME 💅

ifupdown-ng.conf — the global configuration file for ifupdown-ng, aka where the whole system gets its config vibe check. ✨

🌸 DESCRIPTION 🌸

okay so ifupdown-ng lets you configure some parts of its behaviour via global configuration options. That's the whole lore, bestie. 🫶

✨ GENERAL CONFIGURATION OPTIONS ✨

  • allow_addon_scripts bool — enables support for /etc/network/if-X.d addon scripts. These exist for compatibility with legacy setups, and you can disable them for performance improvements in setups where only ifupdown-ng executors are used. Valid values are 0 and 1; the default is 1. 🎀
  • auto_executor_selection bool — automatically determines which executors to use. At present, this is done by inserting use statements for the namespace a config option has. The namespace is separated from the config option with a dash (-). Valid values are 0 and 1; the default is 1. 💅
  • use_hostname_for_dhcp bool — automatically learns the hostname property used for DHCP configuration by querying the system hostname using uname(2). This is basically equivalent to hostname $(hostname) without having to specify any configuration. Valid values are 0 and 1; the default is 1. 🦋
  • allow_any_iface_as_template bool — enables any interface to act as a template for another interface. This is presently the default, but it is deprecated. An admin may choose to disable this setting in order to require inheritance from specified templates. Valid values are 0 and 1; the default is 1. 💀
🚨 deprecated vibes alert: allow_any_iface_as_template is presently the default, but it is deprecated, so don't get too attached.
  • implicit_template_conversion bool — in some legacy configs, a template may be declared as an iface, and ifupdown-ng automatically converts those declarations to a proper template. If this setting is disabled, inheritance will continue to work against non-template interfaces without converting them to a template. Valid values are 0 and 1; the default is 1. 🧚
  • compat_create_interfaces bool — denotes whether or not to create interfaces when compat_* settings are active and it would be necessary to create an interface to be fully compliant. This could happen when inheriting bridge VLAN settings to an interface within a bridge's bridge-ports setting but no interface stanza is found. Valid values are 0 and 1; the default is 1. 💀
  • compat_ifupdown2_bridge_ports_inherit_vlans bool — in ifupdown2, <bridge-vids> as well as the <bridge-pvid> set on a bridge interface will be inherited by all member ports if not set explicitly. When set to 1, ifupdown-ng behaves the same way and will internally copy both options from the bridge member ports if they are not set on the member port. Valid values are 0 and 1; the default is 1. 🌈

📁 FILES 📁

  • /etc/network/ifupdown-ng.conf

👀 SEE ALSO 👀

  • interfaces(5) — the other manual you'll be living in, iykyk. 🫶

💌 AUTHORS 💌

  • Maximilian Wilhelm <max@sdn.clinic> — the icon behind this page. 👑

okay bye bestie — this was ifupdown-ng.conf(5), dated 2026-05-10 💖✨

📦 where this page comes from