Blame doc/sysconfig.txt

rpm-build 133ac4
rpm-build 133ac4
=======================
rpm-build 133ac4
rpm-build 133ac4
Generic options:
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/*
rpm-build 133ac4
rpm-build 133ac4
   CGROUP_DAEMON=
rpm-build 133ac4
     List of control groups that the daemon will be run in. For example,
rpm-build 133ac4
     CGROUP_DAEMON="cpu:daemons cpuacct:/" will run it in the daemons
rpm-build 133ac4
     group for the CPU controller, and the '/' group for the CPU accounting
rpm-build 133ac4
     controller.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/authconfig
rpm-build 133ac4
rpm-build 133ac4
  used by authconfig to store information about the system's user
rpm-build 133ac4
  information and authentication setup; changes made to this file
rpm-build 133ac4
  have no effect until the next time authconfig is run
rpm-build 133ac4
rpm-build 133ac4
    USEHESIOD=no
rpm-build 133ac4
      Whether or not the hesiod naming service is in use.  If not set,
rpm-build 133ac4
      authconfig examines the passwd setting in /etc/nsswitch.conf.
rpm-build 133ac4
    USELDAP=no
rpm-build 133ac4
      Whether or not LDAP is used as a naming service.  If not set,
rpm-build 133ac4
      authconfig examines the passwd setting in /etc/nsswitch.conf.
rpm-build 133ac4
    USENIS=no
rpm-build 133ac4
      Whether or not NIS is in use.  If not set, authconfig examines
rpm-build 133ac4
      the passwd setting in /etc/nsswitch.conf.
rpm-build 133ac4
rpm-build 133ac4
    USEKERBEROS=no
rpm-build 133ac4
      Whether or not Kerberos is in use.  If not set, authconfig examines
rpm-build 133ac4
      the settings in /etc/pam.d/system-auth.
rpm-build 133ac4
    USELDAPAUTH=no
rpm-build 133ac4
      Whether or not LDAP is being used for authentication.  If not set,
rpm-build 133ac4
      authconfig examines the settings in /etc/pam.d/system-auth.  Note
rpm-build 133ac4
      that this option is separate from USELDAP, and that neither implies
rpm-build 133ac4
      the other.
rpm-build 133ac4
    USEMD5=no
rpm-build 133ac4
      Whether or not MD5-based hashing should be used when setting passwords.
rpm-build 133ac4
      If not set, authconfig examines the settings in /etc/pam.d/system-auth.
rpm-build 133ac4
      This option affects authentication using both local files and LDAP.
rpm-build 133ac4
    USESHADOW=no
rpm-build 133ac4
      Whether or not shadow passwords are in use.  If not set, authconfig
rpm-build 133ac4
      checks for the existence of /etc/shadow.
rpm-build 133ac4
    USESMBAUTH=no
rpm-build 133ac4
      Whether or not SMB authentication is in use.  If not set, authconfig
rpm-build 133ac4
      examines the settings in /etc/pam.d/system-auth.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/autofsck
rpm-build 133ac4
rpm-build 133ac4
  does not normally exist; if it does, it can influence a choice
rpm-build 133ac4
  whether or not to fsck after a crash
rpm-build 133ac4
rpm-build 133ac4
    AUTOFSCK_DEF_CHECK=no
rpm-build 133ac4
      If the user does not respond, choose whether or not to fsck
rpm-build 133ac4
    AUTOFSCK_SINGLEUSER=
rpm-build 133ac4
      If this is set, drop to single user mode before fsck.
rpm-build 133ac4
    
rpm-build 133ac4
/etc/sysconfig/init:
rpm-build 133ac4
rpm-build 133ac4
  BOOTUP=<some bootup mode>
rpm-build 133ac4
     BOOTUP=graphical means use X Windows graphical boot up
rpm-build 133ac4
     BOOTUP=color means colorized text mode boot display. 
rpm-build 133ac4
     BOOTUP=verbose means old style display
rpm-build 133ac4
     Anything else means simplified display, but without color or ANSI-formatting
rpm-build 133ac4
  LOGLEVEL=
rpm-build 133ac4
     Sets the initial console logging level for the kernel.
rpm-build 133ac4
     The default is 7. 8 means everything (including debugging);
rpm-build 133ac4
     1 means nothing except kernel panics. syslogd will override
rpm-build 133ac4
     this once it starts.
rpm-build 133ac4
  RES_COL=
rpm-build 133ac4
     Column of the screen to start status labels at. Defaults to 60
rpm-build 133ac4
  MOVE_TO_COL=
rpm-build 133ac4
     A command to move the cursor to $RES_COL. Defaults to nasty
rpm-build 133ac4
     ANSI sequences output by echo -e.
rpm-build 133ac4
  SETCOLOR_SUCCESS=
rpm-build 133ac4
     A command to set the color to a color indicating success.
rpm-build 133ac4
     Defaults to nasty ANSI sequences output by echo -e setting
rpm-build 133ac4
     the color to green.
rpm-build 133ac4
  SETCOLOR_FAILURE=
rpm-build 133ac4
     A command to set the color to a color indicating failure.
rpm-build 133ac4
     Defaults to nasty ANSI sequences output by echo -e setting
rpm-build 133ac4
     the color to red.
rpm-build 133ac4
  SETCOLOR_WARNING=
rpm-build 133ac4
     A command to set the color to a color indicating warning.
rpm-build 133ac4
     Defaults to nasty ANSI sequences output by echo -e setting
rpm-build 133ac4
     the color to yellow.
rpm-build 133ac4
  SETCOLOR_NORMAL=
rpm-build 133ac4
     A command to set the color to 'normal'. Defaults to nasty
rpm-build 133ac4
     ANSI sequences output by echo -e.
rpm-build 133ac4
  PROMPT=yes|no
rpm-build 133ac4
     Set to 'yes' to enable the key check for interactive mode as well as
rpm-build 133ac4
     asking if a filesystem check should be done. Default is 'no' and
rpm-build 133ac4
     the kernel command line option "forcefsck" can be used to check the
rpm-build 133ac4
     filesystems and "confirm" can be used to enable interactive startup
rpm-build 133ac4
     questions.
rpm-build 133ac4
rpm-build 133ac4
  obsoleted values from earlier releases:
rpm-build 133ac4
rpm-build 133ac4
    MAGIC_SYSRQ=yes|no
rpm-build 133ac4
       Setting this to 'no' used to disable the magic sysrq key and
rpm-build 133ac4
       Stop-A (break on serial console) on SPARC. This setting has been
rpm-build 133ac4
       moved into kernel.sysrq and kernel.stop-a settings respectively in
rpm-build 133ac4
       sysctl.d/00-system.conf. Setting either of them there to 0 disables
rpm-build 133ac4
       it, setting it to 1 enables it.
rpm-build 133ac4
    STOP_A=yes|no
rpm-build 133ac4
       Setting this to 'no' used to disable the Stop-A (break on
rpm-build 133ac4
       serial console) key on SPARC.
rpm-build 133ac4
       This setting has been moved into kernel.stop-a setting in
rpm-build 133ac4
       sysctl.d/00-system.conf. Setting it there to 0 disables it,
rpm-build 133ac4
       setting it to 1 enables it. The setting should be present
rpm-build 133ac4
       on SPARC only.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/keyboard:
rpm-build 133ac4
rpm-build 133ac4
  KEYTABLE=<keytable file>
rpm-build 133ac4
     for example: KEYTABLE="/usr/lib/kbd/keytables/us.map"
rpm-build 133ac4
    
rpm-build 133ac4
     If you dump a keymap (using 'dumpkeys') to
rpm-build 133ac4
	/etc/sysconfig/console/default.kmap
rpm-build 133ac4
     it will be loaded on bootup before filesystems are mounted/checked.
rpm-build 133ac4
     This could be useful if you need to emergency type the root password.
rpm-build 133ac4
     This has to be a dumped keymap, as opposed to copying the shipped
rpm-build 133ac4
     keymap files, as the shipped files include other maps from the
rpm-build 133ac4
     /usr/lib/kbd/keytables directory.
rpm-build 133ac4
     
rpm-build 133ac4
  KEYBOARDTYPE=sun|pc
rpm-build 133ac4
    on SPARC only, sun means a sun keyboard is attached on /dev/kbd,
rpm-build 133ac4
    pc means a PS/2 keyboard is on ps/2 port.
rpm-build 133ac4
  
rpm-build 133ac4
/etc/sysconfig/mouse:
rpm-build 133ac4
rpm-build 133ac4
  MOUSETYPE=microsoft|mouseman|mousesystems|ps/2|msbm|logibm|atibm|
rpm-build 133ac4
    logitech|mmseries|mmhittab
rpm-build 133ac4
  XEMU3=yes|no (emulate three buttons with two buttons whenever
rpm-build 133ac4
    necessary, most notably in X)
rpm-build 133ac4
  DEVICE= (the device of the mouse)
rpm-build 133ac4
rpm-build 133ac4
  In addition, /dev/mouse points to the mouse device.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network:
rpm-build 133ac4
rpm-build 133ac4
  NETWORKING=yes|no
rpm-build 133ac4
  GATEWAY=<gateway IP>
rpm-build 133ac4
  GATEWAYDEV=<gateway device to use, when multiple devices have GATEWAY=> (e.g. eth0)
rpm-build 133ac4
  NISDOMAIN=<nis domain name>
rpm-build 133ac4
  NOZEROCONF=
rpm-build 133ac4
    Set this to not set a route for dynamic link-local addresses.
rpm-build 133ac4
rpm-build 133ac4
  NETWORKDELAY=<delay in seconds>
rpm-build 133ac4
    Delay in seconds after all network interfaces are initialized.  Useful if
rpm-build 133ac4
    network has spanning tree running and must wait for STP convergence.
rpm-build 133ac4
    Default: 0 (no delay)
rpm-build 133ac4
rpm-build 133ac4
  IFDOWN_ON_SHUTDOWN=yes|no
rpm-build 133ac4
    If yes, do bring interfaces down during system shutdown. If no, leave them
rpm-build 133ac4
    in their current state (this is only supported on hosts using systemd).
rpm-build 133ac4
    Default: yes (bring interfaces down)
rpm-build 133ac4
rpm-build 133ac4
rpm-build 133ac4
  IPV6FORWARDING=yes|no
rpm-build 133ac4
    Enable or disable global forwarding of incoming IPv6 packets 
rpm-build 133ac4
    on all interfaces.
rpm-build 133ac4
    Note: Actual packet forwarding cannot be controlled per-device, use netfilter6 for such issues
rpm-build 133ac4
    Default: no
rpm-build 133ac4
rpm-build 133ac4
  IPV6_AUTOCONF=yes|no
rpm-build 133ac4
    Sets the default for device-based autoconfiguration.
rpm-build 133ac4
    Default: yes if IPV6FORWARDING=no, no if IPV6FORWARDING=yes
rpm-build 133ac4
  IPV6_ROUTER=yes|no
rpm-build 133ac4
    Sets the default for device-based Host/Router behaviour.
rpm-build 133ac4
    Default: yes if IPV6FORWARDING=yes, no if IPV6FORWARDING=no
rpm-build 133ac4
  IPV6_AUTOTUNNEL=yes|no
rpm-build 133ac4
    Controls automatic IPv6 tunneling.
rpm-build 133ac4
    Default: no
rpm-build 133ac4
rpm-build 133ac4
  IPV6_DEFAULTGW=<IPv6 address[%interface]> (optional)
rpm-build 133ac4
    Add a default route through specified gateway
rpm-build 133ac4
    An interface can be specified: required for link-local addresses
rpm-build 133ac4
    Examples:
rpm-build 133ac4
      IPV6_DEFAULTGW="3ffe:ffff:1234:5678::1"
rpm-build 133ac4
        Add default route through 3ffe:ffff:1234:5678::1
rpm-build 133ac4
      IPV6_DEFAULTGW="3ffe:ffff:1234:5678::1%eth0"
rpm-build 133ac4
        Add default route through 3ffe:ffff:1234:5678::1 and device eth0
rpm-build 133ac4
      IPV6_DEFAULTGW="fe80::1%eth0"
rpm-build 133ac4
        Add default route through fe80::1 and device eth0
rpm-build 133ac4
rpm-build 133ac4
  Note: if IPV6_DEFAULTGW is specified with %interface scope and it
rpm-build 133ac4
        doesn't match IPV6_DEFAULTDEV, IPV6_DEFAULTDEV is ignored.
rpm-build 133ac4
  Note: it's preferred to use %interface for all addresses, not
rpm-build 133ac4
        just link-local if you have multiple IPv6-enabled interfaces.
rpm-build 133ac4
rpm-build 133ac4
  IPV6_DEFAULTDEV=<interface> (optional)
rpm-build 133ac4
    Add a default route through specified interface without specifying next hop
rpm-build 133ac4
    Type of interface will be tested whether this is allowed
rpm-build 133ac4
    Examples:
rpm-build 133ac4
      IPV6_DEFAULTDEV="eth0" INVALID example!
rpm-build 133ac4
      IPV6_DEFAULTDEV="ppp0"
rpm-build 133ac4
      IPV6_DEFAULTDEV="sit1"
rpm-build 133ac4
    Examples for 6to4
rpm-build 133ac4
      IPV6_DEFAULTDEV="tun6to4"
rpm-build 133ac4
        Add default route through dedicated 6to4 tunnel device "tun6to4", if configured
rpm-build 133ac4
rpm-build 133ac4
  Note: "tun6to4" does not support an additional IPV6_DEFAULTGW.
rpm-build 133ac4
        Other interfaces prefer IPV6_DEFAULTGW, if specified.
rpm-build 133ac4
rpm-build 133ac4
  IPV6_RADVD_PIDFILE=<pid-file> (optional)
rpm-build 133ac4
    Location of PID file for controlling radvd, see IPV6_CONTROL_RADVD
rpm-build 133ac4
    Default: "/run/radvd/radvd.pid"
rpm-build 133ac4
    Example:
rpm-build 133ac4
       IPV6_RADVD_PIDFILE="/some/other/location/radvd.pid"
rpm-build 133ac4
  IPV6TO4_RADVD_PIDFILE=<pid-file> (obsolete)
rpm-build 133ac4
    As above, still supported for a while for backward compatibility.
rpm-build 133ac4
  IPV6_RADVD_TRIGGER_ACTION=startstop|reload|restart|SIGHUP (optional)
rpm-build 133ac4
    How to trigger radvd in case of 6to4 or PPP action
rpm-build 133ac4
     startstop: radvd starts if interface goes up and stops
rpm-build 133ac4
       if interface goes down using initscript call of radvd with related parameter
rpm-build 133ac4
     reload|restart: initscript of radvd is called with this parameter
rpm-build 133ac4
     SIGHUP: signal HUP is sent to radvd, pidfile must be specified, if not the default
rpm-build 133ac4
    Default: SIGHUP
rpm-build 133ac4
rpm-build 133ac4
  IPv6 options above can be overridden in interface-specific configuration.
rpm-build 133ac4
rpm-build 133ac4
  obsoleted values from earlier releases:
rpm-build 133ac4
rpm-build 133ac4
    FORWARD_IPV4=yes|no
rpm-build 133ac4
      Create a new file in /etc/sysctl.d/ with the net.ipv4.ip_forward
rpm-build 133ac4
      setting instead. Setting it to 1 there enables IP forwarding,
rpm-build 133ac4
      setting it to 0 disables it (which is the default for RFC compliance).
rpm-build 133ac4
rpm-build 133ac4
    NETWORKWAIT=yes|no
rpm-build 133ac4
      This is not used with the move to systemd.
rpm-build 133ac4
rpm-build 133ac4
    HOSTNAME=<fqdn by default, but whatever hostname you want>
rpm-build 133ac4
      This is now configured in /etc/hostname.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/static-routes-ipv6:
rpm-build 133ac4
  Contains lines of the form:
rpm-build 133ac4
rpm-build 133ac4
    <device> IPv6-network IPv6-gateway
rpm-build 133ac4
    <tunneldevice> IPv6-network
rpm-build 133ac4
rpm-build 133ac4
  <device> must be a device name to have the route brought up and
rpm-build 133ac4
  down with the device
rpm-build 133ac4
rpm-build 133ac4
  For example:
rpm-build 133ac4
  
rpm-build 133ac4
  eth0   fec0:0:0:2::/64                         fec0:0:0:1:0:0:0:20
rpm-build 133ac4
   adds a route for IPv6 network fec0:0:0:2::/64 through fec0:0:0:1:0:0:0:20
rpm-build 133ac4
   
rpm-build 133ac4
  eth0    2000::/3	                         3ffe:ffff:0:1::1
rpm-build 133ac4
   so-called "default" routes for clients
rpm-build 133ac4
rpm-build 133ac4
  sit1    2000::/3
rpm-build 133ac4
   adds routes through dedicated tunnel interface sit1
rpm-build 133ac4
rpm-build 133ac4
  tun6to4  3ffe:ffff:1234::/56			
rpm-build 133ac4
   adds routes through hardwired 6to4 tunnel interface tun6to4
rpm-build 133ac4
  tun6to4  3ffe:ffff:5678::/56			::5.6.7.8
rpm-build 133ac4
   adds routes through hardwired 6to4 tunnel interface tun6to4,
rpm-build 133ac4
   specifying next hop   
rpm-build 133ac4
rpm-build 133ac4
  Notes:
rpm-build 133ac4
    * default routes (such as the "2000::/3" shown above) should be set with
rpm-build 133ac4
       IPV6_DEFAULTGW and IPV6_DEFAULTDEV, see more above.
rpm-build 133ac4
    * tunnel device "sit0" is not supported here, routes will never be applied
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/routed:
rpm-build 133ac4
rpm-build 133ac4
  SILENT=yes|no
rpm-build 133ac4
  EXPORT_GATEWAY=yes|no
rpm-build 133ac4
  
rpm-build 133ac4
/etc/sysconfig/rawdevices:
rpm-build 133ac4
rpm-build 133ac4
  This is used for setting up raw device to block device mappings.
rpm-build 133ac4
  It has the format:
rpm-build 133ac4
  	<rawdev> <major> <minor>
rpm-build 133ac4
        <rawdev> <blockdev>
rpm-build 133ac4
  For example: 
rpm-build 133ac4
     /dev/raw/raw1 /dev/sda1
rpm-build 133ac4
     /dev/raw/raw2 8 5
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/pcmcia:
rpm-build 133ac4
rpm-build 133ac4
  PCMCIA=yes|no
rpm-build 133ac4
  PCIC=i82365|tcic
rpm-build 133ac4
  PCIC_OPTS=<socket driver (i82365 or tcic) timing parameters>
rpm-build 133ac4
  CORE_OPTS=<pcmcia_core options>
rpm-build 133ac4
  CARDMGR_OPTS=<cardmgr options>
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/amd:
rpm-build 133ac4
rpm-build 133ac4
  ADIR=/.automount  (normally never changed)
rpm-build 133ac4
  MOUNTPTS='/net /etc/amd.conf'  (standard automount stuff)
rpm-build 133ac4
  AMDOPTS=  (extra options for AMD)
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/tape:
rpm-build 133ac4
rpm-build 133ac4
  DEV=/dev/nst0
rpm-build 133ac4
    Tape device.  Use the non-rewinding one for these scripts.
rpm-build 133ac4
  
rpm-build 133ac4
    For SCSI tapes this is /dev/nst#, where # is the number of the
rpm-build 133ac4
    tape drive you want to use.  If you only have one then use
rpm-build 133ac4
    nst0.
rpm-build 133ac4
 
rpm-build 133ac4
    For IDE tapes you use /dev/ht#, where # is the number of the tape
rpm-build 133ac4
    drive you want to use (usually ht0).
rpm-build 133ac4
 
rpm-build 133ac4
    For floppy tape drives use /dev/ftape.
rpm-build 133ac4
rpm-build 133ac4
  ADMIN=root
rpm-build 133ac4
    Person to mail to if the backup fails for any reason
rpm-build 133ac4
rpm-build 133ac4
  SLEEP=5
rpm-build 133ac4
    Time to sleep between tape operations.  Some drives need a bit
rpm-build 133ac4
    more than others, but 5 seems to work for 8mm, 4mm, and DLT
rpm-build 133ac4
rpm-build 133ac4
  BLOCKSIZE=32768
rpm-build 133ac4
    This worked fine for 8mm, then 4mm, and now DLT.  An optimal
rpm-build 133ac4
    setting is probably however much data your drive writes at one
rpm-build 133ac4
    time.
rpm-build 133ac4
rpm-build 133ac4
  SHORTDATE=$(date +%y:%m:%d:%H:%M)
rpm-build 133ac4
    A short date string, used in backup log filenames.
rpm-build 133ac4
rpm-build 133ac4
  DAY=$(date +log-%y:%m:%d)
rpm-build 133ac4
    This is used for the log file directory.
rpm-build 133ac4
rpm-build 133ac4
  DATE=$(date)
rpm-build 133ac4
    Regular date string, used in log files.
rpm-build 133ac4
rpm-build 133ac4
  LOGROOT=/var/log/backup
rpm-build 133ac4
    Root of the logging directory
rpm-build 133ac4
rpm-build 133ac4
  LIST=$LOGROOT/incremental-list
rpm-build 133ac4
    This is the file name the incremental backup will use to store
rpm-build 133ac4
    the incremental list.  It will be $LIST-{some number}.
rpm-build 133ac4
rpm-build 133ac4
  DOTCOUNT=$LOGROOT/.count
rpm-build 133ac4
    For counting as you go to know which incremental list to use
rpm-build 133ac4
rpm-build 133ac4
  COUNTER=$LOGROOT/counter-file
rpm-build 133ac4
    For rewinding when done...might not use.
rpm-build 133ac4
rpm-build 133ac4
  BACKUPTAB=/etc/backuptab
rpm-build 133ac4
    The file in which we keep our list of backup(s) we want to make.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/saslauthd:
rpm-build 133ac4
rpm-build 133ac4
  used by the saslauthd init script (part of the cyrus-sasl package) to
rpm-build 133ac4
  control which arguments are passed to saslauthd at startup time; changes
rpm-build 133ac4
  made to this file have no effect until saslauthd is restarted
rpm-build 133ac4
rpm-build 133ac4
  MECH=shadow
rpm-build 133ac4
    controls which data source saslauthd will consult when checking user
rpm-build 133ac4
    passwords; run 'saslauthd -v' to get a full list of available
rpm-build 133ac4
    authentication mechanisms
rpm-build 133ac4
  SOCKETDIR=/run/saslauthd
rpm-build 133ac4
    controls in which directory saslauthd will be directed to create its
rpm-build 133ac4
    listening socket; any change to this value will require a corresponding
rpm-build 133ac4
    change in client configuration files
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/sendmail:
rpm-build 133ac4
  DAEMON=yes|no
rpm-build 133ac4
    yes implies -bd (i.e., listen on port 25 for new mail)
rpm-build 133ac4
  QUEUE=1h
rpm-build 133ac4
    given to sendmail as -q$QUEUE
rpm-build 133ac4
    -q option is not given to sendmail if /etc/sysconfig/sendmail
rpm-build 133ac4
    exists and QUEUE is empty or undefined.
rpm-build 133ac4
rpm-build 133ac4
Files in /etc/sysconfig/network-scripts/
rpm-build 133ac4
========================================
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifup:
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifdown:
rpm-build 133ac4
rpm-build 133ac4
  Symlinks to /sbin/ifup and /sbin/ifdown, respectively.
rpm-build 133ac4
  These are the only two scripts "in" this directory that should
rpm-build 133ac4
  be called directly; these two scripts call all the other
rpm-build 133ac4
  scripts as needed.  These symlinks are here for legacy purposes --
rpm-build 133ac4
  only /sbin/ifup and /sbin/ifdown should currently be used
rpm-build 133ac4
  at the user level.
rpm-build 133ac4
rpm-build 133ac4
  These scripts take one argument normally: the name of the device
rpm-build 133ac4
  (e.g. eth0).  They are called with a second argument of "boot"
rpm-build 133ac4
  during the boot sequence so that devices that are not meant to
rpm-build 133ac4
  be brought up on boot (ONBOOT=no, see below) can be ignored at
rpm-build 133ac4
  that time.
rpm-build 133ac4
rpm-build 133ac4
  Also, interfaces may be brought up via the hotplug scripts;
rpm-build 133ac4
  in this case, HOTPLUG=no needs to be set to no to avoid this.
rpm-build 133ac4
  This is useful e.g. to prevent bonding device activation by merely
rpm-build 133ac4
  loading the bonding kernel module.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/init.ipv6-global:
rpm-build 133ac4
  Not really a public file.  Contains different basic settings that
rpm-build 133ac4
  are set from /etc/[rc.d]/init.d/network at different stages of
rpm-build 133ac4
  network initialization.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/network-functions:
rpm-build 133ac4
rpm-build 133ac4
  Not really a public file.  Contains functions which the scripts use
rpm-build 133ac4
  for bringing interfaces up and down.  In particular, it contains
rpm-build 133ac4
  most of the code for handling alternative interface configurations.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/network-functions-ipv6:
rpm-build 133ac4
rpm-build 133ac4
  Not really a public file.  Contains functions which the scripts use
rpm-build 133ac4
  for bringing IPv6 on interfaces up and down, like addresses, routes,
rpm-build 133ac4
  forwarding handling and static or automatic tunneling.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifcfg-<interface-name> and
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifcfg-<interface-name>:<alias-name>:
rpm-build 133ac4
rpm-build 133ac4
  The first defines an interface, and the second contains
rpm-build 133ac4
  only the parts of the definition that are different in a
rpm-build 133ac4
  "alias" (or alternative) interface.  For example, the
rpm-build 133ac4
  network numbers might be different, but everything else
rpm-build 133ac4
  might be the same, so only the network numbers would be
rpm-build 133ac4
  in the alias file, but all the device information would
rpm-build 133ac4
  be in the base ifcfg file.
rpm-build 133ac4
rpm-build 133ac4
  The items that can be defined in an ifcfg file depend on the
rpm-build 133ac4
  interface type.  The really obvious ones I'm not going to
rpm-build 133ac4
  bother to define; you can figure out what "IPADDR" is, I
rpm-build 133ac4
  think...  :-)
rpm-build 133ac4
rpm-build 133ac4
  Base items:
rpm-build 133ac4
    NAME=<friendly name for users to see>
rpm-build 133ac4
      Most important for PPP.  Only used in front ends.
rpm-build 133ac4
    DEVICE=
rpm-build 133ac4
      devices where it is the "logical name")>
rpm-build 133ac4
    IPADDRn=
rpm-build 133ac4
    PREFIXn=
rpm-build 133ac4
      Network prefix.  It is used for all configurations except aliases
rpm-build 133ac4
      and ippp devices.  It takes precedence over NETMASK when both
rpm-build 133ac4
      PREFIX and NETMASK are set.
rpm-build 133ac4
    NETMASKn=
rpm-build 133ac4
      Subnet mask; just useful for aliases and ippp devices.  For all other
rpm-build 133ac4
      configurations, use PREFIX instead.
rpm-build 133ac4
rpm-build 133ac4
    The "n" is expected to be consecutive positive integers starting from 0.
rpm-build 133ac4
    It can be omitted if there is only one address being configured.
rpm-build 133ac4
rpm-build 133ac4
    GATEWAY=
rpm-build 133ac4
    METRIC=
rpm-build 133ac4
      Metric for the default route using GATEWAY
rpm-build 133ac4
    ONBOOT=yes|no (not valid for alias devices; use ONPARENT)
rpm-build 133ac4
    HOTPLUG=yes|no
rpm-build 133ac4
    USERCTL=yes|no
rpm-build 133ac4
    BOOTPROTO=none|bootp|dhcp
rpm-build 133ac4
      'bootp' or 'dhcp' cause a DHCP client to run on the device. Any other
rpm-build 133ac4
      value causes any static configuration in the file to be applied.
rpm-build 133ac4
    VLAN=yes|no
rpm-build 133ac4
    MTU=
rpm-build 133ac4
      Default MTU for this device
rpm-build 133ac4
    WINDOW=
rpm-build 133ac4
      Default window for routes from this device
rpm-build 133ac4
    PEERDNS=yes|no
rpm-build 133ac4
      modify /etc/resolv.conf if peer uses msdns extension (PPP only) or
rpm-build 133ac4
      DNS{1,2} are set, or if using dhclient. default to "yes".
rpm-build 133ac4
    DNS{1,2}=<ip address>
rpm-build 133ac4
      provide DNS addresses that are dropped into the resolv.conf
rpm-build 133ac4
      file if PEERDNS is not set to "no".
rpm-build 133ac4
    SCOPE=
rpm-build 133ac4
      Set to "scope SCOPE-ID" to set a non-default scope for a statically
rpm-build 133ac4
      configured IP address.
rpm-build 133ac4
    SRCADDR=
rpm-build 133ac4
      use the specified source address for outgoing packets
rpm-build 133ac4
    HWADDR=
rpm-build 133ac4
      ethernet hardware address for this device
rpm-build 133ac4
    MACADDR=
rpm-build 133ac4
      Set the hardware address for this device to this.
rpm-build 133ac4
      Use of this in conjunction with HWADDR= may cause
rpm-build 133ac4
      unintended behavior.
rpm-build 133ac4
    NOZEROCONF=
rpm-build 133ac4
      Set this to not set a route for dynamic link-local addresses
rpm-build 133ac4
      over this device.
rpm-build 133ac4
    PERSISTENT_DHCLIENT=yes|no|1|0
rpm-build 133ac4
      Without this option, or if it is 'no'/'0', and BOOTPROTO=dhcp,
rpm-build 133ac4
      dhclient is run for the interface in "one-shot" mode; if the 
rpm-build 133ac4
      dhcp server does not respond for a configurable timeout, then
rpm-build 133ac4
      dhclient exits and the interface is not brought up - 
rpm-build 133ac4
      the '-1' option is given to dhclient.
rpm-build 133ac4
      If PERSISTENT_DHCLIENT=yes, then dhclient will keep on trying
rpm-build 133ac4
      to contact the dhcp server when it does not respond - no '-1'
rpm-build 133ac4
      option is given to dhclient. Note: this disables the automatic
rpm-build 133ac4
      checking for the presence of a link before starting dhclient.
rpm-build 133ac4
    DHCPRELEASE=yes|no|1|0
rpm-build 133ac4
      With this option set to 'yes' (1), when a dhcp configured
rpm-build 133ac4
      interface is brought down with 'ifdown', the lease will be
rpm-build 133ac4
      released. Otherwise, leases are not released.
rpm-build 133ac4
rpm-build 133ac4
    NO_DHCP_HOSTNAME=yes|no|1|0
rpm-build 133ac4
      Tells initscripts to not obtain hostname from DHCP server in the ifup-post
rpm-build 133ac4
      phase. This option might be useful especially with static configuration of
rpm-build 133ac4
      the interface.
rpm-build 133ac4
    DHCP_SEND_HOSTNAME=yes|no|1|0
rpm-build 133ac4
      Tells initscripts whether the DHCP_HOSTNAME or DHCP_FQDN options (below)
rpm-build 133ac4
      should be sent to DHCP server.
rpm-build 133ac4
    DHCP_HOSTNAME=<hostname>
rpm-build 133ac4
      Sends the specified hostname to the DHCP server.
rpm-build 133ac4
    DHCP_FQDN=<fully.qualified.domain.name>
rpm-build 133ac4
      Sends the specified FQDN to the DHCP server.
rpm-build 133ac4
rpm-build 133ac4
    Please note when both DHCP_HOSTNAME and DHCP_FQDN are specified,
rpm-build 133ac4
    only DHCP_FQDN will be used. (Same behaviour as with NetworkManager.)
rpm-build 133ac4
rpm-build 133ac4
    DHCLIENT_IGNORE_GATEWAY=yes|no|1|0
rpm-build 133ac4
      If set to 'yes', it will cause dhclient-script to ignore any $GATEWAY
rpm-build 133ac4
      setting that may be in the ifcfg file for this interface.
rpm-build 133ac4
      Otherwise, the dhclient session which obtains an ip-address
rpm-build 133ac4
      on the same subnet as $GATEWAY will set the default route
rpm-build 133ac4
      to be via $GATEWAY, and no other dhclient session will set
rpm-build 133ac4
      the default route.
rpm-build 133ac4
    DHCLIENTARGS=
rpm-build 133ac4
      Any additional arguments to dhclient.
rpm-build 133ac4
    NM_CONTROLLED=yes|no
rpm-build 133ac4
      If set to 'no', NetworkManager will ignore this connection/device.
rpm-build 133ac4
      Defaults to 'yes'.
rpm-build 133ac4
    ZONE=
rpm-build 133ac4
      Network zone (trust level) of this connection.
rpm-build 133ac4
      If not set, default zone (specified in /etc/firewalld/firewalld.conf)
rpm-build 133ac4
      is used. To see all available zones, run 'firewall-cmd --get-zones'.
rpm-build 133ac4
    ARPCHECKn=yes|no
rpm-build 133ac4
      If set to 'no', ifup will not try to determine, if requested ip address
rpm-build 133ac4
      is used by other machine in network.
rpm-build 133ac4
      Defaults to 'yes'.
rpm-build 133ac4
    ARPUPDATE=yes|no
rpm-build 133ac4
      If set to 'no' the neighbours in current network will not be updated with
rpm-build 133ac4
      ARP information about this NIC. This is especially handy using LVS Load
rpm-build 133ac4
      Balancing with Direct Routing enabled.
rpm-build 133ac4
      Defaults to 'yes'.
rpm-build 133ac4
    IPV4_FAILURE_FATAL=yes|no
rpm-build 133ac4
      If set to yes, ifup-eth will end immediately after ipv4 dhclient fails.
rpm-build 133ac4
      Defaults to 'no'.
rpm-build 133ac4
rpm-build 133ac4
  For dynamic addressing (BOOTPROTO=dhcp) only DEVICE needs to
rpm-build 133ac4
  be set; all the rest will be determined by the boot protocol.
rpm-build 133ac4
rpm-build 133ac4
    IPV6_SET_SYSCTLS=yes|no
rpm-build 133ac4
      If set, network-scripts will attempt to set sysctls based on the setup
rpm-build 133ac4
      of the interface. For example, will try to set `accept_ra` for interfaces
rpm-build 133ac4
      where $IPV6_AUTOCONF is set to `yes`. Defaults to `yes`, set to `no` if you
rpm-build 133ac4
      want to manage these yourself.
rpm-build 133ac4
rpm-build 133ac4
  Base items being deprecated:
rpm-build 133ac4
    NETWORK=<will be calculated automatically with ipcalc>
rpm-build 133ac4
    BROADCAST=<will be calculated automatically with ipcalc>
rpm-build 133ac4
rpm-build 133ac4
  Alias specific items:
rpm-build 133ac4
    ONPARENT=yes|no
rpm-build 133ac4
      Whether to bring up the device when the parent device is brought
rpm-build 133ac4
      up.
rpm-build 133ac4
      Default: yes
rpm-build 133ac4
rpm-build 133ac4
  IPv6-only items for real interfaces:
rpm-build 133ac4
    IPV6INIT=yes|no
rpm-build 133ac4
      Enable or disable IPv6 static, DHCP, or autoconf configuration for this interface
rpm-build 133ac4
      Default: yes
rpm-build 133ac4
    IPV6FORWARDING=yes|no
rpm-build 133ac4
      Enable or disable global forwarding of incoming IPv6 packets
rpm-build 133ac4
      Note: Obsolete in interface specification!
rpm-build 133ac4
      Default: no
rpm-build 133ac4
    IPV6ADDR=<IPv6 address>[/<prefix length>]
rpm-build 133ac4
      Specify a primary static IPv6 address here
rpm-build 133ac4
      Optional, if normal host and a router advertisement daemon is on local link
rpm-build 133ac4
      Required, if node is a router and interface should route packets
rpm-build 133ac4
      Note: if prefix length is omitted, 64 is assumed
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6ADDR="3ffe:ffff:0:5::1"
rpm-build 133ac4
        IPV6ADDR="3ffe:ffff:0:1::1/128"
rpm-build 133ac4
    IPV6ADDR_SECONDARIES="<IPv6 address>[/<prefix length>] ..." (optional)
rpm-build 133ac4
      A list of secondary IPv6 addresses (e.g. useful for virtual hosting)
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6ADDR_SECONDARIES="3ffe:ffff:0:1::10 3ffe:ffff:0:2::11/128"
rpm-build 133ac4
    IPV6_MTU=<MTU of link> (optional)
rpm-build 133ac4
      Optional, dedicated MTU of this link
rpm-build 133ac4
      Note: Must be greater or equal to 1280.
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6_MTU="1280"
rpm-build 133ac4
    IPV6_PRIVACY=rfc3041
rpm-build 133ac4
      Enables RFC 3041 IPv6 privacy support if set.
rpm-build 133ac4
      Default: RFC 3041 support disabled
rpm-build 133ac4
    IPV6_FORCE_ACCEPT_RA=yes|no
rpm-build 133ac4
      By default network-scripts will set `accept_ra` only if $IPV6_AUTOCONF is
rpm-build 133ac4
      set to `yes`. If you don't want SLAAC addresses but do want to accept RA,
rpm-build 133ac4
      then set this to `yes`. Defaults to `no`.
rpm-build 133ac4
rpm-build 133ac4
  Special configuration options for multi-homed hosts etc.
rpm-build 133ac4
	IPV6_ROUTER=yes|no: Controls IPv6 autoconfiguration
rpm-build 133ac4
	IPV6_AUTOCONF=yes|no: Controls IPv6 autoconfiguration
rpm-build 133ac4
	 Defaults:
rpm-build 133ac4
	  Global IPV6FORWARDING=yes: IPV6_AUTOCONF=no, IPV6_ROUTER=yes
rpm-build 133ac4
	  Global IPV6FORWARDING=no: IPV6_AUTOCONF=yes
rpm-build 133ac4
rpm-build 133ac4
  Optional settings for a 6to4 tunnel
rpm-build 133ac4
    IPV6TO4INIT=yes|no
rpm-build 133ac4
      Enable or disable 6to4 tunneling setup
rpm-build 133ac4
      Default: no
rpm-build 133ac4
    IPV6TO4_RELAY=<IPv4 address> (optional)
rpm-build 133ac4
      IPv4 address of the remote 6to4 relay
rpm-build 133ac4
      Note: if this is omitted, ::192.88.99.1 (the anycast relay address) is chosen
rpm-build 133ac4
    IPV6TO4_IPV4ADDR=<IPv6 address>[/<prefix length>] (optional)
rpm-build 133ac4
      Overwrite local IPv4 address which is accessible from the Internet
rpm-build 133ac4
       (optional, in case of static IPv4-NAT behind a router or other special scenarios)
rpm-build 133ac4
    IPV6TO4_MTU=<MTU for IPv6> (optional)
rpm-build 133ac4
      Controls IPv6 MTU for the 6to4 tunnel
rpm-build 133ac4
      Note: Must be greater or equal to 1280
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6TO4_MTU="1280"
rpm-build 133ac4
      Default: MTU of master device - 20
rpm-build 133ac4
    IPV6TO4_ROUTING="<device>-<suffix>/<prefix length> ..." (optional)
rpm-build 133ac4
      A list of routing tokens to setup proper IPv6 interfaces on the LAN
rpm-build 133ac4
      Example:
rpm-build 133ac4
         IPV6TO4_ROUTING="eth0-:0004::1/64 eth1-:0005::1/64"
rpm-build 133ac4
         Will create one address per eth0 and eth1, taking given SLA
rpm-build 133ac4
rpm-build 133ac4
  Optional settings for a 6to4 tunnel or a ppp link
rpm-build 133ac4
    IPV6_CONTROL_RADVD=yes|no (optional)
rpm-build 133ac4
      Enable signaling radvd that the 6to4 prefix has been changed or a
rpm-build 133ac4
       preconfigured dynamic device is up or down
rpm-build 133ac4
      Default: no
rpm-build 133ac4
rpm-build 133ac4
  IPv6-only items for static tunnel interface:
rpm-build 133ac4
    Interface name: sitX (X => 1)
rpm-build 133ac4
    IPV6INIT=yes|no
rpm-build 133ac4
      Enable or disable IPv6 configuration for this interface
rpm-build 133ac4
      Default: no
rpm-build 133ac4
    IPV6TUNNELIPV4=<IPv4 address>
rpm-build 133ac4
      Specify IPv4 address of a foreign IPv6-in-IPv4 tunnel endpoint
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6TUNNELIPV4="1.2.3.4"
rpm-build 133ac4
    IPV6TUNNELIPV4LOCAL=<IPv4 address>
rpm-build 133ac4
      Specify local IPv4 address of tunnel, useful on interfaces with multiple IPv4 addresses
rpm-build 133ac4
    IPV6ADDR=<IPv6 address>[/<prefix length>] (optional)
rpm-build 133ac4
     local IPv6 address of a numbered tunnel
rpm-build 133ac4
    IPV6ADDR_SECONDARIES="<IPv6 address>[/<prefix length>] ..." (optional)
rpm-build 133ac4
      A list of secondary IPv6 addresses (example see above)
rpm-build 133ac4
    IPV6_MTU=<MTU of tunnel> (optional)
rpm-build 133ac4
      Optional, dedicated MTU of this tunnel
rpm-build 133ac4
      Note: Must be greater or equal to 1280
rpm-build 133ac4
      Example:
rpm-build 133ac4
        IPV6_MTU="1280"
rpm-build 133ac4
rpm-build 133ac4
   IPv6-only option to enable DHCPv6 client:
rpm-build 133ac4
      DHCPV6C=yes|no
rpm-build 133ac4
      This will enable the DHCPv6 features of dhclient to be run for the interface.
rpm-build 133ac4
      See man dhclient(8) and dhclient.conf(5).
rpm-build 133ac4
      DHCPV6C_OPTIONS=...
rpm-build 133ac4
      This will pass given arguments to the DHCPv6 client.  For example,
rpm-build 133ac4
      "-S" option will request network information (e.g., DNS addresses)
rpm-build 133ac4
      only, not IPv6 addresses.
rpm-build 133ac4
rpm-build 133ac4
  Ethernet-only items:
rpm-build 133ac4
    ARP=yes|no (adds 'arp' flag to ip, for use with the
rpm-build 133ac4
      ethertap device)
rpm-build 133ac4
    LINKDELAY=<time in seconds>
rpm-build 133ac4
      Time that the system should pause after the specific interface is
rpm-build 133ac4
      enabled.  This may be useful if one interface is connected to a
rpm-build 133ac4
      switch which has spanning tree enabled and must wait for STP to
rpm-build 133ac4
      converge before the interface should be considered usable.
rpm-build 133ac4
    BRIDGE=<br* device>
rpm-build 133ac4
      If set, the ethernet device is not assigned an address.  It is added to
rpm-build 133ac4
      the specified bridge device instead.
rpm-build 133ac4
    EXTRA_ROUTE_OPTS=<string of route options>
rpm-build 133ac4
      Extra options to add to the interface route. For example, let's say you
rpm-build 133ac4
      wanted an interface route to have an mtu of 1480, but wanted the
rpm-build 133ac4
      interface to still have a route of 1500, you could set "mtu 1480" here.
rpm-build 133ac4
      Anything here is appended to the `ip route add` or `ip route replace`
rpm-build 133ac4
      command.
rpm-build 133ac4
rpm-build 133ac4
   Deprecated, but supported:
rpm-build 133ac4
    ETHTOOL_OPTS=...
rpm-build 133ac4
      Any device-specific options supported by ethtool. For example,
rpm-build 133ac4
      if you wanted to force 100Mb full duplex:
rpm-build 133ac4
        ETHTOOL_OPTS="speed 100 duplex full autoneg off"
rpm-build 133ac4
      Note that changing speed or duplex settings almost always
rpm-build 133ac4
      requires disabling autonegotiation with 'autoneg off'.
rpm-build 133ac4
rpm-build 133ac4
      Multiple options can also be set like so :
rpm-build 133ac4
      ETHTOOL_OPTS="-K ${DEVICE} tso on; -G ${DEVICE} rx 256 tx 256"
rpm-build 133ac4
rpm-build 133ac4
      Long term, this should be done by sysadmin-written udev rules.
rpm-build 133ac4
rpm-build 133ac4
    No longer supported:
rpm-build 133ac4
     PROMISC=yes|no (enable or disable promiscuous mode)
rpm-build 133ac4
     ALLMULTI=yes|no (enable or disable all-multicast mode)
rpm-build 133ac4
     
rpm-build 133ac4
     To properly set these, use the packet socket interface.
rpm-build 133ac4
rpm-build 133ac4
  Ethernet 802.1q VLAN items:
rpm-build 133ac4
     DEVICE=eth0.42
rpm-build 133ac4
       Initscripts use the device name for VLAN devices.
rpm-build 133ac4
               Example: eth0.42 for vlan 42 on device eth0.
rpm-build 133ac4
       Valid VLAN ID range is 0-4095. Most ethernet switches reserve
rpm-build 133ac4
       VLAN ID 1 to be used as management VLAN; starting from VLAN
rpm-build 133ac4
       ID 2 is recommended.
rpm-build 133ac4
     REORDER_HDR=yes|no
rpm-build 133ac4
       When enabled the VLAN device will move the ethernet header
rpm-build 133ac4
       around to make it look exactly like a real ethernet device.
rpm-build 133ac4
       This may help programs such as ISC dhcpd which read the raw
rpm-build 133ac4
       ethernet packet and make assumptions about the location of
rpm-build 133ac4
       bytes. If you don't need it turn it off because there
rpm-build 133ac4
       is a small performance penalty. Default is on.
rpm-build 133ac4
     GVRP=yes|no
rpm-build 133ac4
       When enabled, this will announce new vlan creation to a GVRP
rpm-build 133ac4
       enabled trunk port on a switch. Default is off.
rpm-build 133ac4
rpm-build 133ac4
  PPP/SLIP items:
rpm-build 133ac4
    PERSIST=yes|no
rpm-build 133ac4
    MODEMPORT=<device, say /dev/modem>
rpm-build 133ac4
    LINESPEED=<speed, say 115200>
rpm-build 133ac4
    DEFABORT=yes|no (tells netcfg whether or not to put default
rpm-build 133ac4
      abort strings in when creating/editing the chat script and/or
rpm-build 133ac4
      dip script for this interface)
rpm-build 133ac4
      (meaningless with WVDIALSECT)
rpm-build 133ac4
 
rpm-build 133ac4
  PPP-specific items
rpm-build 133ac4
    WVDIALSECT=<list of sections from wvdial.conf to use>
rpm-build 133ac4
      If this variable is set, then the chat script (if it
rpm-build 133ac4
      exists) is ignored, and wvdial is used to open the
rpm-build 133ac4
      PPP connection.
rpm-build 133ac4
    DEFROUTE=yes|no (set this interface as default route? yes is default)
rpm-build 133ac4
    DEBUG=yes|no (defaults to yes)
rpm-build 133ac4
      turns on/off pppd and chat (if used) debugging.
rpm-build 133ac4
    ESCAPECHARS=yes|no (simplified interface here doesn't let people
rpm-build 133ac4
      specify which characters to escape; almost everyone can use
rpm-build 133ac4
      asyncmap 00000000 anyway, and they can set PPPOPTIONS to
rpm-build 133ac4
      asyncmap foobar if they want to set options perfectly)
rpm-build 133ac4
    HARDFLOWCTL=yes|no (yes implies "modem crtscts" options)
rpm-build 133ac4
    PPPOPTIONS=
rpm-build 133ac4
      command line, so it can override other options like asyncmap
rpm-build 133ac4
      that were specified differently>
rpm-build 133ac4
    PPPOE_EXTRA = any extra arguments to pass to pppoe 
rpm-build 133ac4
    PPPD_EXTRA =  any extra arguments to pass to pppd 
rpm-build 133ac4
    PAPNAME=<"name $PAPNAME" on pppd command line> (note that
rpm-build 133ac4
      the "remotename" option is always specified as the logical
rpm-build 133ac4
      ppp device name, like "ppp0" (which might perhaps be the
rpm-build 133ac4
      physical device ppp1 if some other ppp device was brought
rpm-build 133ac4
      up earlier...), which makes it easy to manage pap/chap
rpm-build 133ac4
      files -- name/password pairs are associated with the
rpm-build 133ac4
      logical ppp device name so that they can be managed
rpm-build 133ac4
      together.
rpm-build 133ac4
    REMIP=<remote ip address, normally unspecified>
rpm-build 133ac4
    MTU=
rpm-build 133ac4
    MRU=
rpm-build 133ac4
    DISCONNECTTIMEOUT=<number of seconds, default currently 5>
rpm-build 133ac4
      (time to wait before re-establishing the connection after
rpm-build 133ac4
      a successfully-connected session terminates before attempting
rpm-build 133ac4
      to establish a new connection.)
rpm-build 133ac4
    RETRYTIMEOUT=<number of seconds, default currently 60>
rpm-build 133ac4
      (time to wait before re-attempting to establish a connection
rpm-build 133ac4
      after a previous attempt fails.)
rpm-build 133ac4
    RETRYCONNECT=yes|no (defaults to yes)
rpm-build 133ac4
      If this is yes, then we will re-run pppd if it exits with a 
rpm-build 133ac4
      "connect script failed" status.  Otherwise, only one attempt
rpm-build 133ac4
      is made to bring up the connection.  Note that some connect
rpm-build 133ac4
      scripts (for example, wvdial) might do their own retries (such
rpm-build 133ac4
      as BUSY or NO DIALTONE conditions).
rpm-build 133ac4
    MAXFAIL=<number>
rpm-build 133ac4
      If this is set, this will cause ppp-watch to exit after
rpm-build 133ac4
      the specified number of attempts.
rpm-build 133ac4
    DEMAND=yes|no
rpm-build 133ac4
      Switches on demand-dialing mode using pppd's "demand" option.
rpm-build 133ac4
    IDLETIMEOUT=600
rpm-build 133ac4
      The amount of time the link needs to be inactive before pppd will
rpm-build 133ac4
      bring it down automatically.
rpm-build 133ac4
    BOOTTIMEOUT=30
rpm-build 133ac4
      The amount of time to wait at boot before giving up on the
rpm-build 133ac4
      connection.
rpm-build 133ac4
rpm-build 133ac4
  IPPP-specific items (ISDN)
rpm-build 133ac4
    PROVIDER=<ProviderName>
rpm-build 133ac4
	 USER=<Login>
rpm-build 133ac4
    PASSWORD=<Password>
rpm-build 133ac4
	 ENCAP=[syncppp|]
rpm-build 133ac4
    DIALMODE=[manual|auto]
rpm-build 133ac4
    SECURE=off|on
rpm-build 133ac4
	 MSN=<>
rpm-build 133ac4
	 PHONE_IN=<Callback.Number>
rpm-build 133ac4
	 	 AREACODE=<>
rpm-build 133ac4
	 REGIONCODE=<>
rpm-build 133ac4
	 PHONE_OUT=<PhoneNumber>
rpm-build 133ac4
    BUNDLING=off|on
rpm-build 133ac4
    HUPTIMEOUT=<number>
rpm-build 133ac4
    DNS1=<PrimaryDNS>
rpm-build 133ac4
    DNS2=<SecondaryDNS>
rpm-build 133ac4
    DOMAIN=""
rpm-build 133ac4
    LAYER=[HDLC|]
rpm-build 133ac4
    CALLBACK=off|on
rpm-build 133ac4
    CHARGEHUP=<number>
rpm-build 133ac4
    CHARGEINT=<number>
rpm-build 133ac4
    CBHUP=<number>
rpm-build 133ac4
    CBDELAY=<number>
rpm-build 133ac4
    DIALMAX=<number>
rpm-build 133ac4
    AUTH=[+pap] [-chap]
rpm-build 133ac4
    IHUP=<>
rpm-build 133ac4
    DELDEFAULTROUTE=[enabled|disabled]
rpm-build 133ac4
    CBCP=off|on
rpm-build 133ac4
    VJ=off|on
rpm-build 133ac4
    VJCCOMP=off|on
rpm-build 133ac4
    AC=off|on
rpm-build 133ac4
    PC=off|on
rpm-build 133ac4
    BSDCOMP=off|on
rpm-build 133ac4
    CCP=off|on
rpm-build 133ac4
    SLAVE_DEVICE=ippp[0-9]
rpm-build 133ac4
rpm-build 133ac4
  ippp0 items being deprecated:
rpm-build 133ac4
    BOOT=[on|off] will be converted to ONBOOT=[yes|no] by netconf
rpm-build 133ac4
    LOCAL_IP=     will be converted to IPADDR by netconf
rpm-build 133ac4
    REMOTE_IP=    will be converted to GATEWAY by netconf
rpm-build 133ac4
rpm-build 133ac4
  Wireless-specific items:
rpm-build 133ac4
    See iw(8) for additional information.
rpm-build 133ac4
    MODE=[Managed|Ad-Hoc|Monitor]
rpm-build 133ac4
    ESSID=
rpm-build 133ac4
      Required.
rpm-build 133ac4
    FREQ=
rpm-build 133ac4
      Required if MODE=Ad-Hoc.
rpm-build 133ac4
    KEY=<default WEP key>
rpm-build 133ac4
rpm-build 133ac4
  IPSEC specific items
rpm-build 133ac4
     SRC=source address. Not required.
rpm-build 133ac4
     DST=destination address
rpm-build 133ac4
     TYPE=IPSEC
rpm-build 133ac4
     SRCNET=source net (for tunneling)
rpm-build 133ac4
     DSTNET=destination network (for tunneling)
rpm-build 133ac4
rpm-build 133ac4
   Manual keying:
rpm-build 133ac4
rpm-build 133ac4
     AH_PROTO{,_IN,_OUT}=protocol to use for AH (defaults to hmac-sha1)
rpm-build 133ac4
     ESP_PROTO{,_IN,_OUT}=protocol to use for ESP (defaults to 3des-cbc)
rpm-build 133ac4
     AESP_PROTO{,_IN,_OUT}=protocol to use for ESP authentication (defaults to
rpm-build 133ac4
	hmac-sha1)
rpm-build 133ac4
     KEY_AH{,_IN,_OUT}=AH key
rpm-build 133ac4
     KEY_ESP{,_IN,_OUT}=ESP encryption key
rpm-build 133ac4
     KEY_AESP{,_IN,_OUT}=ESP authentication key (optional)
rpm-build 133ac4
     SPI_{ESP,AH}_{IN,OUT}=SPIs to use
rpm-build 133ac4
rpm-build 133ac4
   _IN and _OUT specifiers are for using different keys or protocols for
rpm-build 133ac4
   incoming and outgoing packets.  If neither _IN or _OUT variants are set for
rpm-build 133ac4
   protocols or keys, the same will be used for both.  Hexadecimal keys need to
rpm-build 133ac4
   be prefixed with "0x".
rpm-build 133ac4
rpm-build 133ac4
   Automatic keying:
rpm-build 133ac4
rpm-build 133ac4
     IKE_DHGROUP=<number> (defaults to 2)
rpm-build 133ac4
     IKE_METHOD=PSK|X509|GSSAPI
rpm-build 133ac4
         PSK=preshared keys (shared secret)
rpm-build 133ac4
         X509=X.509 certificates
rpm-build 133ac4
         GSSPI=GSSAPI authentication
rpm-build 133ac4
     IKE_AUTH=protocol to use for Phase 1 of SA (defaults to sha1)
rpm-build 133ac4
     IKE_ENC=protocol to use for Phase 1 of SA (defaults to 3des)
rpm-build 133ac4
     IKE_PSK=preshared key for this connection
rpm-build 133ac4
     IKE_CERTFILE=our certificate file name for X509 IKE
rpm-build 133ac4
       IKE_PEER_CERTFILE=peer public cert filename for X509 IKE
rpm-build 133ac4
       IKE_DNSSEC=retrieve peer public certs from DNS
rpm-build 133ac4
     (otherwise uses certificate information sent over IKE)
rpm-build 133ac4
rpm-build 133ac4
     To manage the racoon configuration manually (e.g. when there is more than
rpm-build 133ac4
     one IPSEC configuration with the same DST), set KEYING=automatic and leave
rpm-build 133ac4
     all IKE_* parameters unspecified.
rpm-build 133ac4
rpm-build 133ac4
     To override the identifier to use with a preshared key:
rpm-build 133ac4
rpm-build 133ac4
       MYID_TYPE=address|fqdn|user_fqdn
rpm-build 133ac4
       MYID_VALUE=fqdn or user_fqdn string for this connection
rpm-build 133ac4
rpm-build 133ac4
   Usage of AH or ESP may be disabled by setting {AH,ESP}_PROTO to "none".
rpm-build 133ac4
rpm-build 133ac4
  Bonding-specific items
rpm-build 133ac4
rpm-build 133ac4
    SLAVE=yes
rpm-build 133ac4
      Specifies device as a slave
rpm-build 133ac4
    MASTER=bondXX
rpm-build 133ac4
      Specifies master device to bind to
rpm-build 133ac4
    BONDING_OPTS=
rpm-build 133ac4
      A space-separated list of options to the bonding driver for this
rpm-build 133ac4
      interface, such as:
rpm-build 133ac4
rpm-build 133ac4
      "mode=active-backup arp_interval=60 arp_ip_target=192.168.1.1,192.168.1.2"
rpm-build 133ac4
rpm-build 133ac4
  Tunnel-specific items:
rpm-build 133ac4
    TYPE=GRE|GRE6|IPIP|IPIP6|EXTERNAL
rpm-build 133ac4
      External is a mode for ip6_tunnel interfaces (that cannot be set on
rpm-build 133ac4
      the primary ip6tnl0 interface), which permits unwrapping encapsulated
rpm-build 133ac4
      packets regardless of their internal IP (v4 or v6) provided the inner
rpm-build 133ac4
      address is on the interface. Use $MY_INNER_IPADDR for v4 addresses. Use
rpm-build 133ac4
      $IPV6ADDR and $IPV6ADDR_SECONDARIES as usual for v6 addresses.
rpm-build 133ac4
    MY_INNER_IPADDR=local IP address of the tunnel interface
rpm-build 133ac4
    PEER_OUTER_IPADDR=IP address of the remote tunnel endpoint
rpm-build 133ac4
    MY_OUTER_IPADDR=IP address of the local tunnel endpoint
rpm-build 133ac4
      If unspecified, an IP address is selected automatically for outgoing
rpm-build 133ac4
      tunnel packets, and incoming tunnel packets are accepted on all local
rpm-build 133ac4
      IP addresses.
rpm-build 133ac4
    PEER_INNER_IPADDR=IP address of the remote end of the tunnel interface
rpm-build 133ac4
      If this is specified, a route to PEER_INNER_IPADDR through the tunnel
rpm-build 133ac4
      is added automatically.
rpm-build 133ac4
    TTL=TTL value for tunnel packets
rpm-build 133ac4
      Default is to use the TTL of the packet transported through the tunnel
rpm-build 133ac4
rpm-build 133ac4
  Bridge-specific items:
rpm-build 133ac4
    TYPE=Bridge
rpm-build 133ac4
    STP=off|on (see 'brctl stp')
rpm-build 133ac4
    DELAY=forward delay time in seconds (see 'brctl setfd')
rpm-build 133ac4
    BRIDGING_OPTS=
rpm-build 133ac4
      A space-separated list of bridging options for either the bridge
rpm-build 133ac4
      device, or the port device, such as:
rpm-build 133ac4
rpm-build 133ac4
      BRIDGING_OPTS="hello_time=200 priority=65535"
rpm-build 133ac4
        for bridge devices, or
rpm-build 133ac4
      BRIDGING_OPTS="hairpin_mode=1"
rpm-build 133ac4
        for port devices.
rpm-build 133ac4
rpm-build 133ac4
  TUN/TAP-specific items:
rpm-build 133ac4
    OWNER=<owner of the device>
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/chat-<interface-name>:
rpm-build 133ac4
rpm-build 133ac4
  chat script for PPP or SLIP connection intended to establish
rpm-build 133ac4
  the connection.  For SLIP devices, a DIP script is written
rpm-build 133ac4
  from the chat script; for PPP devices, the chat script is used
rpm-build 133ac4
  directly.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/dip-<interface-name>
rpm-build 133ac4
rpm-build 133ac4
  A write-only script created from the chat script by netcfg.
rpm-build 133ac4
  Do not modify this.  In the future, this file may disappear
rpm-build 133ac4
  by default and created on-the-fly from the chat script if
rpm-build 133ac4
  it does not exist.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifup-post
rpm-build 133ac4
rpm-build 133ac4
  Called when any network device EXCEPT a SLIP device comes
rpm-build 133ac4
  up.  Calls /etc/sysconfig/network-scripts/ifup-routes to
rpm-build 133ac4
  bring up static routes that depend on that device.  Calls
rpm-build 133ac4
  /etc/sysconfig/network-scripts/ifup-aliases to bring up
rpm-build 133ac4
  aliases for that device.  Sets the hostname if it is not
rpm-build 133ac4
  already set and a hostname can be found for the IP for that
rpm-build 133ac4
  device.  Sends SIGIO to any programs that have requested
rpm-build 133ac4
  notification of network events.
rpm-build 133ac4
rpm-build 133ac4
  Could be extended to fix up nameservice configuration, call
rpm-build 133ac4
  arbitrary scripts, etc, as needed.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifup-routes
rpm-build 133ac4
rpm-build 133ac4
  Set up static routes for a device.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/ifup-aliases
rpm-build 133ac4
rpm-build 133ac4
  Bring up aliases for a device.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/route-<interface-name>
rpm-build 133ac4
rpm-build 133ac4
  Contains lines that specify additional routes that should be added when the
rpm-build 133ac4
  associated interface is brought up.
rpm-build 133ac4
rpm-build 133ac4
  The files are processed by the ifup-routes script and uses the /sbin/ipcalc
rpm-build 133ac4
  utility for all network masks and numbers. Routes are specified using the
rpm-build 133ac4
  syntax:
rpm-build 133ac4
rpm-build 133ac4
    ADDRESSn=<network>
rpm-build 133ac4
    NETMASKn=<network/prefix mask>
rpm-build 133ac4
    GATEWAYn=<next-hop router/gateway IP address>
rpm-build 133ac4
rpm-build 133ac4
  The "n" is expected to be consecutive positive integers starting from 0.
rpm-build 133ac4
  For example:
rpm-build 133ac4
rpm-build 133ac4
    ADDRESS0=192.168.2.0
rpm-build 133ac4
    NETMASK0=255.255.255.0
rpm-build 133ac4
    GATEWAY0=192.168.1.1
rpm-build 133ac4
rpm-build 133ac4
  adds a network route to the 192.168.2.0 network via the gateway at
rpm-build 133ac4
  192.168.1.1. Since you must already have a route to the network of the
rpm-build 133ac4
  gateway, there is no need to specify a device.
rpm-build 133ac4
rpm-build 133ac4
  Note: The ifup-routes script also supports an older syntax designed to be
rpm-build 133ac4
  used directly as an argument to "/sbin/ip route add".
rpm-build 133ac4
  If no "ADDRESSn" lines are found the following will still
rpm-build 133ac4
  work:
rpm-build 133ac4
  
rpm-build 133ac4
  192.168.2.0/24 dev ppp0
rpm-build 133ac4
  
rpm-build 133ac4
  adds a network route to the 192.168.2.0 network through ppp0.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/route6-<interface-name>
rpm-build 133ac4
rpm-build 133ac4
  Contains lines that are arguments to "/sbin/ip -6 route add"
rpm-build 133ac4
  For example:
rpm-build 133ac4
rpm-build 133ac4
  site-local route for network fec0:0:0:2::/64
rpm-build 133ac4
   via gateway fec0:0:0:1:0:0:0:20 (e.g. on eth0): 
rpm-build 133ac4
rpm-build 133ac4
  fec0:0:0:2::/64 via fec0:0:0:1:0:0:0:20
rpm-build 133ac4
rpm-build 133ac4
  additional prefix configured to be on-link on eth0:
rpm-build 133ac4
rpm-build 133ac4
  3ffe:fffe:1:2::/64 dev eth0
rpm-build 133ac4
  
rpm-build 133ac4
  6to4 route for network 3ffe:ffff:1::/48, either:
rpm-build 133ac4
rpm-build 133ac4
  3ffe:ffff:1::/48
rpm-build 133ac4
  3ffe:ffff:1::/48 via ::192.168.1.2
rpm-build 133ac4
rpm-build 133ac4
  Note the special case of 6to4 interface: 'via [relay]' is 
rpm-build 133ac4
  automatically added if explicit 'via' wasn't specified.
rpm-build 133ac4
rpm-build 133ac4
/etc/sysconfig/network-scripts/rule-<interface-name>
rpm-build 133ac4
/etc/sysconfig/network-scripts/rule6-<interface-name>
rpm-build 133ac4
rpm-build 133ac4
  Contains lines that specify additional routing rules that should be added
rpm-build 133ac4
  when the associated interface is brought up.
rpm-build 133ac4
rpm-build 133ac4
  Each non-comment line is used directly as an argument to "/sbin/ip rule add"
rpm-build 133ac4
  or "/sbin/ip -6 rule add" for rule6 files.
rpm-build 133ac4