Error: Connection activation failed: 802.1X supplicant took too long to authenticate
Hint: use ‘journalctl -xe NM_CONNECTION=e9d14ef2-413b-4f0c-9cc7-1e82bfa6ecea + NM_DEVICE=mlan0’ to get more details.
nmcli device status screenshot is attached. the wifi device mlan0 which is available is disconnected. what is the procedure to enable it.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello Nisha,
Thank you for reaching out with your WiFi connectivity issue on the Verdin iMX8M Plus with TorizonCore 6.8.2. Let’s go through some steps to help resolve the problem:
Verify WiFi Hardware and Configuration:
Ensure that the WiFi module is properly connected and recognized by the system. Use nmcli device to list network devices and confirm that mlan0 is listed.
Check that the WiFi module is enabled by using nmcli radio wifi on.
Check NetworkManager Logs:
Use the command journalctl -xe NM_CONNECTION=<connection-uuid> + NM_DEVICE=mlan0 to view detailed logs. Replace <connection-uuid> with the actual UUID of your connection.
Look for any specific error messages that might indicate the cause of the timeout.
802.1X Authentication Settings:
Ensure that your WiFi network requires 802.1X authentication and that the correct credentials and settings are configured in NetworkManager.
Verify the configuration file for the connection in /etc/NetworkManager/system-connections/ and ensure that the eap method and credentials are correctly set.
NetworkManager Configuration:
Consider increasing the timeout settings for 802.1X authentication in NetworkManager. Edit the connection settings to increase the auth-timeout parameter if available.
Driver and Firmware Updates:
Ensure that the WiFi driver and firmware are up to date. Check for any updates or patches that might be available for your setup.
Test with a Different Network:
If possible, test the connection with a different WiFi network to rule out network-specific issues.
By following these steps, you should be able to diagnose and potentially resolve the WiFi connectivity issue. If the problem persists, further investigation into the software configuration may be necessary.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
I’m a little confused about your situation. Are you trying to connect the Verdin i.MX8M Plus to an access point or are you trying to turn the module into an access point?
In your initial post you linked to the section of the documentation, about configuring the Toardex module as an access point. But the rest of your work looks like you’re trying to connect to an access point using the module.
Could you also share what exact commands you ran on the module to get to where you are currently.
I used the following commands to enable the access point mode.
nmcli con add type wifi ifname mlan0 mode ap con-name wifi6 ssid wifi6
nmcli con modify wifi6 802-11-wireless-security.key-mgmt wpa-psk
nmcli con modify wifi6 802-11-wireless-security.proto rsn
nmcli con modify wifi6 802-11-wireless-security.group ccmp
nmcli con modify wifi6 802-11-wireless-security.pairwise ccmp
nmcli con modify wifi6 802-11-wireless-security.psk 123456789
nmcli con modify wifi6 ipv4.addresses 192.168.1.36
nmcli con modify wifi6 ipv4.method manual
nmcli con up wifi6
Initially the wifi interface named mlan0 was disconnected or inactive. So the command “nmcli con up wifi6” couldnt activate the wifi ap.
Later i used the command “sudo systemctl restart NetworkManager.service”, which changed the status of the wifi interface mlan0 to connected or active state. After this nmcli con up command worked fine.
Now, the verdin module’s access point “wifi6” is enabled. when I want to connect to this wifi6 from a laptop, i’m unable to connect to the access point. I have tried both hostapd and network manager method but i’m unable to connect to the AP
If you are trying to configure an access point then why are you deviating from the instructions in the documentation you linked earlier? The section on Wi-Fi access point does not use NetworkManager at all: Networking with Torizon OS | Toradex Developer Center
Also mlan0 is not even the WiFi access point interface that is the WiFi client interface.
Could you try again with the instructions exactly as shown in the documentation.
