| 1 |
# This is an example configuration file for ifupdown-ng, which allows |
| 2 |
# the system administrator to configure the behaviour of ifupdown-ng. |
| 3 |
# |
| 4 |
# The settings specified here are the defaults of ifupdown-ng. |
| 5 |
|
| 6 |
# allow_addon_scripts: |
| 7 |
# Enable support for /etc/if-X.d addon scripts. These are used for |
| 8 |
# compatibility with legacy setups, and may be disabled for performance |
| 9 |
# improvements in setups where only ifupdown-ng executors are used. |
| 10 |
# Valid values are 0 and 1, the default is 1. |
| 11 |
allow_addon_scripts = 1 |
| 12 |
|
| 13 |
# allow_any_iface_as_template: |
| 14 |
# Enable any interface to act as a template for another interface. |
| 15 |
# This is presently the default, but is deprecated. An admin may choose |
| 16 |
# to disable this setting in order to require inheritance from specified |
| 17 |
# templates. Valid values are 0 and 1, the default is 1. |
| 18 |
allow_any_iface_as_template = 1 |
| 19 |
|
| 20 |
# auto_executor_selection: |
| 21 |
# Automatically determine which executors are needed to bring up an |
| 22 |
# interface. An admin may choose to disable this setting and explicitly |
| 23 |
# define which executors to use with `use` statements. |
| 24 |
# Valid values are 0 and 1, the default is 1. |
| 25 |
auto_executor_selection = 1 |
| 26 |
|
| 27 |
# compat_create_interfaces: |
| 28 |
# Denotes where or not to create interfaces when compat_* settings are |
| 29 |
# active and it would be necessary to create an interface to be fully |
| 30 |
# compliant. This could happen when inheriting bridge VLAN settings to |
| 31 |
# an interface within a bridges bridge-ports setting but no interface |
| 32 |
# stanza is found. Valid values are 0 and 1, the default is 1. |
| 33 |
compat_create_interfaces = 1 |
| 34 |
|
| 35 |
# compat_ifupdown2_bridge_ports_inherit_vlans: |
| 36 |
# In ifupdown2 <bridge-vids> as well as the <bridge-pvid> set on a bridge |
| 37 |
# interface will be inherited by all member ports if not set explicitly. |
| 38 |
# When set to 1 ifupdown-ng behaves the same way and will internally copy |
| 39 |
# both options from the bridge member ports if they are not set on the |
| 40 |
# member port. Valid values are 0 and 1, the default is 1. |
| 41 |
compat_ifupdown2_bridge_ports_inherit_vlans = 1 |
| 42 |
|
| 43 |
# implicit_template_conversion: |
| 44 |
# In some legacy configs, a template may be declared as an iface, and |
| 45 |
# ifupdown-ng automatically converts those declarations to a proper |
| 46 |
# template. If this setting is disabled, inheritance will continue to |
| 47 |
# work against non-template interfaces without converting them to a |
| 48 |
# template. Valid values are 0 and 1, the default is 1. |
| 49 |
implicit_template_conversion = 1 |
| 50 |
|
| 51 |
# use_hostname_for_dhcp: |
| 52 |
# Automatically learn the hostname property, used for DHCP configuration |
| 53 |
# by querying the system hostname using uname(2). This is basically |
| 54 |
# equivalent to `hostname $(hostname)` without having to specify any |
| 55 |
# configuration. Valid values are 0 and 1, the default is 1. |
| 56 |
use_hostname_for_dhcp = 1 |