2014-11-21 22:44:48 +03:00
<?xml version="1.0"?> <!-- * - nxml - * -->
2015-06-18 20:47:44 +03:00
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2011-04-04 05:48:09 +04:00
<!--
2017-11-18 19:22:32 +03:00
SPDX-License-Identifier: LGPL-2.1+
2011-04-04 05:48:09 +04:00
This file is part of systemd.
Copyright 2011 Lennart Poettering
-->
2014-11-29 12:05:43 +03:00
<refentry id= "sysctl.d"
2015-02-04 05:14:13 +03:00
xmlns:xi="http://www.w3.org/2001/XInclude">
<refentryinfo >
<title > sysctl.d</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > sysctl.d</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > sysctl.d</refname>
<refpurpose > Configure kernel parameters at boot</refpurpose>
</refnamediv>
<refsynopsisdiv >
<para > <filename > /etc/sysctl.d/*.conf</filename> </para>
<para > <filename > /run/sysctl.d/*.conf</filename> </para>
<para > <filename > /usr/lib/sysctl.d/*.conf</filename> </para>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > At boot,
<citerefentry > <refentrytitle > systemd-sysctl.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
reads configuration files from the above directories to configure
2015-03-14 05:22:39 +03:00
<citerefentry project= 'man-pages' > <refentrytitle > sysctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
kernel parameters.</para>
</refsect1>
<refsect1 >
<title > Configuration Format</title>
<para > The configuration files contain a list of variable
assignments, separated by newlines. Empty lines and lines whose
first non-whitespace character is <literal > #</literal> or
<literal > ;</literal> are ignored.</para>
<para > Note that either <literal > /</literal> or
<literal > .</literal> may be used as separators within sysctl
variable names. If the first separator is a slash, remaining
slashes and dots are left intact. If the first separator is a dot,
dots and slashes are interchanged.
<literal > kernel.domainname=foo</literal> and
<literal > kernel/domainname=foo</literal> are equivalent and will
cause <literal > foo</literal> to be written to
<filename > /proc/sys/kernel/domainname</filename> . Either
<literal > net.ipv4.conf.enp3s0/200.forwarding</literal> or
<literal > net/ipv4/conf/enp3s0.200/forwarding</literal> may be used
to refer to
<filename > /proc/sys/net/ipv4/conf/enp3s0.200/forwarding</filename> .
</para>
<para > The settings configured with <filename > sysctl.d</filename>
files will be applied early on boot. The network
interface-specific options will also be applied individually for
each network interface as it shows up in the system. (More
specifically, <filename > net.ipv4.conf.*</filename> ,
<filename > net.ipv6.conf.*</filename> ,
<filename > net.ipv4.neigh.*</filename> and
<filename > net.ipv6.neigh.*</filename> ).</para>
<para > Many sysctl parameters only become available when certain
kernel modules are loaded. Modules are usually loaded on demand,
e.g. when certain hardware is plugged in or network brought up.
This means that
<citerefentry > <refentrytitle > systemd-sysctl.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
which runs during early boot will not configure such parameters if
they become available after it has run. To set such parameters, it
is recommended to add an
<citerefentry > <refentrytitle > udev</refentrytitle> <manvolnum > 7</manvolnum> </citerefentry>
rule to set those parameters when they become available.
Alternatively, a slightly simpler and less efficient option is to
add the module to
<citerefentry > <refentrytitle > modules-load.d</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
causing it to be loaded statically before sysctl settings are
applied (see example below).</para>
</refsect1>
<xi:include href= "standard-conf.xml" xpointer= "confd" />
<refsect1 >
<title > Examples</title>
<example >
<title > Set kernel YP domain name</title>
<para > <filename > /etc/sysctl.d/domain-name.conf</filename> :
</para>
<programlisting > kernel.domainname=example.com</programlisting>
</example>
<example >
2015-06-30 03:34:45 +03:00
<title > Apply settings available only when a certain module is loaded (method one)</title>
2015-02-04 05:14:13 +03:00
<para > <filename > /etc/udev/rules.d/99-bridge.rules</filename> :
</para>
2015-06-30 03:34:45 +03:00
<programlisting > ACTION=="add", SUBSYSTEM=="module", KERNEL=="br_netfilter", \
RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/net/bridge"
2014-06-20 05:13:56 +04:00
</programlisting>
2015-02-04 05:14:13 +03:00
<para > <filename > /etc/sysctl.d/bridge.conf</filename> :
</para>
2014-06-20 05:13:56 +04:00
2015-02-04 05:14:13 +03:00
<programlisting > net.bridge.bridge-nf-call-ip6tables = 0
2014-06-20 05:13:56 +04:00
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
</programlisting>
2015-06-30 03:34:45 +03:00
<para > This method applies settings when the module is
2014-08-03 09:11:12 +04:00
loaded. Please note that, unless the <filename > br_netfilter</filename>
2015-06-30 03:34:45 +03:00
module is loaded, bridged packets will not be filtered by
2014-08-03 09:11:37 +04:00
Netfilter (starting with kernel 3.18), so simply not loading the
module is sufficient to avoid filtering.</para>
2015-02-04 05:14:13 +03:00
</example>
2014-06-20 05:13:56 +04:00
2015-02-04 05:14:13 +03:00
<example >
2015-06-30 03:34:45 +03:00
<title > Apply settings available only when a certain module is loaded (method two)</title>
2015-02-04 05:14:13 +03:00
<para > <filename > /etc/modules-load.d/bridge.conf</filename> :
</para>
2014-06-20 04:43:56 +04:00
2015-06-30 03:34:45 +03:00
<programlisting > br_netfilter</programlisting>
2014-06-20 04:43:56 +04:00
2015-02-04 05:14:13 +03:00
<para > <filename > /etc/sysctl.d/bridge.conf</filename> :
</para>
2011-04-04 05:48:09 +04:00
2015-02-04 05:14:13 +03:00
<programlisting > net.bridge.bridge-nf-call-ip6tables = 0
2014-06-20 04:43:56 +04:00
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
</programlisting>
2015-06-30 03:34:45 +03:00
<para > This method forces the module to be always loaded. Please
2014-08-03 09:11:12 +04:00
note that, unless the <filename > br_netfilter</filename> module is
2014-08-03 09:11:37 +04:00
loaded, bridged packets will not be filtered with Netfilter
2015-06-30 03:34:45 +03:00
(starting with kernel 3.18), so simply not loading the module is
2014-08-03 09:11:37 +04:00
sufficient to avoid filtering.</para>
2015-02-04 05:14:13 +03:00
</example>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-sysctl.service</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-delta</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
2015-03-14 05:22:39 +03:00
<citerefentry project= 'man-pages' > <refentrytitle > sysctl</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > sysctl.conf</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > modprobe</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry>
2015-02-04 05:14:13 +03:00
</para>
</refsect1>
2011-04-04 05:48:09 +04:00
</refentry>