Device Management

Every flexiEdge device can be centrally managed and configured from flexiManage. This documentation section covers the steps required in order to sucessfully deploy flexiWAN.

If you found an error, let us know! Drop us an email to

Initial configuration

flexiWAN can be installed on a variety of supported devices or delivered pre-installed from our certified hardware vendors. After installing flexiWAN or receiving a device with flexiWAN pre-installed, initial network configuration is required in order to connect the device to internet and register with flexiManage.

Logging to local flexiEdge UI

flexiWAN offers a local web interface for initial configuration and troubleshooting. flexiEdge UI is enabled by default on all interfaces and it can be accessed using device IP and port 8080. flexiEdge UI can only be accessed if the device has an active network interface.

Open a browser and point it to the IP and port 8080 of currently active network interface on flexEdge device. Example:


After opening the flexiEdge UI page, enter username and password from Linux.


Upon logging in with credentials, Home page will display device information and status. From the sidebar additional options can be accessed.


The sidebar follows post-installation configuration flow:

  1. System Checker - running system checker verifies your device can run flexiWAN

  2. Interfaces - Configuring network interfaces

  3. Settings - inserting token to connect the device to your flexiManage account.

After completing all three steps the device will be connected to your flexiManage account and waiting for approval.

Running system checker

System checker is a post-installation tool which verifies system requirements and fixes software configuration errors.

Click on System Checker page and run it to check if the system meets the requirements.

system checker

If installed on supported hardware, in most cases there will only be “soft” failures which can be fixed by clicking on “Auto-fix”:

system checker

Confirm the output now says system requirements are met and navigate to the interfaces page.

Network interfaces configuration

On the following page network interfaces can be viewed or configured. At this point only wired interfaces can be configured while WiFi or LTE interfaces can be configured through flexiManage.


flexiWAN relies on netplan for interfaces configuration. It is recommended to configure WAN and LAN wired interfaces prior to adding the device to flexiManage for recovery purpuses. This way the device is reachable via configured interfaces even when flexiWAN is not running.


In addition to wired ethernet connection, flexiWAN supports PPPoE. PPPoE can be configured and provisioned from the flexiEdge UI interfaces page. Simply click on the settings icon next to interface name which will open PPPoE configuraton page.


From the PPPoE configuration page enable the interface and enter the credentials from PPPoE provider and click save. Optionally set custom DNS.


Once PPPoE is configured, wait for a few moments until the page shows PPPoE connection established.



Please note PPPoE can only be provisioned from flexiEdgeUI and its parameters cannot be modified from flexiManage.

After configuring network interfaces, follow the next steps to register device with flexiManage.

Device registration

To register a device, first create your organization token. The organization token needs to be generated only once and is used for all the devices in a single organization. Having multiple tokens in single organization is also supported, where it introduces additional security in case of unauthorized physical access of device. In the flexiManage, navigate to Inventory > Tokens and click on “New Token” button.

Create Token

Provide a token name and click “Add”. A new token will be created and presented in the Tokens page.

Token Created

Copy or download the token in order to add it locally on your device. Token can be added to the device in two ways:

  • connect to flexiEdge UI web interface

  • ssh or using direct console.

Adding the token through the flexiEdge UI

Open a browser and point it to the IP and port 8080 of currently active network interface on flexEdge device. Example:


After opening the flexiEdge UI page, enter username and password from Linux.


Navigate to Settings section and then enter the token copied from flexiManage. Click Update Token and after that continue to flexiManage Devices page to complete the device registration.

EdgeUI 2


Make sure to follow flexiEdge documentation and first run and pass system checker. Check flexiEdge UI to learn more.

Adding the token using SSH or console

For this step connect to a direct console or ssh connection to the device is required. Insert the token using text editor such as nano or vi:

nano /etc/flexiwan/agent/token.txt

Add token

Inserting the token is the final step where local EdgeUI or direct console / ssh connection to physical device are needed. Afterwards all management is done through flexiManage.

Completing the device registration

Once the token is added, the device will appear in the Inventory -> Devices page as a new and unapproved device:

Unknown Device

Click on the newly appeared “Unknown” device name to open the device settings. Enter the device name and description, then approve it.

Update Device

Click on “Update Device” at any time to apply the latest configuration. Follow the next section for device configuration.

Device configuration

Navigate to the Interfaces tab from where all network interfaces can be viewed and configured.

new device

