If I want to use both ISPs fiber 1gig up/down and Cable 100 down 10 up, can I do so without mangling?
Certainly this is a load balancing nightmare which would be probably be setup as a 10:1 ratio
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.
Hi Sib
Awesome advice.
I have done research in many of these areas and thus familiar with the refs, especially the MUM archives stuff.
Since I have a home network and a CCR1009, I think I can take the hit in losing fastrack without any real negative effect on users, do you agree??
exacly, I use that way at every RB I configure with 2xWAN and more, just that all stuff give me all possibility.
I not use a bandwitch-way of selection a main wan, I always send servers via slower isp and users via better wan
but you can adapt any of LoadBalance method in this way.
Mangle are awesome ![]()
What is the most efficient way to send users to the better wanip. A simple route rule for mangled traffic?
What if I have a load balance scenario of 10:2 for example, and the primary the 10 fails, no connectivity (I would use external recursive to check).
How does the router then respond??
I use mangle to manage that.
What if I have a load balance scenario of 10:2 for example, and the primary the 10 fails, no connectivity (I would use external recursive to check).
How does the router then respond??
When ISPx not work, then all conection inside Firewall\Connections gets timeout… in some time… this means user see that internet not work until theyr brower/soft/app not do a new Syn connction who will be send via working ISP OR the old ISPx cameback to life.
This can be fixed just by removing that ISPx marks in firewall and all theyr keep-a-live package will go via working ISP, I put that info as 4) point of my howto. This is awesome and sometimes you not even see ping timeout, sometimes 1x ![]()
Can you give an example config so that I can see how you put it together?
? you not read a #2
or I not understand what you want put together.
I understand the mangle bit, I use it to. But why the recursive part?
ok, means you mix a 1) point with RecursiveRouting with 3) who detect if wanx working or not.
ad1 and ad3 work together.
- ad1 RR do “lock path” that to hostA you go via ISP1 only - this is perfect, and ad3) use from that route to detect, if internet is work via that ISP.
This is mix of both. Sometimes this is winner instead of just ad3 who can use additional parameters like interface and src-address, who can have problems with Contrack and this ad1 solve that at lower level.
I hope this is understand way of answer. - ad1 RR and special part with FailOver, is duplicated in ad3 and here you can have right. But… Routing detection of “next hop” status is just slow, 2x10s to detect DOWN… and ad3) do the same but faster, e.g. if ping 10 pings with interval 1s and all 10x pings have timeout then this can be more “sure” offline detection compare to ping every 10s count=2 who do routing and can generate false detection. Thats ad3 is used.
I hope I write in human form ![]()
I knew it!!, You are either an alien or a very smart teddy bear!!
What Anav said, and thanks. I will try to build this in the weekend and provide some feedback.
I will stop hijacking this post with this one last question. Sib, did you manage to resolve this recursive load balancing with LTE?
Dude2048
This “1) Recursive Routing” can be done only by MikroTik Developers Team
I note that the Mangle video appears to be six years old. Is there anything newer in this space for Mikrotik?
new ways of creating vlan, probably MikroTik give us new way of vlan of few of them in new ros7.
About Mangle and MultiWAN, no, this is still very good.