IFSYSCTL
NAMESYNOPSIS
DESCRIPTION
SYNTAX
EXAMPLES
BUGS
AUTHOR
SEE ALSO
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 = 2 |
or
|
net.ipv4.conf.eth0.rp_filter = 0 |
The settings are applied by the /etc/sysconfig/network/scripts/ifup-sysctl script executed via /lib/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 keyword, 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 current 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 = 2 | |
|
net.ipv6.conf.eth0/1.use_tempaddr = 2 | |
|
# using "/" as separator: | |
|
net/ipv6/conf/eth0/use_tempaddr = 2 | |
|
net/ipv6/conf/eth0.0/use_tempaddr = 2 |
Settings with variables:
|
# using "." as separator: | |
|
net.ipv6.conf.$SYSCTL_IF.use_tempaddr = 2 | |
|
# using "/" as separator: | |
|
net/ipv6/conf/$INTERFACE/use_tempaddr = 2 |
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)
More Linux Commands
manpages/baudrate.3ncurses.html
baudrate(3ncurses) - curses environment query routines......
The baudrate routine returns the output speed of the terminal. The number returned is in bits per second, for example 9600, and is an integer. The erasechar rou
manpages/vdir.1.html
vdir(1) - list directory contents - Linux manual page.......
vdir.1 - List information about the FILEs (the current directory by default). Sort entries alphabetically if none of -cftuvSUX nor --sort is specified. Mandator
manpages/bytes.3pm.html
bytes(3pm) - Perl pragma to force byte semantics rather than
The use bytes pragma disables character semantics for the rest of the lexical scope in which it appears. no bytes can be used to reverse the effect of use bytes
manpages/Tk_HandleEvent.3.html
Tk_HandleEvent(3) - invoke event handlers for window system
Tk_HandleEvent is a lower-level procedure that deals with window events. It is called by Tcl_ServiceEvent (and indirectly by Tcl_DoOneEvent), and in a few other
manpages/auparse_first_record.3.html
auparse_first_record(3) - reposition record cursor (ManPage)
auparse_first_record repositions the internal cursors of the parsing library to point to the first record in the current event. RETURN VALUE Returns -1 if an er
manpages/lndir.1.html
lndir(1) - create a shadow directory of symbolic links to an
The lndir program makes a shadow copy todir of a directory tree fromdir, except that the shadow is not populated with real files but instead with symbolic links
manpages/sivtest.1.html
sivtest(1) - interactive MANAGESIEVE test program (ManPage)
sivtest is a utility that allows you to authenticate to a MANAGESIEVE server and interactively issue commands to it. Once authenticated you may issue any MANAGE
manpages/pselect6.2.html
pselect6(2) - synchronous I/O multiplexing - Linux man page
select() and pselect() allow a program to monitor multiple file descriptors, waiting until one or more of the file descriptors become ready for some class of I/
manpages/XML::DOM::PerlSAX.3pm.html
XML::DOM::PerlSAX(3pm) - Old name of XML::Handler::BuildDOM
XML::DOM::PerlSAX was renamed to XML::Handler::BuildDOM to comply with naming conventions for PerlSAX filters/handlers. For backward compatibility, this package
manpages/XtAppMainLoop.3.html
XtAppMainLoop(3) - query and process events and input.......
If the X event queue is empty, XtAppNextEvent flushes the X output buffers of each Display in the application context and waits for an event while looking at th
manpages/Tcl_SetCommandInfo.3.html
Tcl_SetCommandInfo(3) - implement new commands in C.........
Tcl_CreateObjCommand defines a new command in interp and associates it with procedure proc such that whenever name is invoked as a Tcl command (e.g., via a call
manpages/mono-service.1.html
mono-service(1) - Mono ServiceProcess host - Linux man page
The mono-service is a host to run services built with the ServiceProcess assembly. Use mono-service to run services that use the 1.0 assemblies and use mono-ser
