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
Friday
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
2 Reply
Re:SD-WAN Hub Stops Working When Adding WAN IP Alias
21 hours ago - last edited 21 hours ago

Hi  @Babun-Sikder 

 

Thanks for posting here.

Please confirm:

Is this situation only present in the latest trial firmware v6.0.0.19, or have you also encountered it in previous stable versions?

Are the non-hub gateways using public IP address?

What's the hardware version of the ER7206 you are using? how many? and are they all the same?

  0  
  0  
#2
Options
Re:SD-WAN Hub Stops Working When Adding WAN IP Alias
14 hours ago

 Hi  @Vincent-TP ,

 

Thanks for your reply. Please find my details below:

 

  • I only started using SD-WAN after upgrading to the trial firmware v6.0.0.19, so I cannot confirm if the issue also exists on previous stable versions.

  • The hub is an ER605 v2 with a public IP.

  • The non-hub gateways are:

    • 2 × ER605 v2 (both with non-public IPs)

    • 1 × ER7206 v2 (with non-public IP)

 

After installing v6.0.0.19, I obtained a public IP for the hub and then configured SD-WAN. That’s when I noticed the issue after adding a WAN IP alias.

 

Please advise if further logs or configuration details are needed.

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  
#3
Options