Nexapp - FlowEDGE MutliWAN

FlowEDGE MultiWAN

MultiWAN (Wide Area Network) is a configuration where NexappOS uses multiple internet links from different ISPs at the same time. This increases reliability, improves overall bandwidth, and enables seamless failover. When one link becomes unavailable, traffic is automatically redirected to a healthy link, ensuring continuous connectivity for business-critical services.

MultiWAN is commonly used in environments that demand high availability, stable internet access, and better performance across multiple uplinks.

---

Prerequisites

To enable MultiWAN, NexappOS must have:

• At least two interfaces assigned to the WAN zone

This is the minimum requirement to activate MultiWAN behavior.

---

Default Policy (First-Time Setup)

The first time you open FlowEDGE MultiWAN, you must create a Default Policy.
This policy is mandatory and cannot be deleted.
It defines the baseline routing behavior for all outbound traffic unless overridden by rules.

You can choose one of these modes:

Balanced

• All WAN links are used simultaneously.
• Traffic is distributed based on weights assigned to each WAN.
• Each WAN weight can be set between 1 and 1000.
• Higher weight = more traffic share.

Backup

• Only the primary WAN is used normally.
• Secondary WAN activates only if the primary fails.
• Best for pure failover designs.

Custom

• Recommended for 3 or more WAN links.
• Provides multiple priority levels with independent balancing logic.

---

Custom Mode Concepts

Custom mode introduces priority-based traffic usage.

Key concepts:

• Independent priority levels
  Each priority level is evaluated separately.

• Multiple WANs per priority
  A single level can include two or more WAN links.

• Weights drive distribution within a level
  Weights decide how traffic is split across WANs at the same priority.

• Lower priority activates only on failure
  If all WANs in priority level 1 fail, NexappOS uses priority level 2, and so on.

Example Scenario

Goal:
Use WAN1 and WAN2 in load-balance. Use WAN3 as backup.

1. Select WAN1 + WAN2 and apply Balanced with suitable weights.
2. Click Add priority level.
3. Add WAN3 in this new level.
   • Its weight won’t matter much here because it’s the only WAN in level 2.
   • It acts as a backup link.

---

Routing Rules (Policy-Based Routing)

Routing rules allow you to direct specific traffic through a chosen WAN policy based on matching criteria.

Rules can match traffic by:

• Source IP / network
• Destination IP / network
• Source ports
• Destination ports
• Protocol type

How to Create a Rule

1. Create a new policy
   Click Create policy and define how WANs behave for that policy.

2. Create a rule
   Click Create rule to define matching traffic conditions.

3. Name the rule clearly
   Use a descriptive name reflecting purpose (e.g., “VoIP via WAN2”).

4. Specify traffic type
   Define match criteria:

   Source / Destination address options:

   • Enter a single IP, CIDR, or range (IPv4 only)
   • Any address
   • Select a firewall object

5. Assign the policy Pick the policy you created in step 1.

Sticky Option

Enable Sticky if you want traffic from the same source to always exit through the same WAN for 10 minutes.

This prevents session issues on: - banking websites
- insurance portals
- other HTTPS-sensitive services

Sticky is usually recommended for: - 443/TCP traffic

Port Formats Supported

• <port> → single port
• <port>,<port> → multiple ports
• <port>-<endport> → range

---

General Settings

NexappOS monitors each WAN using ICMP (ping) probes.
These health checks determine WAN availability in real time.

Available settings:

• Hosts to monitor
  Add multiple test targets to validate link health.

• Number of ICMP packets
  Define how many probes are sent per test.

• Failure threshold
  Specify how many failed tests mark a WAN as unreachable.

These parameters let you tune MultiWAN sensitivity based on your ISP quality and latency.

---

Reset MultiWAN Configuration

Warning
Resetting clears MultiWAN settings and may cause loss of internet access if no WAN remains configured.

Reset is recommended when: - you previously had multiple WANs
- you reconfigured to only one WAN link
- you want to normalize routing behavior

Run:

/usr/libexec/rpcd/ns.mwan call clear_config
uci commit mwan3
reload_config

After reset, return to the MultiWAN page and recreate policies/rules.

---

Previous page: Static Routes Next page: SD-WAN Policies (Smart Path Selection)

::contentReference[oaicite:0]{index=0}