flexiWAN Release 5.1.1

Release 5.1.1 includes:

  • flexiManage release 5.1.20

  • flexiEdge release 5.1.22

Release Notes:

flexiWAN is the world’s first open source SD-WAN & SASE with a modular and open architecture offered as a cloud service in a SaaS business model.

Version 5.1.1 was released on Dec, 2021. This version introduces new features such as Quality based routing, AI based network healing, Pure IPSec tunnels to peer devices, as well as scalability enhancements.

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:

  • Quality based routing

  • AI based network healing

  • Peering to cloud services (e.g. Cloud Security, Network aggregation GWs)

  • Performance and scale improvements

  • flexiEdgeUI - troubleshooting network connectivity

  • Other Bug fixes

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

API

Changes

Backward Compatible?

GET /devices

Add sort, order and filter query parameters

Yes

GET /devices

Add response type to query parameters to control the size of the response

Yes

GET /devices

Add number of pending notifications to the response

Yes

DELETE /devices

Allow to delete multiple devices matching a filter

Yes

GET /devices interfaces

Add an indication if rate limited due to public IP/port changes

Yes

PUT /devices/{id}

Fix type for deviceSpecifficRulesEnabled -> deviceSpecificRulesEnabled

No

GET /devices/{id}/tunnels

New API to get specific device tunnels

Yes

GET /tunnels

Add sort, order and filter query parameters

Yes

ALL /tunnels

Allow device/interface B to be null in case of peer connection

Yes

ALL /tunnels

Add N/A as tunnel status in case devices are not connected

Yes

GET /tunnels /devices/{id}/tunnels

Add tunnelStatus (Connected/Not Connected/Pending), isPending, pendingReason to the tunnel response

Yes

GET /jobs

Add filter parameters

Yes

DELETE /jobs

Allow to delete by filter parameters

Yes

GET/POST /peers

New API to get and add peer connections to the system

Yes

PUT/DELETE /peers/{id}

New API to modify and remove peer connections

Yes

GET /notifications

Add sort, order and filter query parameters

Yes

GET /notifications

Add device ID to notification response

Yes

DELETE /notifications

Allow to delete multiple notifications matching a filter

Yes

ALL /mlpolicies

Add link-quality to actions for path selection Quality Based Routing

Yes

Known Issues

List of Known Issues

Title

Description

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

Tunnel loss and RTT during heavy load

During heavy traffic load, loss and RTT calculation might represent biased values

On unstable/slow connections some jobs may be presented as failed on timed out although succeeded

In most of the cases, the jobs have succeeded and the system recovers itself by re-syncing the configuration

Switching WiFi from 2.4Ghz to 5Ghz doesn’t restart DHCP server

To restart the DHCP server for the WiFi interface, stop and start the flexiEdge router

Inbound WAN ICMP with small identifier is dropped

Inbound WAN ICMP with Identifier smaller or equal to 1024 may be dropped

Peer connections on multiple WAN interface

When using peer connection via multiple WAN interfaces, the source IP might be of another WAN