OpenWISP 22.05 release

PS: demo site available!

I am extremely proud to announce the release of OpenWISP 22.05!

In the last 18 months we have done a terrific job at making the system more stable, fixing bugs, adding important features that are essential to manage production networks and improving documentation.

This release comes after many iterations and testing on real world production systems.


As usual, if you are using the official ansible role you can upgrade by following its upgrade instructions,


Complete list of changes

For the exhaustive list of changes, please refer to the change log of the modules you're interested in:

Many thanks to all the contributors and OpenWrt users who made this possible!

PS: demo site available!


I read a few of the getting started and and the quickstart page but I did not see any info on the minimum requirements for the openwrt device.

I am guessing that my tplink 4300 will not have enough space or memory to run this.

If I am reading this correctly that can be used for layer 3 roaming like ruckus has with there dataplane box. IE AP makes a tunnel back to central server and the wifi client's mac address would always show up as coming from server and not a AP allowing the client to roam and not re arp at every new AP.

Looks interesting, but what is this and what does it have to do with OpenWrt?

1 Like

@sml156 the application is designed to run on a server, the packages (see the bottom part of the post where it says "OpenWrt package" run on the device and require some hundred KB of space)

@zunder1990 the ways in which automatic provisioning of tunnels is used by OpenWISP users never ceases to surprise me, the automation is there, once the tunnel is up you can do whatever you want with it. I haven't tried what you suggest but sounds like it could be possible.

@phinn OpenWISP is a network management system which allows to automate the provisioning, configuration, monitoring and firmware upgrades of a fleet of OpenWrt devices from a central system. If you look for "openwisp" in the search box of this forum you will find plenty of posts mentioning it.


It's only a few small ipks on the device. The core does all the heavy lifting.


I am always interested to know if SQM can be configured, and more importantly,
monitored (backlog, flows, drops, ack_drops, etc) ?

1 Like

Hi David, it can be configured using the advanced mode JSON syntax.

Right now those metrics are not monitored because there hasn't been an expressed interest in it, my aim is to make the metric collection more flexible as the configuration system so that it will be easier to add custom metrics and charts in the system.

1 Like

ubnt's unms' rate limiters all use fq_codel underneath. hopefully soon, mikrotik's. I'd like to have an interface that got that more right...

Yea, nobody is keeping track of these key metrics! it's not lack of demand, IMHO, but of clue

1 Like

As more people will become aware and demand it, it will be implemented or we'll provide alternative paths to customize the monitoring module and track custom metrics.