Upgrade to 9.0 (step by step tutorial)
To upgrade Wanguard and Wansight to version 9.0, please follow these steps in the given order. Traffic monitoring and DDoS protection pause while the software components are stopped, so schedule the upgrade within a maintenance window.
- Upgrade unsupported operating systems
- If you're running CentOS 8, RHEL 8, Rocky 8 or AlmaLinux 8, upgrade to RHEL 9, Rocky 9 or AlmaLinux 9. These are no longer supported: CentOS 8 has reached End Of Life, and support for RHEL 8 and its derivatives was dropped in version 9.0.
- Debian 8, Debian 9, Debian 10, Ubuntu 16 and Ubuntu 18 have also reached End Of Life. Upgrade to at least Debian 11 or Ubuntu 20.
- If upgrading the distribution is no longer possible, follow the Console transfer steps to copy the data to a new system.
- Stop all software components
- Log in to the web interface, go to Configuration » Components, stop all components, then log out.
- Stop the WANsupervisor service on all servers
[root@localhost:~]# systemctl stop WANsupervisor
- Back up the database on the Console server
- The backup is written to /root as wanguard_db_backup_*.sql. Keep it until you have confirmed that the upgrade completed successfully.
- On very large databases, backup_quick is considerably faster: it saves the configuration together with the most important operational data.
- Downgrading is not supported: to roll back, reinstall the previous software version and restore this backup with WANmaintenance restore_db.
[root@localhost:~]# /opt/andrisoft/bin/WANmaintenance backup_db - Update the Capture Engine (if applicable)
- If you’re using PF_RING, update it to version 9.2.
- If you're using DPDK, update it to version 25.11.
- If you're using Netmap, update it to a Git version from around June 2026.
- Upgrade the software packages, starting with the Console server
- Do not upgrade the Linux distribution at this point (e.g., from Ubuntu 24 to 26).
- The upgrade might take tens of minutes if the database is very large (due to Unlimited values in Data Retention). Do not reboot the server.
- Ensure you upgrade the software on all servers, not just the Console server. It’s crucial to run the same software version everywhere.
On RHEL/Rocky/AlmaLinux 9, run:[root@localhost:~]# rpm -Uvh https://packages.andrisoft.com/rhel9/wanrepo-9.0-0.noarch.rpmOn RHEL/Rocky/AlmaLinux 10, run:
[root@localhost:~]# yum upgrade[root@localhost:~]# rpm -Uvh https://packages.andrisoft.com/rhel10/wanrepo-9.0-0.noarch.rpmOn Debian 11, run:
[root@localhost:~]# yum upgrade[root@localhost:~]# echo "deb [signed-by=/usr/share/keyrings/andrisoft-keyring.gpg] https://packages.andrisoft.com bullseye main" > /etc/apt/sources.list.d/andrisoft.listOn Debian 12, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb [signed-by=/usr/share/keyrings/andrisoft-keyring.gpg] https://packages.andrisoft.com bookworm main" > /etc/apt/sources.list.d/andrisoft.listOn Debian 13, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb [signed-by=/usr/share/keyrings/andrisoft-keyring.gpg] https://packages.andrisoft.com trixie main" > /etc/apt/sources.list.d/andrisoft.listOn Ubuntu 20, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb https://packages.andrisoft.com focal main" > /etc/apt/sources.list.d/andrisoft.listOn Ubuntu 22, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb https://packages.andrisoft.com jammy main" > /etc/apt/sources.list.d/andrisoft.listOn Ubuntu 24, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb https://packages.andrisoft.com noble main" > /etc/apt/sources.list.d/andrisoft.listOn Ubuntu 26, run:
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade[root@localhost:~]# echo "deb https://packages.andrisoft.com resolute main" > /etc/apt/sources.list.d/andrisoft.list
[root@localhost:~]# apt update
[root@localhost:~]# apt dist-upgrade - Start the WANsupervisor service on all servers
[root@localhost:~]# systemctl start WANsupervisor
- Reset the built-in dashboards (optional)
- The built-in dashboards were redesigned in 9.0. To adopt the new layouts, execute the command below on the Console server. Customizations made to the built-in dashboards are lost; dashboards created by users are not affected.
[root@localhost:~]# /opt/andrisoft/bin/WANmaintenance restore_dashboards - Start all software components
- Log in to the web interface, go to Configuration » Components, and start all components.
- Set up ClickHouse (optional)
- InfluxDB remains the fastest graph storage engine for most installations, so you can skip this step. A ClickHouse server is required only for the interactive Flow Graphs (enabled in the Flow Collector window of the Flow Sensor configuration), for profiling rules, and for very high cardinality graph data.
- Follow the ClickHouse Installation steps in the General Settings » Graphs & Storage chapter of the User Guide, then press [Initialize DB] in the ClickHouse Connector.
- Setting ClickHouse as Graph Storage Engine 2 writes new graph data to both backends in parallel, so ClickHouse builds up history from that point on. Data already stored in InfluxDB is not copied over.
- Review the relevant release note(s)
- Check for additional details or changes introduced in this release.
Your feedback is highly appreciated! If you encounter any issues, please contact
AuthorAndrisoft Team
Date Created4 June 2026
Date Updated30 July 2026
Views607

