Thanks for contacting Teltonika Networks’ technical support team.
Before I start answering your questions, I would like to recommend a different device. In your specific situation, RUTX12 would be a better router.
You are correct, RUT956 has 2 SIM slots, but it has only 1 LTE CAT4 modem. Meaning, that RUT956 can use only 1 SIM card at a time. The second one will work as a backup and bonding would only potentially work with 1 mobile interface, wired WAN, and Wi-FI at the same time. In addition, RUT956 has only 100 Mbps ports and supports 2.4GHz Wi-Fi.
On the other hand, RUTX12 has 2 LTE CAT6 modems and 2 SIM cards. RUTX12 can use those 2 SIM cards at the same time. With this device, bonding will work with 2 mobile interfaces, wired WAN, and Wi-FI simultaneously. You will get even better streaming quality/stability. In addition, RUTX12 has gigabit ports and supports 2.4GHz and 5GHz Wi-Fi.
You mentioned that this setup will run on a powerbank inside a car. Teltonika Networks also provides an automotive power supply adapter: AUTOMOTIVE POWER SUPPLY.
If are concerned about power usage, then you could choose RUTX11. Keep in mind that RUTX11 has only 1 CAT6 modem and you will be able to use only 1 SIM card at a time. RUTX11 Is a little bit more power-friendly, even though it offers similar performance when comparing RUTX11 and RUTX12 with 1 SIM card active.
For more information regarding RUTX11 and RUTX12 power usage view the pages below.
RUTX11 power usage tests: RUTX11 Power Consumption - Teltonika Networks Wiki
RUTX12 power usage tests: RUTX12 Power Consumption - Teltonika Networks Wiki
Regarding your questions.
Since questions 1 and 2 are both about accessing the router and devices under it (inside LAN) I will combine the questions.
To begin with, bonding technology is provided by our partners Bondix Intelligence. Bonding allows to combine multiple WAN interfaces into one for greater single connections speeds. In the scenario where 2 different SIM cards are used then a wider mobile connectivity coverage would be also possible. Keep in mind that this is a paid solution, and you will need additional coordination with Bondix Intelligence.
For more information about Bondix Intelligence view our wiki page: Bondix Intelligence - Teltonika Networks Wiki
To remotely reach your devices, there are 3 possible solutions in your scenario:
- If Bondix Intelligence will provide you with a static public IP. You can use simple port forwarding rules to connect to your devices.
To configure S.A.NE server and create a port forward rule to reach a device inside router’s LAN view Bondix Intelligence’s wiki page: Teltonika Portforwarding - Bondix Wiki. It describes how to set a static public IP for S.A.NE server and create a port forward rule to reach a device under RUT951. With this solution, you could reach the camera using the S.A.NE server’s IP + port combination.
Disclaimer: for more specific instructions you will need to contact Bondix themselves. In addition, there is a possibility that Bondix will tell you to use an older RUTOS firmware if they have not updated their bonding software for our newer firmware.
- If Bondix Intelligence will provide you with a dynamic public IP. You can use port forwarding rules and DDNS to connect to your devices.
Since the DDNS software will have to be installed in the S.A.NE server then, unfortunately, we cannot provide you with specific instructions on how to complete this setup. As mentioned earlier, bonding technology is provided by our partner Bondix Intelligence, and for detailed instructions on how to set up a DDNS with S.A.NE server and create specific port forwarding rules for this scenario, you will need to contact Bondix themselves.
Talking about DDNS in general, you do need public IPs. They can be dynamic or static but they have to be public. If they are private then the DDNS server, which is somewhere in the internet, will not be able to reach the DDNS client.
- If you will be able to only get private IPs for your SIM cards and Starlink and you decide to not use bonding then you could use our Remote Management System (RMS) to reach the devices. To reach devices remotely via RMS you do not need public IPs. You only need to provide them with internet connectivity from some kind of source. It can be mobile, wired, or Wi-Fi.
To remotely connect to your router’s WebUI you can simply generate WebUI access link and connect to the device.
Go to Devices and select the Device WebUI button.
In the window, press Connect. This will generate a WebUI access link for 30 minutes. If you want a link that would last longer then, change the Duration until settings according to your needs. Then press Generate.
To remotely access devices inside a router’s LAN using RMS. There are two solutions
Firstly, RMS has a feature RMS Connect. It allows to reach devices inside the router’s LAN. RMS Connect supports SSH, Telnet, HTTP(S), RDP, VNC, and SFTP protocols. To configure this kind of setup our wiki page has a great page explaining RMS Connect feature: RMS Remote Access - Teltonika Networks Wiki
Secondly, you could create a VPN hub and put the router and its LAN devices into a VPN. Then by connecting your pc to this VPN you would be able to access the router and its LAN devices. To properly set up this configuration our wiki page has a great page explaining the RMS VPN hub feature: RMS VPN Hubs - Teltonika Networks Wiki
If you decide to not use bonding , then I recommend setting up either load balancing or failover on all your WAN interfaces. Load balancing allows you to distribute your traffic over multiple WAN interfaces while Failover allows you to set a main WAN interface and then create backups. In the scenario, when the main internet connection is lost then the backup will step in and provide the internet.
For more information about failover and load balancing view our wiki page: RUTX12 Failover - Teltonika Networks Wiki
Regarding altitude data from GPS. GPGAA/GAGGA NMEA codes provide altitude. **GGA provides 2 altitudes. First, altitude above mean sea level (geoid) in meters. Second, the height of geoid (mean at sea level) above the WGS84 ellipsoid. The altitude readings in **GGA messages will be near the letter M.
Your mentioned NMEA feed solution could provide the altitude. Keep in mind that the server for NMEA data forwarding should either have a public IP or be reachable by the router via other routes.
For more information about setting up an NMEA feed view our wiki page: RUTX12 GPS - Teltonika Networks Wiki
If you have more questions, feel free to ask.