Changes

  {"rate":<span style=color:blue>72200</span>,"mcs":<span style=color:blue>7</span>,"40mhz":<span style=color:blue>false</span>,"short_gi":<span style=color:blue>true</span>}}]}]}

  {"rate":<span style=color:blue>72200</span>,"mcs":<span style=color:blue>7</span>,"40mhz":<span style=color:blue>false</span>,"short_gi":<span style=color:blue>true</span>}}]}]}

To obtain these values, Linux '''iwinfo''' command and '''assoclist''' parameter (red) is used. Highlighted in green are the devices connected to the router via Wi-Fi 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 Wi-Fi 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.  

===Wi-Fi information===

===Wi-Fi information===

  {"enabled":<span style=color:blue>false</span>},"hwmodes":["<span style=color:blue>b</span>","<span style=color:blue>g</span>","<span style=color:blue>n</span>"],"hardware":{"name":"<span style=color:blue>Generic MAC80211</span>"}}]}

  {"enabled":<span style=color:blue>false</span>},"hwmodes":["<span style=color:blue>b</span>","<span style=color:blue>g</span>","<span style=color:blue>n</span>"],"hardware":{"name":"<span style=color:blue>Generic MAC80211</span>"}}]}

As with the clients list command described above, to obtain this information Linux '''iwinfo''' command is used, this time with the '''info''' parameter (red). The relevant information, such as Wi-Fi SSID, Wi-Fi MAC address, Wi-Fi 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 Wi-Fi SSID, Wi-Fi MAC address, Wi-Fi channel, Encryption type, etc., is highlighted in blue

===Manufacturing information===

===Manufacturing information===

  {"jsonrpc":"2.0","id":1,"result":[0,{"code":0,"stdout":"<span style=color:blue>RUT950HG12C0</span>\n<span style=color:blue>1367435694</span>\n<span style=color:blue>001e4216d666</span>\n"}]}

  {"jsonrpc":"2.0","id":1,"result":[0,{"code":0,"stdout":"<span style=color:blue>RUT950HG12C0</span>\n<span style=color:blue>1367435694</span>\n<span style=color:blue>001e4216d666</span>\n"}]}

To get manufacturing information the '''mnf_info''' (highlighted in red) command is used. In this case a query was sent asking for the device's Product Code (name), Serial Number (sn) and MAC Address (mac) (highlighted in red in the query, returned values highlighted in blue). Using '''mnf_info''' this way, you can "ask" the router for any type of manufacturing info. Here is the list of possible mnf_info parameters:

To obtain the manufacturing information the '''mnf_info''' (highlighted in red) command is used. In this case a query was sent asking for the device's Product Code (name), Serial Number (sn) and MAC Address (mac) (highlighted in red in the query; returned values highlighted in blue). Using ''mnf_info'', you can "ask" the router for any type of manufacturing information. Here is the list of possible ''mnf_info'' parameters:

* '''mac''' - returns the router's LAN MAC address

* '''mac''' - returns the router's LAN MAC address

===Set SIM card information===

===Set SIM card information===

----

----

In this last example we'll try to change the mobile connection's MTU and Service mode.  

In this last example we'll try to change the mobile connection's MTU and Service mode values.  

'''Windows:'''

'''Windows:'''

  {"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 and options highlighted in orange). The response shown above is a positive response, but don't forget to '''uci commit''' and '''luci-reload''' afterwards or else your changes will not take place. uci commit and luci reload commands are 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. 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).