- initrd: add new NBFT parser (RHEL-83058)
- Add support for configuring per-device IPv4 sysctl forwarding option in NetworkManager (RHEL-89582)
- Support reapply on OVS settings (RHEL-86877)
- Add support for configuring the loopback interface in nmtui (RHEL-70484)
- Replace ioctl wth netlink for ethtool in NetworkManager (RHEL-1794)
- NetworkManager does not add the `lock` attribute when `rto_min` is used (RHEL-83752)
- Can not change `bridge.options.mcast-snooping-enable` on partial managemd OVS bridge (RHEL-86767)
Resolves: RHEL-83058
Resolves: RHEL-89582
Resolves: RHEL-86877
Resolves: RHEL-70484
Resolves: RHEL-1794
Resolves: RHEL-83752
Resolves: RHEL-86767
Fix balance-slb ports rarely not being active after reboot
Revert previous attempt to fix build on ppc64.
We limit number of jobs on ppc64 to avoid high RAM usage.
Related: RHEL-77167
They (probably) crash due to high memory usage. The build argument
-flto-partition=none is known to increase memory usage, so remove it.
Related: RHEL-70420
As done in the c9s branch, use 0 as base for patches that change
behavior from upstream, and 1000 for backports. In this way, upon a
rebase we can drop all (1000+x) patches and keep others.
Related: RHEL-35580
Tests were executed many times on AWS in testing-farm so the set
is very stable and we should be able to gate with the set.
We added nm-cloud-setup tests, few simwifi, gsm, loopback, and ovs
tests so pretty everything is covered. We can add more but that
needs to be discussed in NMCI area in mapper.yaml where gating
tests are specified.
https://src.fedoraproject.org/rpms/NetworkManager/pull-request/17
Connectivity check should work fine with the HTTP URI; if there are
problems with that in specific environments, they need to be understood
and explained.
But more importantly, this change breaks captive portal detection, which
is one of the main purposes of connectivity check. A captive portal is
detected by NM by comparing the content returned from the connectivity
URI with a well-known content; if it's different then we assume someone
is hijacking the request (via DNS poisoning or other means). With HTTPS
this mechanism doesn't work because NM is not able to get the content
from the redirected URI due to certificate verification failure.
This reverts commit 6e53c1b52e.
