flexiWAN Release 3.3.2

Release 3.3.2 includes:

  • flexiManage release 3.3.5

  • flexiEdge release 3.3.9

Release Notes:

flexiWAN is the world’s first open source SD-WAN with a modular and open architecture.

Version 3.3.2 was updated on Apr 20th, 2021. This version introduces Single-Side Symmetric NAT traversal, ability to edit MTU on interfaces, LTE optimization and better modem support and bug fixes.

There are three options for hosting flexiManage, each relevant for companies with a different set of requirements. All of these options come with support services.

  • SaaS model in a shared environment - flexiManage hosted by flexiWAN

  • Dedicated environment - a dedicated, white-label deployment just for you

  • Self-hosting - self-hosting of flexiManage is typically best for large service providers

More information about these 3 options and in order to understand which of these is best for you, please read this blog post.

Pricing information can be found here.

Please contact us for further questions.

New in this release:

  • Single-Side Symmetric NAT traversal

  • MTU configuration

  • LTE improvements

  • Bug fixes and optimizations

Supported and Planned Features

The list of supported and planned features description can be found in the Feature Overview page

Please send us your feature needs and prioritization.

REST API changes in this release

List of REST API Changes



Backward Compatible?

ALL /devices/{id} - Interfaces

Add MTU configuration per interface


ALL /devices/{id} - Interfaces

Add useFixedPublicPort to instruct tunnels to this interface to use fixed port of 4789


GET /devices/{id}/logs

Add filter for flexiEdge UI and Hostapd logs


Known Issues

List of Known Issues



UI hangs on Redis failure

When redis fails, UI might hang and not complete the request

During login, the username email is case sensitive

The email used in account creation and login is case sensitive

Slow websocket connection during heavy load

During heavy traffic load, device connection to flexiManage may be impacted

On unstable/slow connections some jobs may fail on timeout

In most cases the system recover itself by re-syncing the configuration