2020-03-27 20:40:02 +00:00
|
|
|
|
Download packages for CAP upgrade from CAPsMAN
|
|
|
|
|
|
=============================================
|
|
|
|
|
|
|
2023-01-10 13:45:27 +00:00
|
|
|
|
[⬅️ Go back to main README](../README.md)
|
2020-03-27 20:40:02 +00:00
|
|
|
|
|
2022-02-12 12:05:56 +00:00
|
|
|
|
> ℹ️ **Info**: This script can not be used on its own but requires the base
|
2022-02-11 22:34:39 +00:00
|
|
|
|
> installation. See [main README](../README.md) for details.
|
2021-05-03 13:07:50 +00:00
|
|
|
|
|
2020-03-27 20:40:02 +00:00
|
|
|
|
Description
|
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
|
|
CAPsMAN can upgrate CAP devices. If CAPsMAN device and CAP device(s) are
|
|
|
|
|
|
differnet architecture you need to store packages for CAP device's
|
|
|
|
|
|
architecture on local storage.
|
|
|
|
|
|
|
|
|
|
|
|
This script automatically downloads these packages.
|
|
|
|
|
|
|
|
|
|
|
|
Requirements and installation
|
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
|
2023-12-05 09:59:23 +00:00
|
|
|
|
Make sure you have the `package-path` set in your CAPsMAN configuration,
|
|
|
|
|
|
as that is where packages are downloaded to and where the system expects
|
|
|
|
|
|
them.
|
|
|
|
|
|
|
|
|
|
|
|
Then just install the script on CAPsMAN device.
|
2024-03-05 10:06:53 +00:00
|
|
|
|
Depending on whether you use `wifi` package (`/interface/wifi`) or legacy
|
|
|
|
|
|
wifi with CAPsMAN (`/caps-man`) you need to install a different script.
|
2020-03-27 20:40:02 +00:00
|
|
|
|
|
2024-03-05 10:06:53 +00:00
|
|
|
|
For `wifi`:
|
2023-11-14 09:26:06 +00:00
|
|
|
|
|
|
|
|
|
|
$ScriptInstallUpdate capsman-download-packages.wifi;
|
|
|
|
|
|
|
2023-08-07 10:18:47 +00:00
|
|
|
|
For legacy CAPsMAN:
|
|
|
|
|
|
|
|
|
|
|
|
$ScriptInstallUpdate capsman-download-packages.capsman;
|
|
|
|
|
|
|
2024-03-05 10:06:53 +00:00
|
|
|
|
Optionally add a scheduler to run after startup. For `wifi`:
|
2023-11-14 09:26:06 +00:00
|
|
|
|
|
|
|
|
|
|
/system/scheduler/add name=capsman-download-packages on-event="/system/script/run capsman-download-packages.wifi;" start-time=startup;
|
|
|
|
|
|
|
2023-08-07 10:18:47 +00:00
|
|
|
|
For legacy CAPsMAN:
|
|
|
|
|
|
|
|
|
|
|
|
/system/scheduler/add name=capsman-download-packages on-event="/system/script/run capsman-download-packages.capsman;" start-time=startup;
|
2020-03-27 20:40:02 +00:00
|
|
|
|
|
2022-03-22 21:33:46 +00:00
|
|
|
|
Packages available in local storage in older version are downloaded
|
2023-08-07 14:44:26 +00:00
|
|
|
|
unconditionally.
|
|
|
|
|
|
|
2023-12-20 11:11:12 +00:00
|
|
|
|
If no packages are found the script downloads a default set of packages:
|
2023-11-14 09:26:06 +00:00
|
|
|
|
|
2023-12-20 11:29:24 +00:00
|
|
|
|
* `wifi`: `routeros` and `wifi-qcom` for *arm* and *arm64*, `wifi-qcom-ac` for *arm*
|
2023-12-20 11:11:12 +00:00
|
|
|
|
* legacy CAPsMAN: `routeros` and `wireless` for *arm* and *mipsbe*
|
2020-03-27 20:40:02 +00:00
|
|
|
|
|
2023-11-14 13:04:30 +00:00
|
|
|
|
> ℹ️ **Info**: If you have packages in the directory and things go wrong for
|
|
|
|
|
|
> what ever unknown reason: Remove **all** packages and start over.
|
|
|
|
|
|
|
2020-03-27 20:40:02 +00:00
|
|
|
|
Usage and invocation
|
|
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
|
|
|
|
Run the script manually:
|
|
|
|
|
|
|
2023-11-14 09:26:06 +00:00
|
|
|
|
/system/script/run capsman-download-packages.wifi;
|
2020-03-27 20:40:02 +00:00
|
|
|
|
|
|
|
|
|
|
... or from scheduler.
|
|
|
|
|
|
|
|
|
|
|
|
After package download all out-of-date CAP devices are upgraded automatically.
|
|
|
|
|
|
For a rolling upgrade install extra script
|
|
|
|
|
|
[capsman-rolling-upgrade](capsman-rolling-upgrade.md).
|
|
|
|
|
|
|
|
|
|
|
|
See also
|
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
|
|
* [Run rolling CAP upgrades from CAPsMAN](capsman-rolling-upgrade.md)
|
|
|
|
|
|
|
|
|
|
|
|
---
|
2023-01-10 13:45:27 +00:00
|
|
|
|
[⬅️ Go back to main README](../README.md)
|
|
|
|
|
|
[⬆️ Go back to top](#top)
|
