Created attachment 1643703 [details]
nmcli debug log
Description of problem:
I'm no longer to connect to our internal WPA2 Red Hat Wifi.
Downgrading to 1.22.0-0.1.el8 works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.connect to Red Hat Wifi
hm, are you sure that 1.22.0-0.1.el8 works? That would be unexpected, but if you are sure, quite some important information.
Without this piece of information I would have said this is a wpa-supplicant or driver issue...
Could you also attach a level=TRACE log with a working case? Thank you.
Created attachment 1644352 [details]
old nmcli debug trace
Successfully connected with NetworkManager-1.22.0-0.1.el8
It seems the new internal DHCP client implementation times out when requesting a lease:
[1575993447.6522] dhcp4 (wlp2s0): sent DISCOVER to 0.0.0.0
[1575993485.4081] dhcp4 (wlp2s0): request timed out
The old client based on systemd is working well instead.
I can confirm this, if I use dhclient option with NetworkManager-1.22.0-0.2.el8, I'm able to connect.
$ NetworkManager --print-config
# NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf (etc: 99-dhcp.conf)
# no-auto-default file "/var/lib/NetworkManager/no-auto-default.state"
Also, the Wi-Fi settings for wpa-supplicant differ. Which is odd...
Jiri, cuould you please also show the profile in question?
First, identify the file in which it is stored:
nmcli -f UUID,NAME,FILENAME connection show
Then, attach the corresponding file (sanitizing private data first!!).
Probably it's in "/etc/sysconfig/network-scripts/ifcfg-$NAME". In that case, make sure to include all relevant "/etc/sysconfig/network-scripts/*-$NAME" files.
Created attachment 1644480 [details]
The AUTH_RETRIES=1 were suggested by Vladimir, but it didn't make it work.
Created attachment 1644489 [details]
nmcli debug log
(In reply to Thomas Haller from comment #5)
> Also, the Wi-Fi settings for wpa-supplicant differ. Which is odd...
As part of debugging, I have deleted the old profile and created new one from scratch.
This output is from the profile I have pasted and the same I used with the -1 build.
could you please capture packet traces when NM tries to connect, first with dhcp=internal and then with dhcp=dhclient? You can use a command like:
sudo tcpdump -i any -w wifi-internal.pcap
You can send the output files via email to me if you prefer. Thank you.
Upstream merge request:
I cannot reproduce anymore, with or without lease file.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.