The Network Manager listens for commands on this control object
Commands sent to the /pps/services/networking/control object are of the form:
msg::command_string\nid::ID_number\ndat:json:{JSON_data}
Responses always reflect the command_string and ID_number that were sent in the message, along with any errors:
res::command_string\nid::ID_number\ndat:json:{JSON_data}\nerr::error_description
The following table shows the command format:
msg:: | id:: | dat:json: |
---|---|---|
net_connected | Number | ["interface"{"parameter":"value", ...}] (see below) |
net_disconnected | Number | interface |
net_disconnecting | Number | ["interface" | "interface",{"deadline":milliseconds}] |
net_dyn | Number | ["interface",{"gateway":"addr","nameservers":["addr", "addr"],"searchdomains":"domain"}] |
Parameter | Description |
---|---|
ftpproxy | IPv4 FTP proxy. |
ftpproxy6 | IPv6 FTP proxy. |
htpproxy | IPv4 HTTP proxy. |
htpproxy6 | IPv6 HTTP proxy. |
httpsroxy | IPv4 HTTPS proxy. |
httpsproxy6 | IPv6 HTTPS proxy. |
manual | Possible values:
|
manual6 | Possible values:
|
type | The type of network interface. Possible values:
|
You can send ping or traceroute networking commands in the dat:: field. Reply will contain a simple err:: attribute on error, empty on success.
msg::cmd id::5 dat::ping -n -c4 10.42.116.1