TCR100 showing errors in log after firmware upgrade

I have updated TCR100 to one of the latest firmwares TCR1_R_00.07.xx and it started to show failures in multiple places like lease list and wifi client list. The errors are:

/usr/lib/lua/api/network/leases_status:bad argument #1 to 'equal' (string expected, got nil)

When looking into the main page I see an error “Failed to get wireless status” and this from event log:

/usr/lib/lua/api/network/wireless_interfaces_basic:bad argument #1 to 'lower' (string expected, got nil)

I didnt do anything complex in terms of configuration - these errors started when the firmware was updated with the new UI (I think it was the 07.xx).

In terms of network - it works fine - wifi and dhcp server are providing everything.

Is there a way to fix this without resetting? Will it be fine if I backup my config and then reset?

Hello,

The latest firmware version available for the TCR100 is 7.14.4 as seen here: TCR100 Firmware Downloads - Teltonika Networks Wiki

If you could confirm which firmware version you have upgraded to exactly, that would be great.

You may do a backup beforehand, and reset the device, afterward upload the backup. Do note, that you can only upload the backup on the same firmware version (may work uploading on an older one, but could cause some issues).

I’ve also done some research on the error provided, and it says that the error may appear due to the fact that your wireless interface is either non-existant, or has no name set on it. Do double-check that as well please. The configuration file for the wireless might’ve also gone corrupt, this could happen when upgrading from a super old firmware to pretty much the latest one, big jumps like these are recommended only when upgrading without keeping the settings.

I believe the optimal solution for your case would be to completely reset the device (take some screenshots/notes beforehand of your configuration) and reconfigure your device from scratch, this will save you any headache that a backup may bring (it could be that a corrupt file also backups together when the file is generated).

Regards,
M.

So my guess, because I can’t find it in the logs, I was using TCR1_R_00.07.03.2 before upgrading to the TCR1_R_00.07.14.2 which then broke things.

I’ll try fiddling with resetting, but I guess I’ll have to redo all the things again. Thanks for the help

This topic was automatically closed after 60 days. New replies are no longer allowed.