|
|
| Line 70: |
Line 70: |
| | ===Public IP=== | | ===Public IP=== |
| | ---- | | ---- |
| | + | If you're using a SIM card that has a Public IP address (refer [[Private_and_Public_IP_Addresses#Public_IP_address|here]] for more info), you can reach the router via HTTP or SSH via its WAN IP address. |
| | | | |
| | ====HTTP access==== | | ====HTTP access==== |
| | ---- | | ---- |
| | + | Remote HTTP access can be set up via the <b>System</b> → <b>Administration</b> → <b>[[{{{name}}}_Administration#Access_Control|Access Control]]</b> page. |
| | | | |
| | ====SSH access==== | | ====SSH access==== |
| | ---- | | ---- |
| | + | Remote SSH access can be set up via the <b>System</b> → <b>Administration</b> → <b>[[{{{name}}}_Administration#Access_Control|Access Control]]</b> page. |
| | | | |
| | ===SMS=== | | ===SMS=== |
| | ---- | | ---- |
| | + | The {{#ifeq:{{{series}}} | TRB14x | device | router}} can be controlled via SMS messages using SMS utilities rules. SMS can be configured via the <b>Services</b> → <b>SMS Utilities</b> → <b>[[{{{name}}}_Administration#Access_Control|SMS Rules]]</b> page. |
| | | | |
| | ===JSON-RPC=== | | ===JSON-RPC=== |
| | ---- | | ---- |
| | + | JSON-RPC access can be set up via the <b>System</b> → <b>Administration</b> → <b>[[{{{name}}}_SMS_Utilities#Rule_Overview_and_editing|Access Control]]</b> page. |
| | | | |
| | ===VPN=== | | ===VPN=== |
| Line 97: |
Line 102: |
| | ===TR-069=== | | ===TR-069=== |
| | ---- | | ---- |
| − |
| |
| − | One can get the router’s information through '''[[SMS Utilities|SMS]]''' or using '''[[RMS]]''' (Remote Management System). Furthermore, some system related parameters can be obtained using '''[[MQTT]]''' or '''[[RUT955 Modbus|MODBUSD]]''' publisher services. The main focus is on parameters, which change from time to time, like signal strength, operator’s name (it is quite common to change the mobile operator’s name in countries where inner roaming is used) or module temperature. Although it is also possible to read static values, like MAC address, router’s serial number and many others. The access to the mentioned parameters is implemented in both MODBUSD and MQTT publisher applications. Apart from getting parameters, MODBUSD can also be used to set some system related parameters, for example, it can be used to change the value of the digital output.
| |
| − |
| |
| − | Some applications, like MQTT publisher or RMS, allow monitoring or administrating several routers at once. It is a very useful functionality when you want to change the same parameters on more than one router at once. RMS shares some similarities with SSH (Secure Shell) and one of RMS features is to allow SSH access to a remote router. You can access RMS by using your browser with a supplied username and a password at '''http://rms.teltonika.lt'''
| |
| − |
| |
| − | By sending SMS messages to the router the user can execute various commands like reboot, switch Wi-Fi on or off and many others. With each SMS the user needs to specify the router’s administrator password. This is done for authentication purposes. The list of commands that may be executed through SMS is limited. Full list of commands can be found at '''[[SMS Utilities|Services->SMS Utilities]]''' of the router’s WEB page. In theory SMS can be used to manage multiple routers as well by implementing '''[[SMS_Gateway#SMS_Forwarding_To_SMS_Configuration|SMS Forwarding to SMS]]''' to the mix.
| |
| − |
| |
| − | Another interesting router monitoring solution is '''[[SNMP]]''' (Simple Network Management Protocol). By not going into deep detail about this protocol, it is another manner to monitor router parameters. It allows the user to check the current operator, modem model and other router parameters. Compared to other applications and services, only SNMP has ability to inform the user about the occurrence of specific events (called traps) in the system. The main drawback of this protocol is that it does not allow the user to change anything.
| |
| − |
| |
| − | Apart from the services mentioned already, there is one service, which is used only for communication between the router and an Android type device (phones, etc.). It is called '''[[Monitoring via JSON-RPC|JSON-RPC]]''' and it allows the user to set or get various parameters of the system. JSON-RPC provides users with the possibility to execute the same commands as they would through SSH. To sum up, this approach opens up wide possibilities in communication between the router and an Android device.
| |
| − |
| |
| − | Each approach has its advantages and disadvantages. In some situations MQTT publisher works better than MODBUSD, while in others MODBUSD will be the better choice. The most versatile manner of system monitoring and administration is through SSH. SSH provides complete control of the router. The user can execute commands, write shell scripts and do many other things. In this case, the user only needs an application to connect to the router through SSH. The most popular application used in Windows type operating systems is called Putty. If one is trying to connect to the router from a UNIX type operating system, all that is needed is the hostname, username (in this case – root) and password.
| |
| − |
| |
| − | Sometimes the use of SSH is not necessary, so other more conservative services/applications are used. The complete list of applications and services that can be used for router administration and monitoring is given below. It can be seen that all applications, except MQTT publisher and SNMP, support both setting and getting of some system related parameters.
| |
| − |
| |
| − | {| class="wikitable"
| |
| − | |+
| |
| − | ! style="width: 200px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | APPLICATION
| |
| − | ! style="width: 200px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CAN OBTAIN PARAMETERS
| |
| − | ! style="width: 200px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | CAN SET PARAMETERS
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | MQTT publisher
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | no
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | MODBUS daemon
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | SSH
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | RMS
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | SMS
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | SNMP
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | no
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | JSON-RPC
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | ! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | TR-069
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | To summarize, RUT955 provides several solutions for remote router management. Each user can choose what solution suits them the best. If the required functionality is not supported by a particular service, the user can combine several applications, for example, use MQTT publisher along with SNMP. Finally, if a user has special needs, he can write shell scripts and execute them via SSH or use JSON-RPC.
| |
| | | | |
| | [[Category:{{{name}}} Manual]] | | [[Category:{{{name}}} Manual]] |
{{{name}}} supports multiple monitoring and administration possibilities.
Remote control options
The {{{name}}} router supports the following remote control capabilities:
| Remote control method |
Can get parameters |
Can set parameters |
| [[{{{name}}}_Remote_Monitoring_and_Administration#RMS|RMS]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#SSH_access|SSH]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#HTTP_access|SSH]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#SMS|SMS]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#JSON-RPS|JSON-RPC]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#VPN|VPN]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#SNMP|SNMP]] |
yes |
no |
| [[{{{name}}}_Remote_Monitoring_and_Administration#Modbus_TCP|Modbus TCP]] |
yes |
yes |
| [[{{{name}}}_Remote_Monitoring_and_Administration#MQTT|MQTT]] |
yes |
no |
| [[{{{name}}}_Remote_Monitoring_and_Administration#TR-069|TR-069]] |
yes |
yes |
RMS
Public IP
If you're using a SIM card that has a Public IP address (refer here for more info), you can reach the router via HTTP or SSH via its WAN IP address.
HTTP access
Remote HTTP access can be set up via the System → Administration → [[{{{name}}}_Administration#Access_Control|Access Control]] page.
SSH access
Remote SSH access can be set up via the System → Administration → [[{{{name}}}_Administration#Access_Control|Access Control]] page.
SMS
The router can be controlled via SMS messages using SMS utilities rules. SMS can be configured via the Services → SMS Utilities → [[{{{name}}}_Administration#Access_Control|SMS Rules]] page.
JSON-RPC
JSON-RPC access can be set up via the System → Administration → [[{{{name}}}_SMS_Utilities#Rule_Overview_and_editing|Access Control]] page.
VPN
SNMP
Modbus TCP
MQTT
TR-069
[[Category:{{{name}}} Manual]]
