Dual-WAN Config via TP-Link TL-ER6020

[clikdude]

Problem: Can't access internal Gateway IPs "consistently" from internal network. Perhaps I need some static routes? But how?

TL;DR

I have setup a TL-ER6020 on a small network, with a Dual WAN configuration to two separate AT&T ADSL Lines.

Here are the details:

Code: Select all

      AT&T PACE 5268AC Gateway/Router
      __________
      |        |
      ----------
      Router Internal IP: 192.168.1.254 (Net: 192.168.1.0/24)
          |
           \
            \
            WAN 1 DynIP: <AT&T Public IP via DMZPlus: 107.*.*.*>
             _____________
             | ^         | TL-ER6020 - Router IP: 192.168.0.254/24 (Net: 192.168.0.0/24)
             -------------
            WAN 2 DynIP: <AT&T Public IP via DMZPlus: 99.*.*.*>
            /
           /
          |
      Router IP: 192.168.2.254 (Net: 192.168.2.0/24)
      __________
      |        |
      ----------
      AT&T PACE 5268AC Gateway/Router

Load Balancing is configured for both App affinity, as well as Bandwidth balancing. Testing works perfectly.

So what's the problem? Well, from the internal network (192.168.0.0/24) very often my workstation (or any workstation for that matter) cannot reach (ping, traceroute or otherwise) either the 192.168.1.254 or the 192.168.2.254, or both addresses, essentially preventing access to manage the Gateway Routers.

Sometimes the route is "just there", and everything is fine. But often it is not, and no matter what static route configuration I setup, I cannot get it to work.

What have I improperly configured above, or what could be done better to get the internal IP routing to work?

I have attempted Static Routes that were "seemingly" correct, and enabled RIP (v1/v2) and no joy. I am at a loss as to how to correctly configure this, and sorry to say, TP-Link support was similarly incapable of helping.

Any help would be greatly appreciated.