Author: Byron Paul
Date: 17/11/2023
Device: RUTX11
Having a cellular backup for Starlink is really quite strait forward with Teltonika and here's how you can do it
It is assumed that your Starlink set up already works as is for Internet access before adding a 3rd party router. See Aftermarket Routers for Starlink Systems - General Information for background information.
- Connect your Teltonika router WAN port to the Starlink Ethernet adapter
- Power up and log into your router. Make sure you're getting Internet access and enable 'Advanced Mode'
- Check you are getting a CG-NAT address (100.X.X.X) allocated to your WAN interface, cellular is also connected and double check you are getting internet access through the Teltonika router.
- Set the slider buttons for each interface. Priority is set from top to bottom and you can drag and drop to adjust but most Starlink installations will want the WAN as the first/top entry and cellular as secondary/lower entry.
For a basic install that's pretty much it! Test that failover works and optionally set up notification.
A failover will generally occurs within about 10 seconds of service interruption and failback to the original WAN is about the same.
Optional – Events Reporting
Configure notification for a failover event. As cellular data can be expensive your customer will probably want to know if there has been an event. Assuming the SIM card/account is enabled for SMS it’s very easy to set up an SMS alert under “Services>>Event Reporting”
Choose Event Type = WAN failover, Event Subtype = All, Action = SMS and add the target recipient phone #.
Test again that failover is working and an alert is being sent.
Optional - Fine Tuning Link Detection
If you are finding that the failover is too sensitive or otherwise you can adjust the settings via the pencil icon
This brings up the properties of the failover detection
Field properties are as below:
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turn the interface on or off. |
| Interval | integer [1..65000]; default: 3 | Number of seconds between each test |
| Flush connections on | Connected | Disconnected: none | Flushes established connections after the selected scenario occurs to renew the priorities of configured interfaces. |
| Method | Ping | Wget; default: Ping | Defines how health check will be performed on this interface when determining its state. |
| Track IP | ip | hostname; default: 1.1.1.1,8.8.8.8 | IP address(es) or hostname(s) that will be used to determine an interface's state. If the device receives no response from any of the specified hosts, the interface will be considered as 'Offline'. If this value is missing the interface is always considered up. |
| Reliability | integer [1..65000]; default: 1 | Number of hosts that must reply for the test to be considered successful. Make sure there are at least this many hosts defined in the 'Track IP' field, otherwise the interface will always be considered as 'Offline'. |
| Count | integer [1..65000]; default: 1 | Number of pings to send to each host with each test. |
| Up | integer [1..65000]; default: 3 | Number of successful tests required to considered an interface as 'Online'. |
| Down | integer [1..65000]; default: 3 | Number of failed tests required to considered an interface as 'Offline'. |