Dual WAN upgrade with 1 Static IP and 1 dynamic IP (only Failover to static for outgoing but reachable from outside)

Hi,

i have a perfectly working setup for my House based on a single WAN Setup with a static external IP.
I can reach all my internal Servers and clients with dst-nat port forwarding rules. Working like a charm.

My Problem is a traffic volume limit from the static IP provider, and after my wife and me switched to homeoffice we have too much traffic Volume.

The simple thought Solution was a mikrotik ATL LTE 18 Antenna as a second WAN with unlimited traffic…and then my journey to nearly 50 howtos and video tutorials startet but i cant get it to work as expected.

My Plan:
I want to use the new LTE WAN primary for all my inet traffic, the Static IP WAN should only be used if the LTE WAN is down.
BUT the static IP WAN must be reachable from outside for example for security cams or home automation connections.

With the tutorials i was able to get load balancing working or in an other attemp i was able to switch the wan usage by setting distance for the static WAN route=2 and LTE WAN route=1, but whatever i tried lead to the same problem: if the LTE connection ist used primary with distance 1 and i set the static WAN distance 2 the dst-nat did not work (tried connection from outside, dst-nat rules shows me the packets, but it did not answer correctly…

Hope that someone knows what to do…i tried it alone for the last 2 weeks every night without success…little frustrating



home network plan.jpg

need export
/export file=anynameyouwish ( minus router serial number and any public WANIP information )

Q1: Do you access any servers from the LAN using WANIP or all done directly with LANIp of servers???
Q2: How would external users know to reach Wan1 or WAn2 to access servers ??

Q1: at the moment it is possible, so its easier for mobile devices. i dont have to switch server connect profile between wlan mode and mobile mode. But if this is a problem i can switch to only lanip
Q2: External startet connections to internal 192.168.0.0 should only be routed on WAN1 (the static IP) that is working at the moment and should not be changed. The WAN2 (dynamic IP over mobile 4G) should only handle the traffic initiated from 192.168.0.0 to the internet and back
dualwan.cfg.rsc (26.2 KB)

What server do you have that initiates traffic heading outbound??

i have different Servers in the dhcp Range 192.168.0.2-192.168.0.254, for example there is a home assistant, the synology NAS with its services, a pihole for dns blocking, aso.

when they initiate traffic they should use the WAN2 interface for example for their own update prozesses or scheduled file transfers…but if i try to connect to them from outside i do it with the the Static IP on WAN1

i was able to fix it alone :wink: thx to this forum and another 50 howtos i understood mangle function completely.
My usecase is more simple than i though…i just needed 2 mangle rules for marking internal connections to outside and give them to another wan route… now everything is working fine…
failover aso. i will build up later.

And after i review my cfg export i cleaned up a lot of old and not used stuff.

Good to hear!!
Yes if you have traffic coming in on WAN1 to ensure it leaves WAN1 mangling is often required.