Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-user:installation:attended.sysupgrade [2022/08/13 01:14] – [From LuCI web page] richb-hanover | docs:guide-user:installation:attended.sysupgrade [2023/11/20 22:29] – Add explanations and examples of auc command line options efahlgren | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Upgrade using Attended Sysupgrade ====== | ====== Upgrade using Attended Sysupgrade ====== | ||
| - | The Attended | + | The Attended |
| - | This dramatically simplifies the upgrade | + | new firmware while preserving the packages and settings. |
| + | This dramatically simplifies the upgrade | ||
| + | a short wait lets you retrieve and install | ||
| - | ASU allows | + | ASU eliminates the need to make a list of packages |
| - | ASU relies on significant updates over the last several years to the ImageBuilder. | + | or fuss with opkg just to upgrade your firmware. |
| - | There is both a LuCI (web page interface) and command-line package for Attended Sysupgrade. | + | Because it is initiated by a person who waits until it's complete, |
| + | it's called “attended” sysupgrade. | ||
| + | You can see Attended Sysupgrade | ||
| + | at: https:// | ||
| + | There is both a LuCI (web page interface) and command-line package for Attended Sysupgrade. | ||
| ===== From LuCI web page ===== | ===== From LuCI web page ===== | ||
| - | The package | + | The [[packages: |
| + | package | ||
| + | It requests a new firmware image built with the current set of packages, | ||
| + | waits until it' | ||
| + | If "Keep Configuration" | ||
| - | To install '' | + | To install '' |
| + | update the package list, and search for // | ||
| + | Install it in the usual manner. | ||
| - | To upgrade your firmware, go to **System -> Atttended Sysupgrade**. | + | To upgrade your firmware: |
| - | * Click **Search for sysupgrade** You will see choices for the firmware | + | |
| + | * Go to **System -> Atttended Sysupgrade**. You'll see the main Attended Sysupgrade window | ||
| + | | ||
| * Select the desired version from the dropdown, and click **Request Sysupgrade** | * Select the desired version from the dropdown, and click **Request Sysupgrade** | ||
| - | * There may be a wait as the server builds a custom image including | + | * There may be a wait as the server builds a custom image that includes |
| - | * You will see a window describing the new firmware: | + | * When that completes, you will see a window describing the new firmware: |
| * If you wish to keep settings, check the box. Otherwise, settings will be erased and set to factory default. | * If you wish to keep settings, check the box. Otherwise, settings will be erased and set to factory default. | ||
| * Click **Install Sysupgrade** and the router will download the new image, flash it, and reboot. | * Click **Install Sysupgrade** and the router will download the new image, flash it, and reboot. | ||
| + | * You'll be running the new firmware, with all your packages and settings intact. | ||
| + | {{: | ||
| + | |||
| + | {{: | ||
| + | |||
| + | {{: | ||
| + | choose Keep Settings (or not) and click **Install Sysupgrade** | ||
| ===== From the CLI ===== | ===== From the CLI ===== | ||
| - | The [[https:// | + | The [[packages:pkgdata:auc]] package performs |
| + | the same process as the '' | ||
| - | To install the '' | + | To install the '' |
| + | in the web intrface, go to **System -> Software**, update the package list, | ||
| + | and search for //auc//. Install it in the usual manner. | ||
| - | Enter '' | + | To upgrade your device firmware, first **Make A Backup** //(see first step above)// |
| + | Then enter '' | ||
| The default is to get the next version. | The default is to get the next version. | ||
| You can specify the following options on the command line. | You can specify the following options on the command line. | ||
| Line 53: | Line 78: | ||
| </ | </ | ||
| + | To use '' | ||
| + | <code bash> | ||
| + | $ auc -c | ||
| + | auc/0.3.2-1 | ||
| + | Server: | ||
| + | Running: | ||
| + | Available: SNAPSHOT r24414-255d5c9bf8 | ||
| + | Requesting package lists... | ||
| + | | ||
| + | | ||
| + | </ | ||
| + | |||
| + | By default, '' | ||
| + | |||
| + | This example detects that 23.05.2 is installed, and shows information related to downgrading to 22.03.4. | ||
| + | As indicated by the warning, this is probably not a good idea as the jump in versions is "too far", but you *can* use '' | ||
| + | <code bash> | ||
| + | $ auc -c -b 22.03 -B 22.03.4 | ||
| + | auc/0.3.2-1 | ||
| + | Server: | ||
| + | Running: | ||
| + | Available: 22.03.4 r20123-38ccc47687 | ||
| + | WARNING: Downgrade to older branch may not work as expected! | ||
| + | Requesting package lists... | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | ... | ||
| + | </ | ||
| + | |||
| + | ===== ASU Server ===== | ||
| + | |||
| + | The ASU Server listens for image requests and, if valid, automatically generates them. | ||
| + | It coordinates several OpenWrt ImageBuilders and caches the resulting images in a Redis database. | ||
| + | If an image is cached, the server can provide it immediately without rebuilding. | ||
| + | |||
| + | The ASU Server provides an API to request custom firmware images with | ||
| + | any selection of packages pre-installed. | ||
| + | This avoids the need to set up a build environment, | ||
| + | to create a custom firmware image even using a mobile device. | ||
| + | |||
| + | * The current production ASU Server is '' | ||
| + | * There is an development server at '' | ||
| + | * < | ||
| + | * The [[https:// | ||
| + | |||
| + | ASU relies on significant updates over the last several years to the ImageBuilder, | ||
| + | [[https:// | ||