flexiWAN Release 5.2.1¶
Release 5.2.1 includes:
flexiManage release 5.2.10
flexiEdge release 5.2.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.2.1 was released on Apr, 2022. This version introduces new features such as PPPoE, Remote Worker Application, Monitoring Enhancements, Advanced Tunnels Configuration, Device Recover, and more.
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:¶
PPPoE support
Remote Worker Application
Home Screen Quick Network Status
Advanced tunnel configuration: MSS clamping, MTU, OSPF cost
Hub to Spoke policy improvement
Device recovery
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¶
API |
Changes |
Backward Compatible? |
---|---|---|
POST /devices/apply |
Add replace device API |
Yes |
POST /devices/apply |
tunnels method - Add advanced tunnel options to meta section. mtu, mssClamp, ospfCost |
Yes |
GET /tunnels |
Add interface and devId to response |
Yes |
ALL /devices |
Add PPPoE interface type |
Yes |
ALL /mlpolicies |
Add applyOnWan, overrideDefaultRoute parameters |
Yes |
GET /appstore
GET /appstore/purchased
ALL /appstore/purchased/{id}
GET /appstore/purchased/{id}/status
|
New Application Store APIs |
Yes |
POST /users/auth |
flexiManage authentication |
Yes |
Potential Backward Incompatible Changes¶
Title |
Description |
---|---|
Prevent same source and destination ip for peer tunnel |
System prevents defining two Peers with the same source and destination IPs. Using the same Peer with multiple labels is allowed |
LTE/WiFi statistics are queried periodically |
Changes the previous behavior of querying the devices on REST API request |
MTU Limit set to 9999 |
MTU is limited on device registration and connection to 9999 |
Validate LAN subnet overlaps with tunnel subnets |
Devices with LAN IP address that overlaps the tunnels subnets (10.100.X.Y) is not allowed |
Application permission updated in bearer access keys |
Requires to create a new access token for REST API |
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 |
Configuration errors on device start |
Any configuration error such as no IP acquired by DHCP or low LTE signal may result with a failure. Errors that occurs after start are handled properly |
Overlapping subnets may cause an error in flexiEdge UI |
Configuring overlapping subnets on multiple interfaces in flexiEdge UI may cause an error. Once error detected, resetting the configuration will solve the Issues |
MSS clamping may not operate properly |
Some MSS clamping configuration may not operate properly. Modifying the tunnel MTU resolves the issue |
Remote Worker VPN client error |
Launching Remote Worker VPN client on MacOS will show an error on start, however it does not affect functionality. |