Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, it seems that the issue arises from the automatic channel selection feature of the hostapd configuration, which is selecting an invalid channel (channel 34, freq=5170) for the US region. This is causing connectivity issues, particularly for devices like PCs and phones, while some Verdin-based stations remain connected.
Here are some steps you can take to address this issue:
-
Manual Channel Configuration: As you have already attempted, setting the channel manually to a valid channel (e.g., channel 44) is a good step. Ensure that this configuration is persistent and not overridden by any other scripts or configurations.
-
Firmware and Software Updates: Check for any available updates for the hostapd software and the firmware of the Wi-Fi module. Updates may contain fixes for known issues related to channel selection.
-
Configuration Verification: Double-check the hostapd configuration file to ensure there are no conflicting settings that might cause the channel to revert to an invalid one. Also, verify that no other processes or scripts are modifying the configuration at runtime.
-
Logging and Monitoring: Implement detailed logging to capture events related to channel changes. This can help identify the exact conditions under which the channel switches back to an invalid one.
-
Regulatory Domain Settings: Ensure that the regulatory domain settings are correctly configured for the US. This can be done by setting the correct country code in the hostapd configuration and ensuring that the kernel’s regulatory database is up to date.
-
Hardware Compatibility: Verify that the Wi-Fi hardware being used is fully compatible with the channels and configurations being set. Some hardware might have limitations or require specific configurations to operate correctly.
If these steps do not resolve the issue, further investigation into the specific hardware and software interactions may be necessary, possibly involving support from Toradex or the hardware vendor.
Please, also check if these links can help you solve your problem: