NEMO Routing with multiple active WAN sources (MultiPDN) - Nemo-Routing-with-multiple-active-WAN-sources-MultiPDN/NEMO-Routing-with-multiple-active-WAN-sources-MultiPDN

• If NEMO is the primary connection or default WAN route for the router;
  • NCM may not connect. (All traffic may be routed over the NEMO tunnel.)
• If NEMO is not the primary connection or default WAN route for the router;
  • NEMO may not connect. (traffic intended for the "Home Agent" may be routed out the primary route.)

• All NCOS versions.
• NEMO network added to existing active WAN. (Ethernet, WiFi as WAN, SIM, [public/private.])
• NEMO and public internet Multi PDN SIM.
• Local IP Network
  • 192.168.0.0/24
• NEMO Network
  • 10.10.10.0/24
• NEMO Configuration
  • Network (192.168.0.0 mask 255.255.255.0)
  • Home agent 
• 

• Session persistence will prefer the default or oldest learned route. 
• When multiple WAN sources are available, the order they become available will determine the default route.
• Binding traffic to specific WAN's will ensure intended traffic egress points.

• Ensure the NEMO WAN (SIM/PID) is active in the connection manager. 
  • For group configuration, create a WAN profile, specify the SIM Slot installation position, and name "NEMO."
• Ensure that primary routing is preserved by having NCM traffic allowed via primary route.
  • Install Policy Based Routing to bind NCM to primary WAN source. (If default connection is lost momentarily, a less preferred WAN may become the default route for unintended traffic.)
• Install Traffic Steering rules to bind destination traffic to the correct WAN source.
  • 
  • 
• Please reference additional documentation for;
  • How to Use Traffic Steering with Multi-PDN
  • Traffic Steering

• To install or enforce new routes or routing rules, the current session must be interupted.
  • Reboot the device
    • Or
  • Flush firewall