From b7c0c43fc12571e3e359dd4248b801f7b5cbd630 Mon Sep 17 00:00:00 2001 From: Packit Service Date: Dec 12 2020 01:21:58 +0000 Subject: Add sources defined in the spec file --- diff --git a/SPECS/00-server.conf b/SPECS/00-server.conf new file mode 100644 index 0000000..ba3d29f --- /dev/null +++ b/SPECS/00-server.conf @@ -0,0 +1,14 @@ +# This configuration file changes NetworkManager's behavior to +# what's expected on "traditional UNIX server" type deployments. +# +# See "man NetworkManager.conf" for more information about these +# and other keys. + +[main] +# Do not do automatic (DHCP/SLAAC) configuration on ethernet devices +# with no other matching connections. +no-auto-default=* + +# Ignore the carrier (cable plugged in) state when attempting to +# activate static-IP connections. +ignore-carrier=* diff --git a/SPECS/20-connectivity-fedora.conf b/SPECS/20-connectivity-fedora.conf new file mode 100644 index 0000000..4c398c3 --- /dev/null +++ b/SPECS/20-connectivity-fedora.conf @@ -0,0 +1,9 @@ +# Enable connectivity checking for NetworkManager. +# See `man NetworkManager.conf`. +# +# Note that connectivity checking works badly with rp_filter set to +# strict. Check "/proc/sys/net/ipv4/conf/*/rp_filter". +[connectivity] +uri=http://fedoraproject.org/static/hotspot.txt +response=OK +interval=300 diff --git a/SPECS/20-connectivity-redhat.conf b/SPECS/20-connectivity-redhat.conf new file mode 100644 index 0000000..94783b3 --- /dev/null +++ b/SPECS/20-connectivity-redhat.conf @@ -0,0 +1,9 @@ +# Enable connectivity checking for NetworkManager. +# See `man NetworkManager.conf`. +# +# Note that connectivity checking works badly with rp_filter set to +# strict. Check "/proc/sys/net/ipv4/conf/*/rp_filter". +[connectivity] +uri=http://static.redhat.com/test/rhel-networkmanager.txt +response=OK +interval=300 diff --git a/SPECS/70-nm-connectivity.conf b/SPECS/70-nm-connectivity.conf new file mode 100644 index 0000000..0e4b0e2 --- /dev/null +++ b/SPECS/70-nm-connectivity.conf @@ -0,0 +1,15 @@ +# The Strict mode of RFC3704 Reverse Path filtering breaks some pretty +# common and reasonable use cases. +# +# Notably, it 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), systemd configures a Loose filter since +# commit 230450d4e4f1 ('sysctl.d: switch net.ipv4.conf.all.rp_filter from 1 +# to 2'). However, RHEL systemd package happens to default to Strict mode +# for historic reasons. Let's override it if we're doing connectivity +# checking. + +# Source route verification +net.ipv4.conf.all.rp_filter = 0 diff --git a/SPECS/NetworkManager-1.26.0.tar.xz b/SPECS/NetworkManager-1.26.0.tar.xz new file mode 100644 index 0000000..d6a9572 Binary files /dev/null and b/SPECS/NetworkManager-1.26.0.tar.xz differ diff --git a/SPECS/NetworkManager.conf b/SPECS/NetworkManager.conf new file mode 100644 index 0000000..6ee4797 --- /dev/null +++ b/SPECS/NetworkManager.conf @@ -0,0 +1,50 @@ +# Configuration file for NetworkManager. +# +# See "man 5 NetworkManager.conf" for details. +# +# The directories /usr/lib/NetworkManager/conf.d/ and /run/NetworkManager/conf.d/ +# can contain additional configuration snippets installed by packages. These files are +# read before NetworkManager.conf and have thus lowest priority. +# The directory /etc/NetworkManager/conf.d/ can contain additional configuration +# snippets. Those snippets are merged last and overwrite the settings from this main +# file. +# +# The files within one conf.d/ directory are read in asciibetical order. +# +# If /etc/NetworkManager/conf.d/ contains a file with the same name as +# /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored. +# Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can +# put an empty file to /etc with the same name. The same applies with respect +# to the directory /run/NetworkManager/conf.d where files in /run shadow +# /usr/lib and are themselves shadowed by files under /etc. +# +# If two files define the same key, the one that is read afterwards will overwrite +# the previous one. + +[main] +#plugins=ifcfg-rh + + +[logging] +# When debugging NetworkManager, enabling debug logging is of great help. +# +# Logfiles contain no passwords and little sensitive information. But please +# check before posting the file online. You can also personally hand over the +# logfile to a NM developer to treat it confidential. Meet us on #nm on freenode. +# Please post full logfiles except minimal modifications of private data. +# +# You can also change the log-level at runtime via +# $ nmcli general logging level TRACE domains ALL +# However, usually it's cleaner to enable debug logging +# in the configuration and restart NetworkManager so that +# debug logging is enabled from the start. +# +# You will find the logfiles in syslog, for example via +# $ journalctl -u NetworkManager +# +# Note that debug logging of NetworkManager can be quite verbose. Some messages +# might be rate-limited by the logging daemon (see RateLimitIntervalSec, RateLimitBurst +# in man journald.conf). Please disable rate-limiting before collecting debug logs. +# +#level=TRACE +#domains=ALL