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
Lubomir, does this need more than the change in bug 2067117? What's your opinion on this?
(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.