RUTC41 – Wi-Fi WAN client remains in “Starting” state after reboot without Ethernet WAN

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:

  1. The Wi-Fi client configuration is present and correctly references the smartphone hotspot.
  2. The router detects the configured station interface in its wireless configuration.
  3. The WPA supplicant configuration file for the client interface is generated correctly.
  4. The WPA supplicant process is running.
  5. However, the expected wireless interface wlan0-1 is not created after the failed startup.
  6. The WAN interface wan1 consequently reports NO_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:

  1. Is this a known issue with RUTC41 firmware RUTC_R_00.07.26?
  2. Are there any known problems with initializing a Wi-Fi STA interface during boot when the Ethernet WAN interface is unavailable?
  3. Could this be related to the startup sequence of wpad, netifd, or the creation of the wireless STA interface?
  4. 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

I’d like to add some additional findings concerning the above bug in RutOS:

In the condition where the router boots without wired WAN connection and then fails to initialize the wifi0 WAN client, leading it to remain in status “Starting”, i can make it work by logging in to WebUI, manually disabling the SSID, wait 10 seconds and then re-enabling it.

As temorary workaround, i have now added the below line to the Custom Scripts file, which triggers an automatic wifi reload 30 seconds after boot. With this code snippet added, the router connects successfully to the wifi0 WAN client and has internet, if booted without WAN cable connected.

(sleep 30 && wifi reload) &

I seriously hope this bug will be quickly fixed with one of the next FW updates!

######################################################
Please forward the below comment to management / quality assurance:
######################################################
This is my first time using networking devices from Teltonika. While build quality and pricing of the products appears really good, i have to say that the amount of bugs i have encountered in just a few days of working with your products, far exceeds anything i know from other manufacturers. I really hope Teltonika will improve in this concern.

Dear Teltonika Team,

Since there has been no reply yet regarding the above post about the faulty initialization of the WiFi WAN client interface during router startup, I suspect it might have gotten lost. I would be grateful if you could briefly confirm whether the issue is currently being looked into.

Best regards, APT

Greetings,

Apologies for the delayed response.

I tested your setup on an RUTC41 running firmware version 07.26.2 but was unable to reproduce the issue you described.

For testing, I configured Wired WAN as the highest priority interface and Wi-Fi Client (2.4 GHz) as the second priority interface. I also enabled failover for both interfaces, leaving the rest of the configuration at its default settings.

After rebooting the device with the Wired WAN cable disconnected, the Wi-Fi WAN interface initialized successfully, and the device established an internet connection as expected.

Could you please try upgrading your device to firmware version 07.26.2? Ideally, I would recommend performing the upgrade without keeping settings and then configure the device from scratch.

If you have an extensive configuration that you would prefer not to lose, you can download a backup beforehand in System → Maintenance → Backup. In this case, I would recommend selecting Device backup rather than Configuration backup.

Please note that to restore this backup, you would first need to downgrade the device to firmware version 07.26 (version on which the backup was downloaded)

Additionally, could you provide some more details about your current configuration? Is it mostly default settings, with the router configured as a Wi-Fi Client and failover enabled for both WAN interfaces, or have you made any other changes that might be relevant?

Firmware can be downloaded here: RUTC41 Firmware Downloads - Teltonika Networks Wiki

Best Regards,
Justinas

Hello Justinas,

thank you for your feedback and the tests you carried out.

As requested I have update the router to FW 7.26.2. However, the configuration of this device is fairly complex with 20+ VLAN’s, lot’s of firewall zones, Tailscale, Docker Images, etc. Thus running the FW update without keeping the settings was not an option, i’d spend easily a day or more to reconfigure stuff manually.

Sadly, updating to 7.26.2 did not solve the problem.

My WAN configuration is just like your’s WAN / WAN6 has highest priority, the comes WiFi0 and at last the mobile connections, which i have so far not used in this application, thus all mobile WAN connections are disabled. Wired WAN and wifi0 WAN have both Failover enabled.

RAM usage is approx. 33%, FLASH approx. 56%.

The router still shows the same behaviour. If it is booted with the WAN cable connected and the cable is disconnected during operation, it transitions to wifi0 WAN. When booted without wired WAN connection, the SSID connecting to the extenal hotspot remains in startup state, thus router is permanently offline (unless it can connect again via wired WAN). Since it is installed off-site it is a problem that the device is unreachable thereafter.

The router runs a docker image which is about 50 MB in size. Docker data storage is a drive connected to the routers USB port (which is also used as SAMBA share). CPU utilization caused by the docker image is however marginal, typically 5-15%. However, i can imagine that the initial startup of the router takes a few seconds longer with that docker image. For testing purpose, i disabled automatic starting of the docker image at router startup, this had no effect.

Since the wifi0 WAN client tansitions to RUNNING state perfectly fine once the router has fully booted, and only hangs if it is supposed to do the same during startup, i imagine the problem arises with the internal loading sequence of drivers or certain components needed for the wifi client to work not being ready during bootup at the time when the router tries to activate wifi0 for WAN usage.

As mentioned, when the router is in this wifi0 SSID startup error state and i log in locally, simply disabling the SSID and then re-enabling it again after a few seconds makes it work. Same with the custom script which resets wifi 30 seconds after boot. In my eyes this indicates that there can’t be anything wrong with the configuration.

If without changing anyhting to the configuration, a slightly delayed 2nd wifi initialization makes it work, i can’t see that this has anything to do with configuration and is a router issue.

I can of course send you the router device and / or configuration backup file.

Best regards, APT