Interfaces can be configured by changing “No” to “Yes” in the Assigned column. In most cases, WAN interface IP’s will be automatically recognized assuming link is up, and default to DHCP. Fields can be modified directly by clicking and modifying them. In case of LTE or WiFi interfaces, click on settings (Gear Icon) next to each of the interfaces for detailed configuration. WiFi and LTE configuration is covered below in greater detail.

Configuration overview

The following network configurations are available on the Interfaces page:

  • Type - marks interface as WAN or LAN. flexiWAN requires at least one WAN and LAN for operation. Multiple WAN and LAN interfaces are supported.

  • Assigned - when set to “Yes” interface can be configured. Select “No” to not use the interface with flexiWAN.

  • DHCP/Static - used with WAN interfaces, WAN can be configured with static IP or set to receive an IP via DHCP.

  • DNS settings - within DHCP/Static column click on settings to open DNS settings. Users can assign manaul DNS or allow upstream override.

  • Metric - use metrics to define primary, secondary etc. interfaces.

  • MTU - set custom MTU per interface. Also applied on tunnels.

  • Public IP - automatically detected external IP using STUN. If your flexiWAN device is behind a NAT or a router, the public IP colunm will show the external IP.

  • Path Labels - assign Path Lables to logically label or filter traffic. See Path Labels section for more detials.

  • OSPF - LAN interfaces have OSPF automatically enabled in Routing column. OSPF is available on LAN interfaces only.


  • Wired ethernet, PPPoE and LTE interfaces are supported as WAN interfaces.

  • Wired ethernet or WiFi AP mode are supported on LAN interfaces.

  • Make sure to assign interfaces by changing “No” to “Yes” in the Assigned column.

  • Multiple LAN and WAN interfaces are supported.

  • Status icons (green, red, gray) in GW column show if the device has internet connectivity.

  • Netplan is used for networking configuration, all flexiManage network configuration is saved to Netplan.

Internet monitoring and failover

By default each WAN interface has gateway monitoring enabled. Its purpuse is to monitor and signal to the user if WAN interface is down. Gateway monitoring is part of automatic failover functionality, allowing failover between multiple WAN interfaces. Automatic failover works out-of-the-box and automatically when there are multiple WAN interfaces present. Interface which has lower metric, will have higher priority. Eg. bottom interface from the screenshot has higher priority.

gateway monitoring

Monitoring option can be viewed and changed by clicking on “Setup Gateway” icon in the Gateway (GW) column.

gateway monitoring 2

NAT Traversal (STUN) configuration

flexiWAN enables NAT Traversal by default, allowing devices to establish tunnels behind NAT, when there is a private IP on flexiEdge WAN. NAT Traversal setting is automatically adjusted if it detects public or private IP on WAN, so there is no need to disable it in most cases.

To configure NAT Traversal or change Public IP, simply click on settings icon in the Public IP column within WAN row:

NAT Traversal


  1. Public IP can be changed by clicking on interface Public IP column. Note that this is possible only when IP is statically assigned, and not when using DHCP.

  2. flexiWAN can detect if it’s establishing tunnels locally (devices within the same net3work) or remotely (geographically remote site) and adjust NAT Traversal accordingly.

  3. Under Public IP column detected NAT type is displayed. Most common NAT type detected is Full Cone. In case it says “Blocked”, try updating device settings after assigning interfaces. When flexiWAN detects bridged / direct external IP on WAN, NAT traversal will be automatically disabled and status will be “Open Internet”


  1. When using NAT Traversal (STUN), make sure to disable NAT randomization on your upstream router / edge device. Otherwise it may change outgoing port for every connection and prevent tunnels from being connected. If possible, put flexiWAN in DMZ on your upstream router.

DNS configuration

Each WAN interface, whether configured statically or set to DHCP can have DNS servers set. The DNS servers configured on WAN will be used by flexiEdge device for DNS resolution. This is not to be confused with DNS setup for LAN clients, which can be configured when configuring DHCP server on LAN.

To check current or set manual DNS servers for WAN, simply click on the Settings icon within “DHCP/Static” column. In same window DNS doman can be set.

default DNS settings

By default and if DHCP is set for WAN, device will use DNS servers received from DHCP. However by disabling the “Use DHCP DNS” users can assign DNS serves manually.

default DNS settings 2

We recommend using and combining the below DNS providers:

  • Google DNS -

  • -

  • Cloudflare -,

  • Quad9 -,

