RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2013587 - [RFE] Add blackhole routing as a supported routing type in NetworkManager
Summary: [RFE] Add blackhole routing as a supported routing type in NetworkManager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: ---
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Matej Berezny
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks: 1937823
TreeView+ depends on / blocked
 
Reported: 2021-10-13 10:02 UTC by Vojtěch Bůbela
Modified: 2022-05-10 15:30 UTC (History)
12 users (show)

Fixed In Version: NetworkManager-1.36.0-0.8.el8
Doc Type: No Doc Update
Doc Text:
The release note is in BZ#1996617.
Clone Of:
Environment:
Last Closed: 2022-05-10 14:54:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-99625 0 None None None 2021-10-13 10:40:09 UTC
Red Hat Product Errata RHEA-2022:1985 0 None None None 2022-05-10 14:54:30 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 972 0 None opened ip: modified tests to test additional types of routes as well 2022-02-24 22:11:49 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1083 0 None opened [th/route-blackhole] add support for blackhole/unreachable/prohibit route types 2022-02-08 20:29:30 UTC

Description Vojtěch Bůbela 2021-10-13 10:02:34 UTC
Add support for route type blackhole.

Comment 2 Thomas Haller 2021-11-09 09:06:06 UTC
blackhole routes don't have a device. That makes them different from unicast (and most other route types).

It also means, they are more like routing rules. That is, when we activate profiles that configure blackhole routes, then these routes are not per-ifindex, instead they are global. that means, we need a global manager that handles whether to configure a blackhole routes. Like done for routing rules, where we have nmp-rules-manager.h.

Also note that NMPlatform (and NMPlatformIP[46]Route) currently always expect that a route has an ifindex. To support blackhole routes, that needs to be adjusted *first*.

Comment 3 Thomas Haller 2021-11-09 09:08:42 UTC
systemd-networkd supports Type=blackhole. I'd check how that is implemented...

Comment 10 errata-xmlrpc 2022-05-10 14:54:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:1985


Note You need to log in before you can comment on or make changes to this bug.