SD-WAN Hub Stops Working When Adding WAN IP Alias

SD-WAN Hub Stops Working When Adding WAN IP Alias

SD-WAN Hub Stops Working When Adding WAN IP Alias
SD-WAN Hub Stops Working When Adding WAN IP Alias
Yesterday
Hardware Version: V2
Firmware Version: 2.3.0

Hi TP Link Omada Team,

 

I’m experiencing an issue with TP-Link Omada SD-WAN. I have a network setup with SD-WAN Hub and Branches. Everything works fine until I add a WAN IP alias on the Hub router. After adding the alias, the SD-WAN Hub stops communicating with the branches, and tunnels fail to establish.

 

From my observations:

  • SD-WAN traffic seems to rely on the primary WAN IP.

  • When the alias is added, traffic may originate from the alias instead of the primary WAN IP, causing the hub to reject connections.

  • Static routes and NAT rules may also conflict when using WAN aliases.

 

What I’ve tried:

  • Ensuring the SD-WAN service uses the primary WAN interface.

  • Checking NAT rules and firewall settings.

  • Updating to the latest firmware.

Result: SD-WAN only works if I remove the WAN IP alias.

 

Question to the community:
Is there a supported way to use a WAN IP alias on the Hub router without breaking SD-WAN? Or is this a known limitation? Any guidance or recommended workarounds would be greatly appreciated.

 

Thanks in advance!

Omada & VIGI | Using at 3 Locations | Controller: V6.0.0.19 (Linux) | GW: ER7206 | SW: SG2428P & SG2210P | APs: 2 × EAP610 | WAN: Jio&Airtel | NVR2016H & 8 Cam's.
  0      
  0      
#1
Options

Information

Helpful: 0

Views: 263

Replies: 0