LAN Bridge configuration

Two or more network interfaces can be bridged when assigned the same IP and CIDR. Clients connected to both or more interfaces will assign or receive an IP from the same range.

  skinparam linetype ortho
  left to right direction
  skinparam rectangle {
      borderColor Transparent
      backgroundColor Transparent
      fontColor Transparent
      stereotypeFontColor Transparent
      shadowing false
  node "vRouter" as VPP {
      rectangle GRP1 {
        node "Bridge" as BR1 {
          usecase "LAN 1" as LAN1
          usecase "LAN 2" as LAN2
      usecase "Loop 0\n<size:10>(</size>" as Loop0
      usecase "Other\nFunctions" as ROUTER
  node "Computer 1\n<size:10>(</size>" as C1
  node "Computer 2\n<size:10>(</size>" as C2
  C1 -- LAN1
  C2 -- LAN2
  LAN1 --- Loop0
  LAN2 -- Loop0
  Loop0 .. ROUTER


Bridge is automatically created when multiple LAN interfaces are configured with the same IP address and CIDR. Both DHCP server and OSPF continue to work on bridged interfaces.

Once two or more interfaces are configured with the same IP and CIDR, the symbol BRIDGE_ICON will indicate bridge mode is configured. Make sure to update device to apply changes.

LAN bridge


Vhen using virtual machines make sure to attach different virtual switch to each LAN interface, in order to avoid network loops.

LTE configuration

flexiWAN supports LTE network interfaces in addition to wired interfaces. Since LTE functionality is configured through flexiManage, it’s required to have an active wired network interface in addition to the LTE interface. The wired interface does not have to be assigned, but it must be recognized and have internet access through which the device can connect to flexiManage. Currently flexiWAN supports specific M.2 LTE modems from the list below.

Please see the list of devices Certified by flexiWAN on our website. We recommend checking with us or with the hardware vendor that the LTE or WiFi of the device you purchase has been certified for flexiWAN.

Known working and supported LTE cards:

LTE Modules tested by flexiWAN


Module Type

Sierra Wireless









  1. Other models by Sierra Wireless and Quectel may work as well. If you use a non-listed card which works flexiWAN, let us know and we’ll add it to the list.

  2. Modems must be set as MBIM and not QMI. Run System Checker to change to MBIM on supported modems.

In order to configure the LTE interface, navigate to device settings and click on Interfaces tab. From there, click on settings (Gear Icon) next to LTE interface name to configure its settings.


After clicking on the LTE settings, LTE configuration options will appear. Configure the following settings:

  • Correctly enter SIM PIN.

  • Set the LTE to enabled.

  • Enter interface metric (must not be same as wired WAN).

  • Confirm APN is detected correctly. In case the APN is not detected, enter your APN manually.

LTE config2

SIM PIN can be changed or disabled by clicking on settings icon next to PIN state.

LTE config3

After entering settings, click Save and then click on Update Device from Interfaces tab.


Important considerations when configuring LTE network interfaces:

  • Always make sure to keep NAT Traversal enabled for LTE interfaces, otherwise tunnels may not connect.

  • When adding tunnels between LTE and other devices, STUN can take up to several minutes until providing port to NAT Traversal. Monitor “Device-modify” and “add tunnel” jobs from Troubleshooting > Jobs section.

  • If interfaces page doesn’t show LTE interface, try to reset and re-add the device to flexiManage.

  • Supported LTE cards are listed above. Using non-supported LTE cards require testing prior to deployment. USB LTE cards were not tested at this point.

WiFi AP configuration

flexiWAN supports WiFi AP for LAN, assuming the WiFi card is recognized and supported by the underlying Ubuntu (see list of pre-tested WiFi cards below). flexiWAN uses hostapd for wireleess access point, supported standards are b/g/n and AC. Both 2.4Ghz and 5Ghz modes are supported, however dual band is not supported currently.

WiFi cards tested by flexiWAN:

WiFi cards tested by flexiWAN




QCA6174 802.11ac


Out-of-the-box (OOB) support



requires drivers via DKMS



OOB support



OOB support



OOB support

Comfast CF-812AC


requires drivers via DKMS



OOB support


Most WiFi cards can work if the correct drivers are installed. Use DKMS and install approperiate WiFi drivers with it.

In order to configure WiFi AP on LAN, navigate to the device settings and click on Interfaces tab. From there set the WiFi recognized interface as assigned and add the local IP. Then click on the settings icon next to WIFI interface name.

Wifi AP 1

On WiFi settings page, configure the following to enable its operation:

  • Select between 2.4Ghz and 5Ghz bands via tabs on top.

  • Enable the wifi interface

  • Add SSID / WiFi network name

  • Choose Operation Mode. Make sure your WiFi card supprots the selected mode.

  • Pick a Region.

  • Set Channel or keep it set as Automatic. In most cases Automatic moode will select the best Channel, however with some cards it is required to manually set the Channel.

  • Pick security Mode and enter WiFi network password.

Enter WiFi AP settings and click save at the bottom of the page. Make sure to also click on “Update Device” while on Interfaces page.

Wifi AP 2


WiFi AP considerations:

  • WiFi functionality is limited to the WiFi card capabilities.

  • When using 5Ghz, the vRouter may fail to start due WiFi ACS not collecting survey data. Try setting the Channel manually instead of configuring it as Automatic.

  • If your WiFi card is not recognized, try to reset and re-add the device to flexiManage.

  • In most cases, if your WiFi card is not recognized, but has support for linux, drivers for it can be added via DKMS and it should work with flexiWAN afterwards.

  • Some WiFi cards have world regulatory domain hardcoded and may not be able to run when configured to some specific Channels.

  • Be sure to enable DHCP on WiFi LAN interface so AP clients can get an IP.

Completing the configuration

Once network interfaces are configured, click on “Update Device” button to apply your configuration.

Update Device


  1. Changes to the device configuration can be applied dynamically even when the device is running

  2. Changes in the interface assignments will result in router restart

  3. WAN changes may momentary disconnect tunnels.

  4. WAN IP change will trigger automatic tunnel reconstruction.

After the device is approved and interfaces configuration is complete, it will show status as approved, connected and synced after a few seconds.

Connected Device

Starting/Stopping the vRouter

The device is connected to the management but the router is not running yet. To start a device click on the “Start Device” button.

Run Device

After a few seconds the device will start and show that the router is running. During the start or stop process, the device may disconnect from the management for a few moments, as the vRouter takes control of the interfaces.

Running Device

Follow the same steps to create multiple devices in your network:

Multiple Devices

To stop the router click on the “Stop Device” button.

Restoring Devices

Each device configuration is kept in flexiManage, and as long as the device is not deleted from it, original configuration can be restored to a new flexiEdge device. In case of a hardware failure or other cases where flexiEdge device is no longer online, restoring configuration from an existing device to a new one is possible in just a few clicks.

Restore feature will preserve all device settings such as interfaces configuration, Path Labels, static rotues and every other device specific configuration available from flexiManage.

Procedure for restoring configuration is outlined below, prior to restoring make sure to follow the usual installation and post-installation steps for the replacement device. Specifically, after installing flexiWAN on a new / replacement device, don’t forget to run the system checker and insert the token afterwards.


When restoring the old configuration to a new device, devices must have identical number of interfaces.

In case the original device is no longer available and now shows as offline in flexiManage, its configuration can be restored to a new device. In this example, device Ottawa is no longer connected to flexiManage.

Device not connected

After installing flexiWAN on new device and adding the token, it’s available in flexiManage and ready to replace the disconnected one.

New device connected

Select the old from which you wish to restore and the new device on which the configuration will be restored.

Device selection

Following the usual flexiManage flow, click on the Actions button and from it click on Replace Device.

Replacing device 1

On the following pop-up confirm which device is the device being replaced and which device is the replacement device. In this example, Ottawa device is old and new device is not yet named. Lastly, approve the original device deletion after which the new device will have the settings and name from the original device.

Final approval

That’s it, flexiEdge device has been restored. the new device will now appear as connected and in not running state. Please make sure to verify all configuration is correct before starting vRouter.


Deleting Devices

To delete a device click on the “Delete Device” button. Make sure to delete all Tunnels connected to that device before attempting to delete it.


Every device change or configuration will schedule a job to apply the changes. This is done for scalability purposes and so the UI will not halt. The job is queued in the system and executed when the device is connected and ready. The operation succeeds only if the job is completed successfully. Jobs can be viewed in the Troubleshooting -> Jobs menu. An error during an operation is reported as a failed job. If the job fails, the system rolls the job back and returns to the previous state.