summaryrefslogtreecommitdiff
path: root/man/NetworkManager.conf.xml
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2019-02-08 16:05:36 +0100
committerThomas Haller <thaller@redhat.com>2019-02-08 16:05:36 +0100
commit4023012cd1c8626d26d2649b53a558c48b5ffff9 (patch)
treef94a83f971c6febb9414f65e94392124089a75c2 /man/NetworkManager.conf.xml
parentbba33ba20c6d3bdbbafe6184903e0437f11c9c28 (diff)
downloadNetworkManager-4023012cd1c8626d26d2649b53a558c48b5ffff9.tar.gz
man: add a warning to NetworkManager.conf manual for rp_filter and connectivity checking
Diffstat (limited to 'man/NetworkManager.conf.xml')
-rw-r--r--man/NetworkManager.conf.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml
index 4d6fe12df7..b6577aed50 100644
--- a/man/NetworkManager.conf.xml
+++ b/man/NetworkManager.conf.xml
@@ -1056,10 +1056,12 @@ managed=1
<refsect1>
<title><literal>connectivity</literal> section</title>
+
<para>This section controls NetworkManager's optional connectivity
checking functionality. This allows NetworkManager to detect
whether or not the system can actually access the internet or
whether it is behind a captive portal.</para>
+
<para>Connectivity checking serves two purposes. For one, it exposes
a connectivity state on D-Bus, which other applications may use. For example,
Gnome's portal helper uses this as signal to show a captive portal login
@@ -1070,6 +1072,12 @@ managed=1
when being connected to WWAN and to a Wi-Fi network which is behind a captive
portal, WWAN still gets preferred until login.</para>
+ <para>Note that your distribution might set <literal>/proc/sys/net/ipv4/conf/*/rp_filter</literal> to
+ strict filtering. That works badly with per-device connectivity checking,
+ which uses SO_BINDDEVICE to send requests on all devices. A strict rp_filter
+ setting will reject any response and the connectivity check on all but the
+ best route will fail.</para>
+
<para>
<variablelist>
<varlistentry>