RUT200 Custom Scripts

I use the custom scripts to automatically execute a script with the name “connection” when the router is initialized. This was previously located in the “/bin/” folder. Since the firmware update, this is apparently read-only, which is why I put it in the “root” folder → “/root/connection”.

Unfortunately, this script does not run from system startup. Do i need to change something here, to make it runable? (RUT200 Custom Scripts - Teltonika Networks Wiki)
My custom script:
#!/bin/sh
/root/connection &
exit 0

I have tried everything. Even put the script into init.d and activated it. Nothing helps. What is going on here?

Does anyone know more here? Please :slight_smile:

Does the script run normally when executed on SSH? Is it a shell script? If so you could copy all the contents and paste into custom script window.

I can start the scripts manually and then it works…
I don’t want alle the content in the custom scipt window. :frowning:

i now downgraded the firmware version to 13.x and it is working again. But now i observe a highly unstable connection.

With firmware 7.14 Teltonika decided to “Improve” security, and this resulted in a lot of file directories and packages being blocked. The reason for it being blocked is because custom scripts now run as admin and not as root. This is a huge headache and I seriously hope Teltonika undo’s this horrendous change.

Hello @Sarah2610,

Apologies for the delayed response.

Starting from firmware version 7.14, custom scripts should be placed in the /usr/local directory. For scheduling their execution, you can use crontabs. More information is available on our wiki page: Crontabs – Teltonika Networks Wiki

Please let me know if you have any further questions or need assistance.

Best regards,

Hello @Sarah2610,

To add, starting with firmware version 7.15, there have been changes to how scripts are executed. As part of our new architecture, services and applications, including scripts run via the “Event Juggler” or custom scripts at startup, no longer execute with root privileges. This means your Lua script and custom startup scripts will now run with the same user privileges as the application itself, and this behavior will continue in future firmware releases.

We appreciate your understanding.

Best regards,