Load balancer setup 2 WAN with port fordward

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Load balancer setup 2 WAN with port fordward

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Load balancer setup 2 WAN with port fordward
Load balancer setup 2 WAN with port fordward
2024-04-11 13:37:12
Hardware Version: V2
Firmware Version: 2.1.2

Hello everyone,

i could see a lot of community members got their issue resolved here by SME's intervention.

i have purchased ER605 Omada Gigabit Multi-WAN VPN Router for load balancing and port forwarding purposes.

someone please help me to understand if my configuration is correct. after watching few videos, I have done settings as described.

 

We have 3 WAN’s and using this device for Load balancing and fail over (ACT, Airtel and BSNL) ACT 1 Giga, Airtel 300 MBPS and BSNL 90 MBPS respectively.

3 WAN and LAN should be in separate subnet - example my Tipi link IP is 192.168.0.1 have changed it to 192.168.1.1 as a lot of devices running on this IP series.

 

WAN-01 - 192.168.2.1 - ACT stating IP availed- for port forward purpose- all ports opened other than port 25.

WAN-02 - 192.168.3.1 - Airtel.

WAN-03 - 192.168.4.1 - BSNL.

 

Gateway IP address should be WAN -01- ACT IP address in WAN 2 and WAN-03.

 

Port forwarding done – Transmission- NAT- Virtual Server.

 

 

Please validate and confirm if all settings are okay

  0      
  0      
#1
Options
1 Reply
Re:Load balancer setup 2 WAN with port fordward
2024-04-11 16:38:37

  @sathyashankar 

 

Loadbalancing, your weights should be 100,30,9 across WAN1,2,3.

 

It is not clear if you are running any of the ISP devices in bridge mode, or if they are in routed mode.  Where possible I recommend bridge mode, because that means that the ISP assigned IP gets assigned to the respective WAN port on the TPlink device.  If that's not possible, then I would statically assign an IP from the router's subnet (ie 192.168.X.1/24, so assigned WAN IP as 192.168.X.2) and then make this .2 address the DMZ for that router (port forwards all ports).

 

If you have a public static IP on your 1G connection, and you want those ports to be accessible to the internet, then those connections always have to go through WAN1..which means you need to return those connections to WAN1 and not via the load balancer.  So set a Policy Route for any server/service you have exposed on WAN and force, based on source IP and/or port to go back through only WAN1.  

 

User traffic will still have the ability to round robin, based on weighting, across all 3 connections, but any service depending on the IP and/or DNS resolution of WAN1 will stop working if WAN1 goes down.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#2
Options