Dual WAN connections for Failover/Resilience Only - Not Load Balancing

Dual WAN connections for Failover/Resilience Only - Not Load Balancing

Dual WAN connections for Failover/Resilience Only - Not Load Balancing
Dual WAN connections for Failover/Resilience Only - Not Load Balancing
5 hours ago
Model: ER7206 (TL-ER7206)  
Hardware Version: V2
Firmware Version: 2.2.3

Hi,

 

I have deployed an ER7206 router at a site with 2 WAN connections :-

 

SFP WAN/LAN1 - 100Mbps fixed line connection

WAN2 - 4G Cellular connection (metered usage).

 

The intention is that the WAN1 connection will always be used when available. The WAN2 connection will only be used if WAN1 is down.

 

Currently the configuration is as below :-   (screenshot from Omada controller version 5.15.24.18)

 

 

We are seeing very high (and therefore expensive!) use of the cellular connection via WAN2.

 

It appears that only VPN traffic is using the SFP LAN/WAN1 connection.

 

Could anyone point me at what I may be doing wrong ?

 

Thanks,

 

 

Andy

 

 

 

 

 

 

  0      
  0      
#1
Options
3 Reply
Re:Dual WAN connections for Failover/Resilience Only - Not Load Balancing
5 hours ago

  @AndyBH 

 

set up a policy route and direct traffic to the WAN port you want to use as default and enable Use the other WAN port if the current one is down

 

 

 

  0  
  0  
#2
Options
Re:Dual WAN connections for Failover/Resilience Only - Not Load Balancing
4 hours ago

  @MR.S 

 

Thanks - I've configured as below.......

 

 

But still if I visit whatsmyip dot org from a PC on the "Guest-Wifi" network it is showing the IP address of the Cellular connection on WAN2. 

 

I did reboot the PC to clear any exisiting sessions. 

 

Is there anything else I need to be doing for this to take effect ?

 

Thanks,

 

Andy

 

 

 

  0  
  0  
#3
Options
Re:Dual WAN connections for Failover/Resilience Only - Not Load Balancing
4 hours ago

  @AndyBH 

that was strange, with the internet settings you have, you should only use the backup wan when the primary wan is down. so there is actually no need for policy route either. try running whatip in incognito.
you can also try setting the internet settings like this and use policy routing.

 

 

  1  
  1  
#4
Options