This project intends to simplify the sysupgrade process of devices running OpenWrt or distributions based on the former like LibreMesh. The provided tools here offer an easy way to reflash the router with a new version or package upgrades, without the need of opkg installed.

Additionally it offers an API (covered below) to request custom images with any selection of packages pre-installed, allowing to create firmware images without the need of setting up a build environment, even from mobile devices.

Add a view to the Luci system tab called "Attended Sysupgrade". Offers a button to search for updates and if found, to flash the image created by the update server.

Dependencies:

• rpcd-mod-rpcsys Used to read list of installed packages and trigger sysupgrade on the target.
• uhttpd-mod-ubus Communication between the Browser and the Router
• cgi-io Upload image from Browser to Router

Add CLI to perform sysupgrades.

Dependencies:

• rpcd-mod-rpcsys Used to read list of installed packages and trigger sysupgrade on the target.
• usteam-ssl and ca-certificates Securely communicate and download firmware from server via https

• https://as-test.stephen304.com/chef dev version
• https://chef.libremesh.org

The server listens to update and image requests and images are automatically generated if the requests was valid. This is done by automatically setting up OpenWrt ImageBuilders and cache images in a database. This allows to quickly respond to requests without rebuilding exiting images again.

• stephen304 dev version
• planetexpress

You can set this server in /etc/config/attendedsysupgrade after installation of a client.

Sends information about the device to the server to see if a new distribution version or package upgrades are available. An upgrade check could look like this:

Most information can be retrieved via ubus call system board. Missing information can be gathered via the rpcd-mod-rpcsys package. packages contains all user installed packages plus version. Packages installed as an dependence are excluded as they've been automatically and dependencies may change between versions.

It's also possible to check for a new version without sending packages by removing packages from the request.

The server validates the request. Below is a possible response for a new version:

See other status codes

An version upgrade does not ignore package upgrades for the following reason. Between versions it possible that package names may change, packages are dropped or merged. The response contains all packages included changed ones.

The upgrade check response should be shown to the user in a readable way.

Once the user decides to perform the sysupgrade a new request is send to the server called upgrade request.

The upgrade request is nearly the same as the upgrade check before, except only containing package names without version and adding board and possibly model. While the server builds the requested image the clients keeps polling the server sending a request_hash via GET to the server.

If the request_hash was retrieved the client should switch to GET requests with the hash to save the server from validating the request again.

api/upgrade-request/<request_hash

See other status codes

It's also possible to request to build an image. The request is nearly the same as for upgrade-request. The response only contains a link to the created files or upgrade-request parameters if available.

An additional parameter is the defaults parameter which allows to set the content of /etc/uci-defaults/99-server-defaults within the image. This allows to set custom options for the resulting image. To distinguish between custom images the name will contain a hash of the requested defaults value and is stored in a different place, only visible if the full hash (32bit) is known.

This is a special case for clients that do not necessary require a sysupgrade compatible image. An example is the LibreMesh Chef firmware builder.

The client should check the status code:

It's also possible to receive information about build images or package versions, available devices and more. All responses are in JSON format.

• /api/image/<image_hash> Get information about an image. This contains various information stored about the image.

• /api/manifest/<manifest_hash> Get packages and versions of a manifest. The manifest contains all installed packages of an image. The manifest_hash can be received by the api call /api/image.

• /api/distros Get all supported distros with latest version and a short description if available.

• /api/versions[?distro=<distribution>] Get all supported versions with short description (of a singele distribution if given).

• /api/models?distro=&version=&model_search=<search string> Get all supported devices of distro/version that contain the model_search string

• /api/packages_image?distro=&version=&target=&subtarget=&profile= Get all default packages installed on an image