we are using Teltonika routers for remote maintenance of our products (mechanical engineering).
Since we only access the machines when there is an malfunction or something like, the customers do not want do have the RUT 24/7 online.
We are thinking about using a physical key switch mapped to the RUT digital input.
But what is the best way to turn off?
Deactivate complete WAN interface → Seems kind of harsh and we also had a use case where a customers needs access from WAN side too.
Is there a way to disable the RMS connection via script? This would probably be the best method.
Or should I enable firewall rule LAN → WAN when the key switch gets activated and otherwhise leave the firewall rule disabled?
Using the digital input to control access is a good approach.
Instead of disabling the WAN interface, I’d avoid that unless you specifically want to disconnect the router from the internet. Turning off the WAN can affect other services the customer may still rely on.
A cleaner solution is to control only the remote management path:
If your goal is to prevent remote maintenance, enabling/disabling firewall rules based on the digital input is a practical option. When the key switch is OFF, block the required inbound/outbound traffic. When it’s ON, re-enable the rules.
If you’re using RMS, check whether the RMS service can be started/stopped via a script on your firmware version. If that’s supported, it would be the most elegant solution since it only affects the management connection and leaves normal internet connectivity untouched.
Another option is to trigger a Hotplug or I/O event script from the digital input so the behavior is automatic without requiring manual configuration changes.
I’d be interested to know if anyone has implemented start/stop control for the RMS service directly through scripts, as that seems like the cleanest solution for this use case.
Actually, you don’t need any scripts or WAN disabling for this. There’s a much simpler way using just the built-in Event Juggler in RutOS. It controls the RMS connection directly and takes less than a second without dropping the internet.
Here is how to set it up:
Create the Events:
Go to Services → Event Juggler
Create a new event named for example Event_ON: Enable event, set Event type to I/O, select I/O pin name Input(3), and set Trigger to Rising.
Create a second event named for example Event_OFF: Enable event,set Event type to I/O, select the same input pin, and set Trigger to Falling.
Configure Actions for the Events:
Expand the Event:On the far right of the event row, click the arrow icon(v) to expand the event panel. This will reveal the action table below.
Manage the Action:Under the Manage actions column:
For Event_ON: Click Edit (or Add new if the row is empty). In the configuration window that opens:
Change Action name to Action_ON (or any name you prefer).
Set Action type to RMS.
Switch RMS state to on.
For Event_OFF: Click Edit (or Add new if the row is empty). In the configuration window that opens:
Change Action name to Action_OFF.
Set Action type to RMS.
Switch RMS state to off.
Click Save & Apply at the bottom of the page.
This is by far the cleanest way to do it. It only toggles the RMS service itself and leaves everything else running perfectly.
I am still waiting for my colleague from the electrical department to wire it up and test the setup. Unfortunately, I think it will take 1-2 months because it will be tested as part of the project itself.
That’s why I can’t provide any more information right now.