OpenWISP 22.05 release

[nemesis]

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.

Highlights

• Added support for remotely executing shell commands on devices
• Added automatic provisioning of Subnets and IPs
• Added support for WireGuard and VXLAN tunnels
• Added required templates
• Most modules have a fully featured REST API
• The web UI theme has been modernized with the aim to improve user experience
• OpenWISP Monitoring has been added to ansible-openwisp2 and docker-openwisp
• OpenWISP RADIUS has been added to ansible-openwisp2 and docker-openwisp
• OpenWISP WIFi Login Pages 1.0.0 has been released and a dedicated ansible role has been created to allow deploying it
• There have been significant advancements and improvements in Docker OpenWISP

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

PLEASE MAKE SURE TO BACK UP YOUR CURRENT INSTANCE BEFORE UPGRADING.

Complete list of changes

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

• Ansible OpenWISP 2
• OpenWISP Controller
• openwisp-config OpenWrt package
• OpenWISP IPAM
• OpenWISP Monitoring
• openwisp-monitoring OpenWrt package
• OpenWISP Firmware Upgrader
• OpenWISP Network Topology
• OpenWISP RADIUS
• OpenWISP WiFi Login Pages
• Ansible Wireguard OpenWISP
• Ansible OpenWISP WiFi Login Pages

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

[sml156]

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.

[zunder1990]

@nemesis

Added support for WireGuard and VXLAN tunnels

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.

[phinn]

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

[nemesis]

@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.

[mfoxworthy]

@sml156

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.

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