sysctl.d: switch net.ipv4.conf.all.rp_filter from 1 to 2

This switches the RFC3704 Reverse Path filtering from Strict mode to Loose
mode. The Strict mode breaks some pretty common and reasonable use cases,
such as keeping connections via one default route alive after another one
appears (e.g. plugging an Ethernet cable when connected via Wi-Fi).

The strict filter also makes it impossible for NetworkManager to do
connectivity check on a newly arriving default route (it starts with a
higher metric and is bumped lower if there's connectivity).

Kernel's default is 0 (no filter), but a Loose filter is good enough. The
few use cases where a Strict mode could make sense can easily override
this.

The distributions that don't care about the client use cases and prefer a
strict filter could just ship a custom configuration in
/usr/lib/sysctl.d/ to override this.

Cherry-picked from: 230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e
Resolves: #1653824
1 file changed
tree: 12675ac63baf2e758a3bc1c7df9b71bc12d953de
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .mailmap
  7. .mkosi/
  8. .travis.yml
  9. .vimrc
  10. .ycm_extra_conf.py
  11. LICENSE.GPL2
  12. LICENSE.LGPL2.1
  13. Makefile
  14. NEWS
  15. README
  16. README.md
  17. TODO
  18. catalog/
  19. coccinelle/
  20. configure
  21. doc/
  22. factory/etc/
  23. hwdb/
  24. man/
  25. meson.build
  26. meson_options.txt
  27. mkosi.build
  28. modprobe.d/
  29. network/
  30. po/
  31. presets/
  32. rules/
  33. shell-completion/
  34. src/
  35. sysctl.d/
  36. sysusers.d/
  37. test/
  38. tmpfiles.d/
  39. tools/
  40. travis-ci/
  41. units/
  42. xorg/
  43. zanata.xml
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status
CII Best Practices
Build Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the HACKING file for information how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.

Stable branches with backported patches are available in the stable repo.