0
edits
Changes
Template:Networking rutxxx configuration example JSON RPC commands (view source)
Revision as of 11:21, 25 January 2021
, 11:21, 25 January 2021no edit summary
If the commands found in the guide above did not suffice your needs, this section provides a list of additional ones. The commands presented in this section will be for both Linux and Windows operating systems. They should be used as syntax examples for your own purposes.
If the commands found in the guide above did not suffice your needs, this section provides a list of additional ones. The commands presented in this section will be for both Linux and Windows operating systems. They should be used as syntax examples for your own purposes.
<br><br>
===WiFi clients list===
===WiFi clients list===
----
----
To obtain these values, the Linux '''iwinfo''' command and '''assoclist''' parameter (red) are used. Highlighted in green are the devices connected to the router via WiFi as identified by their MAC addresses. The response information about the connection with the device, such as signal strength, noise, time of inactivity (idle time), rx, tx rate, etc., is highlighted in blue.
To obtain these values, the Linux '''iwinfo''' command and '''assoclist''' parameter (red) are used. Highlighted in green are the devices connected to the router via WiFi as identified by their MAC addresses. The response information about the connection with the device, such as signal strength, noise, time of inactivity (idle time), rx, tx rate, etc., is highlighted in blue.
<br><br><br><br>
===WiFi information===
===WiFi information===
----
----
As with the clients list command described above, to obtain this information the Linux '''iwinfo''' command is used, but this time with the '''info''' parameter (red). The relevant information, such as WiFi SSID, WiFi MAC address, WiFi channel, Encryption type, etc., is highlighted in blue
As with the clients list command described above, to obtain this information the Linux '''iwinfo''' command is used, but this time with the '''info''' parameter (red). The relevant information, such as WiFi SSID, WiFi MAC address, WiFi channel, Encryption type, etc., is highlighted in blue
<br><br><br><br>
===Manufacturing information===
===Manufacturing information===
----
----
* '''batch''' - returns the router's Batch number
* '''batch''' - returns the router's Batch number
* '''hwver''' - returns the router's Hardware Revision number
* '''hwver''' - returns the router's Hardware Revision number
* '''simpin''' - returns the router's SIM card's PIN (as it is specified in the '''[[Mobile]]''' section)
* '''simpin''' - returns the router's SIM card's PIN (as it is specified in the '''[[{{{name}}}_Mobile]]''' section)
* '''blver''' - returns the router's Bootloader version
* '''blver''' - returns the router's Bootloader version
<br><br><br>
===GPS Data===
===GPS Data===
----
----
}
}
'''Linux:'''
'''Linux:'''
curl -d "{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"call\",\"params\":[\"5363304b3ed4ee0806f101295fc52e93\",\"file\",\"exec\",{\"command\":\"gpsctl\",\"params\":[\"-ix\"]}]}" http://<span style=color:black>192.168.1.1</span>/ubus
Response:
{"jsonrpc":"2.0","id":1,"result":[0,{"code":0,"stdout":"<span style=color:blue>-23.612625\n-46.626355\</span>n"}]}
The blue part in the code are the Latitude and Longitude.
<br><br><br>
===Firmware number===
===Firmware number===
----
----
{"jsonrpc":"2.0","id":1,"result":[0,{"data":"<span style=color:blue>RUT9XX_R_00.05.00.5</span>\n"}]}
{"jsonrpc":"2.0","id":1,"result":[0,{"data":"<span style=color:blue>RUT9XX_R_00.05.00.5</span>\n"}]}
This command ('''file''', '''read''', highlighted in red) is an alternative to the Linux '''cat''' command we see used in the '''[[Monitoring_via_JSON-RPC#Getting_router_parameters|Getting router paramaters]]''' section of this guide. All you need is to specify the path (in this case '''/etc/version''', highlighted in red) to the file that you wish to read.
This command ('''file''', '''read''', highlighted in red) is an alternative to the Linux '''cat''' command. All you need is to specify the path (in this case '''/etc/version''', highlighted in red) to the file that you wish to read.
<br><br><br><br>
===Reboot===
===Reboot===
----
----
The success response for this command is an empty message. If the response contains no data, the command was executed successfully.
The success response for this command is an empty message. If the response contains no data, the command was executed successfully.
<br><br><br><br>
===Set SIM card information===
===Set SIM card information===
----
----
{"jsonrpc":"2.0","id":1,"result":[<span style=color:blue>0</span>]}
{"jsonrpc":"2.0","id":1,"result":[<span style=color:blue>0</span>]}
The command used is ''uci set'' (highlighted in red). The config file name is '''simcard''', section '''sim1''', options '''mtu''' and '''service''' (configs, sections and options highlighted in orange). The response shown above is a positive response, but don't forget to execute ''uci commit'' and ''luci-reload'' afterwards or else your changes will not take effect. The usage of ''uci commit'' and ''luci-reload'' commands is described '''[[Monitoring_via_JSON-RPC#Setting_router_parameters|here]]''' (for Windows) and '''[[Monitoring_via_JSON-RPC#Setting_router_parameters_2|here]]''' (for Linux).
The command used is ''uci set'' (highlighted in red). The config file name is '''simcard''', section '''sim1''', options '''mtu''' and '''service''' (configs, sections and options highlighted in orange). The response shown above is a positive response, but don't forget to execute ''uci commit'' and ''luci-reload'' afterwards or else your changes will not take effect.
[[Category:{{{name}}} Configuration Examples]]
[[Category:{{{name}}} Configuration Examples]]
