Dear Teltonika Support Team,
I am experiencing an issue with the Wi-Fi WAN client on my RUTC41 and would appreciate your assistance in identifying the cause.
Device information
- Model: Teltonika RUTC41
- Firmware: RUTC_R_00.07.26
- Wi-Fi client interface: radio0 (2.4 GHz)
- Wi-Fi client network: wan1 (wifi0)
Problem description
Under regular circumstances internet access is provided via the wired WAN port. A Wi-Fi WAN client is used as failover, connecting to an external hotspot.
If i unplug the wan cable, the router transitions perfectly to using Wi-Fi WAN. However, if the router is rebooted while the Ethernet WAN cable is disconnected, the Wi-Fi WAN client does not initialize successfully.
After rebooting, the router’s GUI displays:
- Wifi0: Inactive
- Reason: The SSID configured for the Wi-Fi client is in status “Starting”.
The status remains unchanged even though the external hotspot is active and available throughout the reboot process.
Interestingly, if the router is booted with the Ethernet WAN connection present and the Ethernet cable is disconnected afterwards, the Wi-Fi WAN client connects successfully and provides the expected WAN failover functionality.
This suggests that the issue may be related to the initialization sequence of the Wi-Fi WAN client during router startup, particularly when no Ethernet WAN connection is available.
Troubleshooting and observations
I have already verified the following:
- The Wi-Fi client configuration is present and correctly references the smartphone hotspot.
- The router detects the configured station interface in its wireless configuration.
- The WPA supplicant configuration file for the client interface is generated correctly.
- The WPA supplicant process is running.
- However, the expected wireless interface
wlan0-1is not created after the failed startup. - The WAN interface
wan1consequently reportsNO_DEVICE.
The following messages were recorded in the system log during startup:
Interface setup failed: WPA_SUPPLICANT_FAILED
WARNING (wireless_add_process):
executable path /usr/sbin/wpad does not match process path (/proc/exe)
Command failed: ubus call network.wireless notify
(Invalid argument)
Interface socket does not exist at:
/var/run/wpa_supplicant/wlan0-1
Questions
Could you please clarify:
- Is this a known issue with RUTC41 firmware RUTC_R_00.07.26?
- Are there any known problems with initializing a Wi-Fi STA interface during boot when the Ethernet WAN interface is unavailable?
- Could this be related to the startup sequence of
wpad,netifd, or the creation of the wireless STA interface? - Is there a recommended firmware version, configuration adjustment, or workaround for this issue?
I would particularly appreciate confirmation whether this is a known firmware issue or whether additional diagnostic information is required.
I can provide the complete system log and configuration details if needed.
Thank you for your assistance.
Best regards