IFSERVICES(5) Network configuration IFSERVICES(5)NAME
ifservices-* - control network services with ifup/down
SYNOPSIS
/etc/sysconfig/network/ifservices-<configuration_name>/
DESCRIPTION
The directory /etc/sysconfig/network/ifservices-<configuration_name>/ is read by the script /etc/sysconfig/network/scripts/ifup-services
which starts and stops system services when an interface is set up/down. ifup-services is used by /sbin/ifup, which is the command line
user interface for setting up network interfaces.
This is useful if you don't have a permanent network connection. If you sometimes boot without network and plug in the network cable later
you can add links to system services in this directory. These services will then be started with ifup and stopped with ifdown.
The configuration name used for ifservices-* should match exactly the configuration name of the ifcfg-* file for the interface.
For the usage with NetworkManager (where you don't necessarily need a ifcfg-* file) you can also use /etc/sysconfig/network/ifser-
vices-<interface>-<essid>/ (for wlan interfaces) or if that does not exist /etc/sysconfig/network/ifservices-<interface>/. As a final
fallback /etc/sysconfig/network/ifservices/ is checked as well. If NetworkManager is active services will be stopped after the interface is
down.
The links in this directory are equal to the links in the runlevel directories /etc/init.d/rc*.d/ They have to point to service start
scripts which are usually in /etc/init.d/. Links starting with 'S' are start links, which are called in alphabetical order after ifup has
set up the interface. Links starting with 'K' are kill links which are called before ifdown takes down the interface. See also section
Sequencing Directories in boot (7).
EXAMPLE
In this example we use an interface with MAC address 00:de:ad:be:af:00. This interface is not always physically connected. As soon as you
plug in the cable ypbind and autofs should be started. When you pull the cable they should be stopped. This can be reached with:
in file /etc/sysconfig/network/ifcfg-eth-id-00:de:ad:be:af:00
...
STARTMODE=ifplugd
...
in dir /etc/sysconfig/network/ifservices-eth-id-00:de:ad:be:af:00/
S10portmap -> /etc/init.d/portmap
S20ypbind -> /etc/init.d/ypbind
S30autofs -> /etc/init.d/autofs
S20autofs -> /etc/init.d/autofs
K30ypbind -> /etc/init.d/ypbind
Now you have to disable the start of this services at boot time
chkconfig ypbind off
chkconfig autofs off
Notes:
You may call scripts/create-ifservices-directory [<interface_name>] to create a directory with the links from this example. This will cre-
ate the directory ifservices-<interface_name> or if no interface name was given ifservices-template.
Maybe you have to add also variable IFPLUGD_PRIORITY. For details about startmode ifplugd read ifup (8).
The service portmap had to be added because ypbind needs it. This service is still started at boot time because it does not need an active
network connection. But ypbind may now be started earlier as usual. Therefore we make sure that portmap is started before. Starting an
already running service again does not affect the service.
SEE ALSO ifup(8), ifcfg(5).
AUTHOR
Christian Zoz <zoz@suse.de>
sysconfig February 2005 IFSERVICES(5)
Check Out this Related Man Page
IFSYSCTL(5) Network configuration IFSYSCTL(5)NAME
ifsysctl[-<interface name>] - per network interface sysctl settings
SYNOPSIS
/etc/sysconfig/network/ifsysctl
/etc/sysconfig/network/ifsysctl-<interface name>
DESCRIPTION
These files are intended to contain sysctl settings, that should be applied when a network interface is created. This are usually interface
specific settings, like:
net.ipv6.conf.eth0.use_tempaddr = 1
or
net.ipv4.conf.eth0.rp_filter = 0
The settings are applied by the /etc/sysconfig/network/scripts/ifup-sysctl script executed via /etc/udev/rules.d/77-network.rules rule (see
udev(7)), after the creation and after the rename of the interface name to its persistent name (when applicable), but before the ifup
<interface name> -o hotplug may be executed to configure the interface.
The settings are not applied by default when the NetworkManager is active (NETWORKMANAGER=yes), except when the IFSYSCTL_NETWORKMANAGER=yes
variable is set in the /etc/sysconfig/network/config file.
Settings from the ifsysctl- file are applied every time an interface has been created.
Settings from the ifsysctl-interface name file are applied when the interface with the corresponding interface name has been created.
SYNTAX
The sysctl(8) utility is required to apply the settings. It supports two separator characters for sysctl keywords: a "." in default format
and a "/" in the alternate format. Therefore the syntax is basically same to the /etc/sysctl.conf file.
Interface names may contain a ".". In the default sysctl format using a "." as separator, that is any "." in the interface name of the key-
word, has to be replaced with a "/". In the alternate sysctl format with "/" as separator, normal interface names can be used.
Optionally, the ifsysctl files may contain also the $INTERFACE and the $SYSCTL_IF variables, that are automatically replaced with the cur-
rent interface name usable in the alternate format and with the sysctl-quoted interface name for the default format, before the settings
are passed to the sysctl utility.
Note also, that settings with variables in the ifsysctl (without the -<interface name> suffix), will be applied for every interface!
Further, files with variables are not compatible to the /etc/sysctl.conf file.
EXAMPLES
Settings for "eth0" and "eth0.1" interfaces
# using "." as separator:
net.ipv6.conf.eth0.use_tempaddr = 1
net.ipv6.conf.eth0/1.use_tempaddr = 1
# using "/" as separator:
net/ipv6/conf/eth0/use_tempaddr = 1
net/ipv6/conf/eth0.0/use_tempaddr = 1
Settings with variables:
# using "." as separator:
net.ipv6.conf.$SYSCTL_IF.use_tempaddr = 1
# using "/" as separator:
net/ipv6/conf/$INTERFACE/use_tempaddr = 1
To test your ifsysctl-eth0 or ifsysctl file, use:
/etc/sysconfig/network/scripts/ifup-sysctl eth0 -o debug
BUGS
Please report bugs at <https://bugzilla.novell.com/>
AUTHOR
Marius Tomaschewski <mt@suse.de>
SEE ALSO ifup(8)ifcfg(5)sysctl(8)sysconfig December 2009 IFSYSCTL(5)