Bug 1832273 - LLDP: add lldp status device property
Summary: LLDP: add lldp status device property
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.0
Assignee: Wen Liang
QA Contact: Filip Pokryvka
Depends On:
Blocks: 1935910
TreeView+ depends on / blocked
Reported: 2020-05-06 12:48 UTC by Fernando F. Mancera
Modified: 2021-11-10 06:46 UTC (History)
13 users (show)

Fixed In Version: NetworkManager-1.32.0-0.2.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-11-09 19:28:54 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4361 0 None None None 2021-11-09 19:29:30 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 782 0 None opened connection: add @lldp_status_flag_libnm test 2021-06-18 11:35:02 UTC

Description Fernando F. Mancera 2020-05-06 12:48:14 UTC
Description of problem:

Currently libnm does not expose any lldp status property in NM.Device. It would be nice to have one, this way nmstate could check easily if the device is listening LLDP packets.

Actual results:

There is no such property.

Expected results:

There is a LLDP status property.

Comment 6 Wen Liang 2021-03-01 00:33:39 UTC
upstream PR for fixing it , https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/712

Comment 7 Wen Liang 2021-04-14 11:47:15 UTC
Upstream PR has been merged, https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/712

Comment 13 errata-xmlrpc 2021-11-09 19:28:54 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 (Moderate: NetworkManager security, 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.


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