Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When bringing down 802.1x connection, my expectation is that EAPOL-logoff frame is sent so that authenticator can change switch port in question to unautheticated state right away. You can do that manually by issuing 'wpa_cli ... logoff' but that doesn't look right behaviour to me.
Version-Release number of selected component (if applicable):
NetworkManager-1.37.2-1.el9.x86_64
wpa_supplicant-2.10-2.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. create 802.1x wired connection
2. bring the connection up
3. bring the connection down
Actual results:
authenticator (hostapd) is not informed that NM's station is closing connection
Expected results:
EAPOL-logoff frame is sent and authenticator knows that the station got disconnected
Additional info:
related bug: bug 2067117
(In reply to Till Maas from comment #1)
> Lubomir, does this need more than the change in bug 2067117? What's your
> opinion on this?
I think so, if you bring up and down 802.1x-protected connection, wpa_supplicant service keeps running with the same PID so even if wpa_supplicant starts logging off on signals like SIGTERM, it won't solve scenario of bringing active connection or device down.
(In reply to Till Maas from comment #1)
> Lubomir, does this need more than the change in bug 2067117? What's your
> opinion on this?
Yes, I think it's pretty much what David says. Bringing the connection down is different from terminating the daemon altogether.
Based on https://bugzilla.redhat.com/show_bug.cgi?id=2067117#c4 this won't change the default behavior. Also, it does not appear that an actual user is requesting this. Therefore, due to lack of capacity, I am going to close this.