Thanks for your reply.
The company I am working for produces a range of embedded system ‘appliances’; for example the current project is around a range of LoRaWAN gateway devices that are based on either ARM/Debian or OpenWRT platforms. They share a common web based administration interface across the range.
There is a requirement to be able to remotely access the devices once they are deployed in the field. All the usual remote access approaches are provided for in the design, but as you know, they all involve potentially compromising security by opening ports, and, probably more importantly, they are dependent on significant levels of end user knowledge to ensure security is maintained.
What we would like to be able to do is the ship the product with no open ports and the appropriate Remote.it module installed, so that one of the options the end user has for remote access is to use Remote.it, thereby making it easy to implement a secure solution, if for no other reason than it is so simple to activate without having to worry about open ports etc.
So I did an implementation using the CLI module on the ARM/Debian platform. It turns out to be a very neat solution.
The user decides that they want to use the Remote.it option for remote access, so the first thing they do is open a Remote.it account.
The user then has a relationship with Remote.it and can work out with you whatever licencing model is appropriate.
On the device we have a screen where the user enters the details of Remote.it account which the device will be associated with, the Device Name that will be displayed, and selects the services (HTTP, SSH) that are to be enabled. Click the Register button, and the job is done.
Log in to the Remote.it page (app.remote.it/#devices) and the device is there in the Device List waiting to be used.
The process is very simple for the user to navigate for the first time, and the chances of needing to contact technical support are pretty small.
Users who have trialled it love it. Sweet!
So, now having sold this approach to the management, we want to do the same thing on the OpenWRT based devices.
Ooops! Curiously, there is no CLI module option for OpenWrt. Why???
OK, so now we start playing around with the other remoteit module that would normally run interactively from the command line and generate a Claim Code that is used to register the device.
In the workaround approach as you have described, the end user has to install a Remote.it Desktop application in order to get a Licence key that is then entered into the administration screen on the device, and the registration process proceeds.
Somehow we seem to have lost the elegant simplicity of the CLI based approach.
Asking the first time user to install a Desktop application just to get a Licence key is not something I would be prepared to do, and I am sure that this level of complication will certainly result in support calls to you and us.
The obvious question is why is the CLI module not available for OpenWRT?
And the next question is whether the CLI module is going to be supported in the long term for any platform?
I think Remote.it is an excellent solution for secure remote access, and I am sure it will be widely taken up as a premium remote access solution.
Unfortunately for us, there is just one small piece of the puzzle missing for OpenWRT platforms.
Look forward to hearing your thoughts.