Multi-WAN on GL-AXT1800 – can it route into still functional ethernet that has a broken internet connection?

Router
1

Hi,

my GL inet router sits on network A and routes into another ethernet B. Network B has another router (not GL Inet!) that connects it to the Internet.

I have setup Multi-WAN with tethering as a fallback which works fine. When the connection from network B to the internet is lost, the GL-AXT1800 considers network B as unreachable and switches to tethering, just as expected.

Now here is the catch: Network B is not totally off line, it’s just the internet connection. There is a network file server on network B that I want to reach from network A.

Q: Can I make the GL inet router recognize network B as a LAN that is still reachable, instead of a WAN that is unreachable?

Can’t get my head around this… :thinking: can anyone help?

2

You could change the “testing” IPs for Multi-WAN to IPs that are within the network B. In this case, Multi-WAN will always recognize B as active. But it won’t know about internet issues then.

Or you create a static route within luci for network B.

1 Like
3

Thanks for your reply!

Sounds like I should use the static route. What does it look like (I am not a routing expert)?

And: would it interfere with Multi-WAN?

4

Within luci you will find the routes page, should look somehow like this:

image
image1016×554 42.5 KB

There you will create a new route containing a target (your network B, so f.e. 192.168.22.0), the targets’ subnet mask (f.e. 255.255.255.0) and the IPv4-Gateway (which is the IP of the network B router)

5

Hmmm… this does not work. I have added this rule:

interface=wan, target=192.168.137.0/24, gateway=192.168.137.32

Then, Status/Routing shows this when the internet is offline:

CleanShot 2024-05-07 at 12.23.01@2x
CleanShot 2024-05-07 at 12.23.01@2x1772×638 34.3 KB

And the ping does not work:

% ping 192.168.137.32
PING 192.168.137.32 (192.168.137.32): 56 data bytes
64 bytes from 192.168.137.32: icmp_seq=0 ttl=64 time=0.712 ms
64 bytes from 192.168.137.32: icmp_seq=1 ttl=64 time=0.972 ms
64 bytes from 192.168.137.32: icmp_seq=2 ttl=64 time=0.688 ms
^C
--- 192.168.137.32 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.688/0.791/0.972/0.129 ms

% ping 192.168.137.1 
PING 192.168.137.1 (192.168.137.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
--- 192.168.137.1 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss

What gives?

6

Because I am mostly too stupid for imagine how the setup looks like, could you draw it using draw.io maybe?
Make sure to include the IPs for each router (and modem) as well.

Thank you!

7

Looks like this:

CleanShot 2024-05-07 at 12.52.02@2x
CleanShot 2024-05-07 at 12.52.02@2x1908×1380 196 KB

8

Hi @admon, is there already news about this?