Bug 2083565

Summary: [NMCI] failures in 8021x_hostapd_freeradius_doc_procedure (wpa_supplicant not getting a reply)
Product: Red Hat Enterprise Linux 9 Reporter: David Jaša <djasa>
Component: wpa_supplicantAssignee: Davide Caratti <dcaratti>
Status: CLOSED MIGRATED QA Contact: Laura Trivelloni <ltrivell>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: rvr, sukulkar
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 10:05:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
behave report
none
behave report (NM 1.38)
none
behave report (NM 1.34)
none
behave report (with EAPOL traffic dumped)
none
behave report (with EAPOL traffic dumped and tcpdumps available)
none
1st pcap: standalone supplicant (TTLS)
none
2st pcap: NM-called supplicant (TTLS)
none
3rd pcap: standalone supplicant (TLS)
none
4th pcap: NM-called supplicant (TTLS): failure none

Description David Jaša 2022-05-10 11:07:57 UTC
Created attachment 1878286 [details]
behave report

Description of problem:
We encounter failures in 8021x_hostapd_freeradius_doc_procedure which are pretty frequent on el8 (in default machines and VMs) that wpa_supplicant can't get a reply. We don't have yet a definite proof that this doesn't happen somewhere in the setup, hopefully integration of tcpdumps will shed some light on it soon.

Most of the times, wpa_supplicant called by NM is affected but sometimes even wpa_supplicant called from shell (see Behave reports that will be attached)

Version-Release number of selected component (if applicable):
NM upstream and downstream
8.6 and 8.7 versions of wpa_supplicant, hostapd and freeradius, e.g.:
wpa_supplicant-2.10-1.el8.x86_64
hostapd-2.10-1.el8.x86_64
freeradius-3.0.20-12.module+el8.6.0+13617+542eca26.x86_64

How reproducible:
frequently but not always

Comment 1 David Jaša 2022-05-10 11:09:41 UTC
Created attachment 1878287 [details]
behave report (NM 1.38)

Comment 2 David Jaša 2022-05-10 11:10:33 UTC
Created attachment 1878288 [details]
behave report (NM 1.34)

Comment 3 David Jaša 2022-05-12 11:47:10 UTC
Created attachment 1878910 [details]
behave report (with EAPOL traffic dumped)

Comment 4 David Jaša 2022-05-12 15:23:01 UTC
Created attachment 1878971 [details]
behave report (with EAPOL traffic dumped and tcpdumps available)

I managed to capture this bug happening at latest stage (NM autheticating via EAP-TTLS) and I have tcpdump pcaps for all the EAPOL converation so I'm obsoleting previous attachments and I'll attach the pcaps as further attachments

Comment 5 David Jaša 2022-05-12 15:24:00 UTC
Created attachment 1878972 [details]
1st pcap: standalone supplicant (TTLS)

Comment 6 David Jaša 2022-05-12 15:25:00 UTC
Created attachment 1878973 [details]
2st pcap: NM-called supplicant (TTLS)

Comment 7 David Jaša 2022-05-12 15:26:29 UTC
Created attachment 1878974 [details]
3rd pcap: standalone supplicant (TLS)

Comment 8 David Jaša 2022-05-12 15:27:32 UTC
Created attachment 1878976 [details]
4th pcap: NM-called supplicant (TTLS): failure

Comment 9 David Jaša 2022-05-16 08:17:51 UTC
Versions of on ^^^ machine:
NetworkManager-1.39.3-30309.copr.1a995325d5.el8.x86_64
wpa_supplicant-2.10-1.el8.x86_64
hostapd-2.10-1.el8.x86_64
freeradius-3.0.20-12.module+el8.6.0+13617+542eca26.x86_64

Comment 10 RHEL Program Management 2023-09-21 10:00:36 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 11 RHEL Program Management 2023-09-21 10:05:37 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.