Blame SOURCES/0053-sysctl.d-switch-net.ipv4.conf.all.rp_filter-from-1-t.patch

a3e2b5
From 75c9af80cf3529c76988451e63f98010c86f48f1 Mon Sep 17 00:00:00 2001
a3e2b5
From: Lubomir Rintel <lkundrak@v3.sk>
a3e2b5
Date: Wed, 28 Nov 2018 11:44:20 +0100
a3e2b5
Subject: [PATCH] sysctl.d: switch net.ipv4.conf.all.rp_filter from 1 to 2
a3e2b5
a3e2b5
This switches the RFC3704 Reverse Path filtering from Strict mode to Loose
a3e2b5
mode. The Strict mode breaks some pretty common and reasonable use cases,
a3e2b5
such as keeping connections via one default route alive after another one
a3e2b5
appears (e.g. plugging an Ethernet cable when connected via Wi-Fi).
a3e2b5
a3e2b5
The strict filter also makes it impossible for NetworkManager to do
a3e2b5
connectivity check on a newly arriving default route (it starts with a
a3e2b5
higher metric and is bumped lower if there's connectivity).
a3e2b5
a3e2b5
Kernel's default is 0 (no filter), but a Loose filter is good enough. The
a3e2b5
few use cases where a Strict mode could make sense can easily override
a3e2b5
this.
a3e2b5
a3e2b5
The distributions that don't care about the client use cases and prefer a
a3e2b5
strict filter could just ship a custom configuration in
a3e2b5
/usr/lib/sysctl.d/ to override this.
a3e2b5
a3e2b5
Cherry-picked from: 230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e
a3e2b5
Resolves: #1653824
a3e2b5
---
a3e2b5
 sysctl.d/50-default.conf | 2 +-
a3e2b5
 1 file changed, 1 insertion(+), 1 deletion(-)
a3e2b5
a3e2b5
diff --git a/sysctl.d/50-default.conf b/sysctl.d/50-default.conf
a3e2b5
index e263cf0628..b0645f33e7 100644
a3e2b5
--- a/sysctl.d/50-default.conf
a3e2b5
+++ b/sysctl.d/50-default.conf
a3e2b5
@@ -22,7 +22,7 @@ kernel.sysrq = 16
a3e2b5
 kernel.core_uses_pid = 1
a3e2b5
 
a3e2b5
 # Source route verification
a3e2b5
-net.ipv4.conf.all.rp_filter = 1
a3e2b5
+net.ipv4.conf.all.rp_filter = 2
a3e2b5
 
a3e2b5
 # Do not accept source routing
a3e2b5
 net.ipv4.conf.all.accept_source_route = 0