31,703
edits
Changes
Draft:Monitoring via JSON-RPC (view source)
Revision as of 13:53, 18 June 2018
, 13:53, 18 June 2018→Getting router parameters
Look for '''stdout'''; what follows after is the direct response to our query: ''{"jsonrpc":"2.0","id":1,"result":[0,{"code":0,"stdout":"<span style="color:green">'''-59'''</span>\n"}]}''. This tells us that the router's current signal strength is <span style="color:green">'''-59 dBm'''</span>.
Look for '''stdout'''; what follows after is the direct response to our query: ''{"jsonrpc":"2.0","id":1,"result":[0,{"code":0,"stdout":"<span style="color:green">'''-59'''</span>\n"}]}''. This tells us that the router's current signal strength is <span style="color:green">'''-59 dBm'''</span>.
----
You can issue many SSH commands in a similar manner. For example, if you wish to check the ''network'' config file, the SSH command to do so would be '''cat /etc/config/network''', which, translated to JSON-RPC, would be:
You can issue many SSH commands in a similar manner. For example, if you wish to check the ''network'' config file, the SSH command to do so would be '''cat /etc/config/network''', which, translated to JSON-RPC, would be:
