# This is a template for a network interface configuration file used with ifup.
# See 'man 8 ifup' for details.
# Additionally to the following variables you can set every variable from the
# interface independent configurations files (config, dhcp, wireless) to
# overwrite the global settings.

# STARTMODE tells ifup when a interface should be set up. Possible values are:
# - auto:    start it as soon as the interface is available. Either when booting
#            or when a device is plugged or initialized at runtime
# - manual:  start it only when ifup is called manually
# - off:     will not be started at all
# - onboot:  alias for auto, deprecated, only for backward compliance
# - hotplug: alias for auto, only difference is that configurations with that
#            startmode are not considered to be mandatory if list of mandatory
#            devices is derived automatically.
STARTMODE=

# With BOOTPROTO you can choose in which mode the interface will be set up.
BOOTPROTO=

# If using a static configuration you have to set an IP address and a netmask
# or prefix length. The following examples are equivalent:
# 1) IPADDR=192.168.1.1
#    NETMASK=255.255.255.0
# 2) IPADDR=192.168.1.1
#    PREFIXLEN=24
# 3) IPADDR=192.168.1.1/24
IPADDR=
NETMASK=
PREFIXLEN=

# Set the broadcast address of this interface. If you leave it empty a default
# will be used. See DEFAULT_BROADCAST in /etc/sysconfig/network/config.
BROADCAST=

# If you'd like to set up a point to point connection you may specify the
# remote IP here.
REMOTE_IPADDR=

# Set a label for the interface. See 'multiple addresses' below.
LABEL=

# This options defines whether the script /etc/ppp/poll.tcpip is run after
# connecting to the internet via a dialup connection or not. The script
# itself calls various jobs like fetchmail, fetchnews and sendmail.
# Default to yes
RUN_POLL_TCPIP=

# Have a look at the iproute2 documentation.
SCOPE=

# Every other option from "ip address add" can be added here.
IP_OPTIONS=

# Set a specific Maximum Transmission Unit (MTU) for this interface.
MTU=

# Set a specific link level address (LLADDR), a.k.a. MAC address or hardware address, 
# for this interface (if the driver supports it).
LLADDR=

# Every other option from "ip link set" can be added here.
# Example:
#       LINK_OPTIONS="multicast off"
LINK_OPTIONS=

# Multiple addresses
#    You can extend the variable name 'IPADDR' by any string you like (IPADDR_1,
#    IPADDR_FOO, IPADDRxxx, ...) and use these variables for your IP addresses.
#    If you need some additional parameters for these addresses, then just add
#    the same extension to these variable names.
#    IPADDR_AAA=1.2.3.4
#    NETMASK_AAA=255.0.0.0
#    BROADCAST_AAA=1.2.3.55
#    IPADDR_BBB=10.10.2.3/16
#    LABEL_BBB=BBB
#    an so on ...
#
# You do not need to set a label for any address. But then you should not use
# ifconfig any longer; go and use ip. If you want to use ifconfig then omit the
# label for your main address and set a label for every additional address.

# Routing:
# If you need special routes for a configuration, then use a file named
# ifroute-<config> where <config> is the same string as in ifcfg-<config>.
# It has the same syntax like routes except one difference:
# If you omit the interface name (4th field) in the ifroute file it will be
# set to the current interface name when setting up the interface. You need to
# do this with hotpluggable devices, where you do not know which interface name
# they will get at the time when you plug them.
# See man 5 routes.


# Multiple DHCP clients:
#
# With two or more DHCP clients running, they would concurrently try to replace
# the default route or rewrite resolv.conf, rewrite ntp.conf etc. There are two
# ways of dealing with this conflict (and it is a conflict, because you can
# have only one default route even though routes are stackable, and there can
# only be one resolv.conf file):
#
#  1) allow both clients to do that stuff. This would work in many cases if
#     only one of the interfaces is used at a time. However, it would lead to
#     undefined behaviour.
#
#  2) allow only one of the DHCP clients to do that stuff. This implies
#     that there would be a "primary" interface and a "secondary". This is the
#     assumption the default configuration is based on. But since the system
#     can't guess which interface is "more important" and should have the
#     default route and resolver configuration associated with it, it simply
#     chooses the first interface that is started with DHCP to be
#     "authoritative".  Which one that is can be influenced by adding
#     DHCLIENT_PRIMARY_DEVICE=yes to one of the /etc/sysconfig/network/ifcfg-*
#     files. This can even be added to more than one file, to achieve the
#     behaviour described in 1).  Thus, there is the flexibility to do it
#     either way.
#
# Per default, only the DHCP client that is started first will be allowed to
# change the default route / resolver configuration etc.  All other running
# clients will only configure the interface with an address, but not change
# "global" configuration.
#
# Thus, to specifically allow an interface's DHCP client to change "global"
# configuration, set the following variable to "yes":
DHCLIENT_PRIMARY_DEVICE=

# Even more finegrained control can be excerted by setting any of the variables
# from /etc/sysconfig/network/dhcp here:
DHCLIENT_DEBUG=
DHCLIENT_SET_HOSTNAME=
DHCLIENT_SET_DOMAINNAME=
DHCLIENT_KEEP_SEARCHLIST=
DHCLIENT_MODIFY_RESOLV_CONF=
DHCLIENT_SET_DEFAULT_ROUTE=
DHCLIENT_MODIFY_NTP_CONF=
DHCLIENT_MODIFY_NIS_CONF=
DHCLIENT_TIMEOUT=
DHCLIENT_REBOOT_TIMEOUT=
DHCLIENT_CLIENT_ID=
DHCLIENT_HOSTNAME_OPTION=
DHCLIENT_VENDOR_CLASS_ID=
DHCLIENT_LEASE_TIME=
DHCLIENT_ADDITIONAL_OPTIONS=

