5 uBus is the interconnect system used by most service running on a _LEDE_ setup.
6 Service can connect to the bus and provide methods that can be called by other services or clients.
8 There is a CLI that can be used to communicate with services on the bus.
12 Usage: ubus [<options>] <command> [arguments...]
14 -s <socket>: Set the unix domain socket to connect to
15 -t <timeout>: Set the timeout (in seconds) for a command to complete
16 -S: Use simplified output (for scripts)
17 -v: More verbose output
20 - list [<path>] List objects
21 - call <path> <method> [<message>] Call an object method
22 - listen [<path>...] Listen for events
23 - send <type> [<message>] Send an event
24 - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
27 To find out which services are currently running on the bus simply use the list command. This will show a complete list.
30 root@lede:/# ubus list
36 network.interface.loopback
38 network.interface.wan6
44 To find out which methods a specific service provides also use the list command but add a few more parameters to see a complete list
47 root@OpenWrt:/# ubus -v list system
52 "watchdog":{"frequency":"Integer","timeout":"Integer","stop":"Boolean"}
53 "signal":{"pid":"Integer","signum":"Integer"}
56 You can now call a remote method and receive a reply. A reply may be a simple integer return code or a more complete reply. Internally the bus uses a blob format, the CLI conveniently converts this to JSON.
59 root@lede:/# ubus call system board
63 "system": "MIPS Malta",
65 "distribution": "LEDE",
68 "codename": "designated_driver",
69 "target": "malta\/le",
70 "description": "LEDE Designated Driver 3"
75 You can call a method and pass it some parameters by simply appending a JSON structure to the CLI command.
77 root@lede:/# ubus call system signal '{ "pid": 123, "signum": 9 }'