Using Cellular Routers for Remote Site Communication

Good morning automation fans! Today we will be discussing our use and compatibility of two different manufacturers of cellular routers, the technical difficulties we ran into, the attempted resolution paths for those issues, the solution that ultimately worked and finally the deployment of these remote site cellular routers.
These routers were attached to the DIN rail via mounts that arrived after these pictures were taken
Our client in South Texas has handfuls of remote water distribution sites that communicate back to a central location. Currently they are using MDS iNET II 900 radios for site communications and have been for the past 10+ years. These work but come with their own issues like antenna placement/alignment, rent for the antenna locations if they do not own the infrastructure and lightning strikes. To try and get around these pesky issues, we decided to use the Sierra Wireless XR60 and RX55 Cellular routers. Unfortunately, since these two devices do not support OpenVPN, we attempted to use IPsec to get them communicating to each other. "IPsec (Internet Protocol Security) is a suite of protocols that authenticates and encrypts IP packets to secure communication between two points over a network — typically operating at the network layer (Layer 3), so it protects traffic transparently without requiring changes to individual applications." If that explanation went right over your head then congratulations, we are in the same boat. I am not an IT person nor do I pretend to be one but we gave it the "ol' college try". Long story short: it did NOT work out. The main issue was that IPsec tunnel policies (traffic selectors) are usually defined by subnet, not host. If both ends (the XR60 & RX55) use the same subnet (which they did due to the configuration of the existing radio network that will not be modified), each router can't tell whether 192.xxx.2.xxx traffic is meant for its own local network or for the remote network across the tunnel — the routing table has no way to differentiate. So, we did some research/investigation on devices that were capable of performing the tasks that we required and settled on an RUTM54 by TELTONIKA. We reached out to their sales & support team, who were fantastic by the way, and they sent us a demo model to check out. After some initial testing we decided that it would work for our application and ordered our own RUTM54 cellular router. Unfortunately, we have now arrived at our second roadblock: incompatible certificates.
We configured the RUTM54 to run an OpenVPN server to be the "base station" that the remote sites (using the Sierra Wireless RX55 & XR60) would connect and send data to. I mentioned previously that the Sierra devices don't "technically" support OpenVPN protocol, so we had to play certificate gymnastics to try and find a solution that would allow us to connect the RX55 to the OpenVPN server. The TELTONIKA RUTM54 would generate the certificates required for a client device to connect BUT it turned out to be missing a critical component that the Sierra RX55 apparently needed: the 'Key Usage' (Also, at this point, I had no idea that the Sierra Wireless routers only supported a TUN configuration and not a TAP. It would not of worked anyway even if the 'Key Usage' issue did not stop me). Don't even bother asking because I still don't fully understand it or why it was missing from the generated certificates. After much research, investigation and the use of Claude AI to scour the internet for solutions, I thought I had a path forward. A dark and gloomy path but a path none the less: generate the required certificates using the command line interface (CLI) available on the RUTM54. I dive into the CLI with Claude, the lifeguard on duty, and start churning out certificates that had the missing key usage information. Once that was complete, I excitedly navigated back to the certificate library on the RUTM54 to export them out to use in the RX55 and get these devices talking. Guess what I found? NOTHING. None of the certificates I generated using the CLI were visible. Just my luck, an unknown bug. Certificates generated using the CLI are not visible to the user interface. So back to the CLI I went, entered the commands to print the certificates to the screen, copied & pasted them to text files and saved them with the correct file types (.cert.pem or .cert.key). Then I had to import them back to the RUTM54 certificate library so they would visible in the user interface. Finally I uploaded the certificates to the RX55, crossed my fingers, and enabled the VPN connection.
-VPN: FAILED- Fantastic.
At this point we hit the pause button on the project, ordered another TELTONIKA cellular router, the RUTM20, to replace the Sierra Wireless RX55 & XR60. Once we received our new cellular router and got the SIM card updated for that device (SIM card tied to the device IMEI# -whatever- moving on) I generated the OpenVPN Client profile on the RUTM54, imported it into the RUTM20. . . . . . . . . . . . . . . . . . .
-VPN: CONNECTED-
If your wondering if there is a "VPN Tunnel Established" song & dance, you can sleep easy knowing there most CERTAINLY is! Now that the OpenVPN tunnel is up and running, we performed a real world test with two of or test controllers (an Opto22 Pac R2 & EPIC PR1) and transferred data from the 'client' to the 'server'. We left that test running for about 4 days without any issues. Packed up the two small panels containing a power supply and the TELTONIKA routers and shipped them to our customer for installation. But WAIT, there's more. . . . . . . .
FedEx absolutely destroyed the 'client' panel while in transit to our customer. We had to order another RUTM20 cellular router to replace the damaged device, get our customer to send back the 'server' panel that was delivered and perform the testing all over again. Panels tested and resent to the customer where they arrived safely this time. From there it was PLUG & PLAY. Once the network cables were moved from the MDS radios to the cellular routers, communications turned green and we were in business baby! The TELTONIKA devices also have an online remote management service (RMS) that gives you access to the devices. Perfect for managing the devices that are currently deployed in the field. Anything you can do while connected directly to the router you can do through the RMS.
Hey ACI, what about the two ($600+) Sierra Wireless cellular routers that you abandoned? Your right, we cant just NOT use them, that's too much money to waste. So I came up with an easy solution. Since those routers do not support the type of VPN tunnel being used, we purchased a TELTONIKA RUT140 non-cellular router/access point that supports OpenVPN. Using the Sierra Wireless cellular routers to provide the internet connectivity to the RUT140 that handles the OpenVPN connection to the 'server', which is then connected to the remote site controller, we established a VPN connection. Yay! Another song & dance performed, money saved! We will NOT be purchasing Sierra Wireless devices ever again. Only TELTONIKA moving forward.
In conclusion, this project was an absolute nightmare, to say the least. But once we switched over to using TELTONIKA it was a lot easier. The support that they provided was prompt and invaluable to the completion of this project. The silver lining to all of this was now I know a lot more about certificates and VPN connections than I ever wanted to. So, if you are ever looking for remote site connectivity support, contact Automated Concepts, we got you covered!





Comments