Sorry, async WAN-s and without Mangle… no idea
I always do
-
MANGLE
I really recommended to learn and do this one HowTo who have got the best way to use many WAN’s at ones.
Next you can use any method netwatch/script/pcc etc to just flow the outgoing - then this is small stuff.
Bandwidth-based load-balancing with failover. This presentation also covers Mangle.
This was presented at the MUM (MikroTik User Meeting) in New Orelans, USA.
Tomas Kirnak - YouTube: https://www.youtube.com/watch?v=67Dna_ffCvc&t=1s
http://mum.mikrotik.com/presentations/US12/tomas.pdf -
My own detectors of offline and do action with fix that stuff
Advance watchdog: http://forum.mikrotik.com/t/tx-rx-fp-rx-dropped-pppoe-account/132656/1 -
ISP who is now DOWN should have a remove all connections from conntrack table, and that connection and theyr keepalive will start NEW connection via UP ISP without breake at network.
One of main action here is that:
ip route enable [find dst-address="0.0.0.0/0" gateway=8.8.4.4 routing-mark="wan2_SM" ]
delay 1s
foreach IPList in=[/ip firewall address-list find list="LANs_via_SM"] do={
local CurIP [ip firewall address-list get $IPList address ]
local IP3oct [pick $CurIP 0 [find $CurIP "." ([find $CurIP "." ([find $CurIP "."]+1)]+1)]]
ip firewall connection remove [find connection-mark~"wan1_Orange<->LANs" src-address~$IP3oct ]
ip firewall connection remove [find connection-mark~"wan1_Orange<->LANs" reply-src-address~$IP3oct ]
}
With all that points I receive good and FULL working MultiWan.
The last one point is very importand in your situation because he help’s hop to next ISP that users who are using “re-connected” wan.
Other words it’s fix for massive TIMEOUT problem when WAS is offline.
btw, IP Octet manipulation thread.