Hi All,
I am using Mikrotik v7.6,
How to combine 2 ISP in this version, Kindly help
Version not imporant, RoS does not allow load bonding…
You can share the bandwidth available to all users but one session can only go through one ISP ( no additive capability ).
Hi anav,
I have done it will v6.4,
I have combined 3 ISP internet, 75+75+100
But in v7.6 there are some options is missing.
Bonding is only possible with the ISP that also bonds at there end… So sorry but I am moving on…dont believe you.
You can’t do load bonding but yes load balancing, but doing load balancing not means that you combine all different ISP bandwith, only do balancing in terms of connections between diferent ISP. But is true that on connections that are multiple and simultaneously you can “combine” all the bandwith, for example downloading a torrent with multiple seeders, this is a very specific case that it works, but with most common traffic you can use the bandwith of only one ISP only. Using PBR, the “bandwith combination” will never work. I did it on 2015 using NTH. PCC I never tested it. Personally on my network I use PBR.
Regards.
Hi krafg,
I understand now, I have tested with ookla speed net, but I also understand your point, Thanks,
Here is again, my question..
How can I do load balance this in V7.6?
By configuring the router appropriately.
Search the forum for PCC
unfortunately is very spread the use of “bonding” term when refering to LoadBalancing, also “summation” or “combine”
Is a better practice to refer to it as Load Balancing
Oficial info about it
I think the poster he/she is referring to is the venerable so called ISP merge they found in youtube with the so called network professional, which is half baked solution that leads to undesirable results specially in HTTPS traffic. I’ve dismantle a lot of customers setup here that rely on this abomination and teach them doing PBR instead to properly utilize multiple links.
Mikrotik is a good swiss army knife if you know how to use it properly some others can’t accept the fact that networking in general has exact science that’s why we have training and certification programs in this field.
Its posts like this that add to the confusion.
They are not the same and you seem to equate them. Bonding is Bonding and should be called bonding.
Load balancing is load balancing and should be called load balancing.
Sure, the point is in terms of what you want combine with WAN’s, Connections or Bandwith. Normally people think in bandwith and here is when people believes that Load Balancing is for that, when for that is bonding and all these people hits with a wall.
Other people believes that configuring one side of link the bonding should works when it’s not like this. Bonding requieres configuration on both sides of link and for this normally only applies for LAN links (PAgP, LACP, etc.)
This is the reality, nothing is magical.
Regards.
Lets talk reality.
The base reasons for multiwans, is
a. to ensure connectivity, REDUNDANCY as businesses cannot afford downtime and thus one uses ISPs from different vendors (and often different types dsl vs cable etc).
(typically seen in a primary and failover scenario)
b. to make a larger pool of BANDWIDTH availalbe to users. In basic terms there is more bandwidth available to share and yes a single connection can only access one ISP during its session. WIth the larger pool of available bandwidth comes the requirement to equitably spread that available bandwidth to all users as we see fit through PCC load balancing queuing etc…
The notion of bonding ISP connections to form one pipe for a connection/session is a possibility due to multipwans but not really a core requirement, design or function. Its an expensive proposition that needs the intervention of the ISP. (same ISP and thus redundancy is dropped immediately). ALso with increases in fiber, one can already get a shitload of throughput on a single pipe.