I'm currently using my Beryl AX to connect to a Guest WiFI for internet access, and then my WAN port to a rack of systems on a few isolated networks. I want to be able to access both connections simultaneously.
Is this even possible, being that Multi-WAN modes are either "Failover" or "Load Balanced"?
If it is possible, are static route(s) the way to go or some other method?
Any opinions or suggestions would be greatly appreciated. Thanks in advance!
Pls explain in details what you want to do.
Load balance will use both connections. Data will be distributed to either connection but not what you can control.
May I know do you want to connect and access both connections (WAN and Repeater Wi-Fi) at same time?
I think you were supposed to config the routing table of the Beryl AX, go to LuCI page, find the Static Routes, based on your network topology, set the static route (your special access is the rack of the system, means that interface is WAN), another data such as normal access will via the repeater Wi-Fi (no required to configure).
Yes, sorry... I want to connect to both interfaces at the same time. Internet via the Guest WiFI and a specific set of networks (say 10.192.0.0/16) on the WAN port.
I figured I would need to use static routes, and I've tried configuring them. However I'm getting confused by two things (perhaps more).
First - which Multi-WAN configuration do I want to use? I'm assuming Load Balance?
Second - If I need to configure a static route for the 10.192.0.0 network, which interface would I bind it to exactly?
Thanks for your help!
Failover and Balance both ok, it could not affect the step 2, just depends on your scenario.
I think would like to know the gateway IP of the 10.192.0.0/16, so that can be added the configuration (if say the gateway is 10.192.0.254/16:
Can you pls try @bruce 's suggestions?
I think that is the correct answer.
I think I got this working? 
Still need to do some further testing, but things are looking promising!
I had to enable the static route, as you mentioned (thank you for that!).
But, I also had to turn off Enable Interface Status Tracking, otherwise it was only letting me use one interface to egress at a time. Once I did that, boom!
This interface status tracking issue is really a bug. I have both MT3000 and a Mango (MT300v2). There is no problem in the ethernet interface status track in MT300v2. But in MT3000 with the same parameters, it always reports connection problem and stops all connections but in fact the connection path is okay. Would GL.iNet Staff please look into this issue and fix it?
Please share some screenshot or syslog, to let me know detail the issue.
how you know the link still connecting? by the ping in SSH or the PC/phone Internet no problem?
Where to show? post some screenshots.
Screenshots below -
Everything connects well at first if I disable ethernet interface connection tracking.
Then I enable the interface connection tracking at the ethernet interface
The indicator of ethernet turns from green to grey and an exclamation mark appear in first screen, then ping fails.
Log file attached
MT3000.tar (197 KB)
Is IP 10.35.93.65 or 10.35.52.1 a primary up 2 level router? The topology like that?
MT3000 -> router A: 10.35.93.65 -> router B: 10.35.52.1
I don't think so. MT3000 was allocated an IP address of 10.35.52.188 at WAN side. 10.35.52.1 is the gateway, while 10.35.93.65 is DNS server.
Confirmed with R&D, the Multi-WAN only support the track public IP, not support the private (local) IP, i.e. the private class A/B/C
Thanks for your information about the behaviour. It is strange to me because I was using Mango and the behaviour was different. Nevertheless, I think the following should still be improved.
The Mango probably have not updated the codes.
