Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
8068 Discussions

Wifi SPA3 with AX210 (Ubuntu 20.04) connect failed

ChunjieHao
Beginner
‎12-08-2021 12:58 AM
3,007 Views

I am having an issue with network manager when creating a hotspot on my device. After some troubleshooting I was able to narrow the issue down to setting WPA3 as the encryption protocol. On WPA2 the hotspot works without issue. I use  nm-connection-editor to WPA3.

 

I generally use nmcli to start the hotspot via nmcli con up hotspot it fails with the error:

Error: Connection activation failed: 802.1X supplicant took too long to authenticate
Hint: use 'journalctl -xe NM_CONNECTION=51931e8f-e06d-4f86-aefa-d7604162e806 + NM_DEVICE=wlp2s0' to get more details.

 

 

ephw@gepserver:~$ journalctl -xe NM_CONNECTION=51931e8f-e06d-4f86-aefa-d7604162e806 + NM_DEVICE=wlp2s0
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option expiry >
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option ip_addre>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option requeste>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option routers >
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option subnet_m>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): state changed u>
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8070] device (wlp2s0): state change: >
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8322] device (wlp2s0): state change: >
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8329] device (wlp2s0): state change: >
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8388] device (wlp2s0): Activation: su>
lines 976-1001/1001 (END)
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option expiry => '1638959025'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option ip_address => '192.168.1.101'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requested_broadcast_address => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requested_domain_name => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8034] dhcp4 (wlp2s0): option requested_domain_name_servers => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_domain_search => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_host_name => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_interface_mtu => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_ms_classless_static_routes => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_nis_domain => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8035] dhcp4 (wlp2s0): option requested_nis_servers => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_ntp_servers => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_rfc3442_classless_static_routes => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_root_path => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_routers => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_static_routes => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8036] dhcp4 (wlp2s0): option requested_subnet_mask => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option requested_time_offset => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option requested_wpad => '1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option routers => '192.168.1.1'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): option subnet_mask => '255.255.255.0'
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8037] dhcp4 (wlp2s0): state changed unknown -> bound
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8070] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8322] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8329] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
12月 08 16:23:45 gepserver NetworkManager[735]: <info> [1638951825.8388] device (wlp2s0): Activation: successful, device activated.

 


0 Kudos

Link Copied

3 Replies
JosueO_Intel
Moderator
‎12-14-2021 08:20 AM
2,996 Views

Hello ChunjieHao,


Thank you for posting on the Intel communities. In order to have a better understanding of the issue, please share with us the following information: 


  1. How many devices are being affected by this issue?
  2. Was it working before? If so, when did the issue start happening?
  3. Are you using a desktop or a laptop?
  4. Is the Intel® AX200 the original wireless adapter of the system?
  5. Is the issue happening in an enterprise environment?


Also, please download and install the Intel System Support Utility (Intel SSU):

https://www.intel.com/content/www/us/en/download/18895/26735/intel-system-support-utility-for-the-linux-operating-system.html

Open the application and select "Everything" click on "Scan" to see the system and device information. By default, Intel SSU will take you to the "Summary View". Click on the menu where it says "Summary" to change to "Detailed View".  

Click on "Next", save the report and attach it to your response.



Regards, 


Josue O.  

Intel Customer Support Technician



0 Kudos
Copy link
JosueO_Intel
Moderator
‎12-17-2021 05:43 AM
2,971 Views

Hello ChunjieHao,


Were you able to check the previous post?  

Let us know if you still need assistance.  



Regards, 


Josue O.  

Intel Customer Support Technician



0 Kudos
Copy link
JosueO_Intel
Moderator
‎12-21-2021 05:34 AM
2,950 Views

Hello ChunjieHao,


We have not heard back from you, so we will close this thread. If you need any additional information, please submit a new question as this thread will no longer be monitored. 


Best regards,  

Josue O. 

Intel Customer Support Technician



0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.