Community discussions

MikroTik App
 
User avatar
todayheads
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 79
Joined: Wed Jul 27, 2016 2:18 pm

Merging Multiple Wans

Mon May 14, 2018 2:54 am

is there a way to combine internet connections coming from the same ISP like 3 DSL connection from the Same provider?
 
User avatar
anav
Forum Guru
Forum Guru
Posts: 19352
Joined: Sun Feb 18, 2018 11:28 pm
Location: Nova Scotia, Canada
Contact:

Re: Merging Multiple Wans

Mon May 14, 2018 4:56 am

The short answer is no if you think you can triple the speed or throughput of one connection.
The truth is extra WAN connections means that you can
a. have a wider amount of bandwidth to share from a single device (your router).
b. you have redundancy in that if one ISP is down, the other can pick up some of the slack (however this assumes a more typical, cable and dsl or fibre connection.
If all from the same ISP its more than likely that the ISP going down will hit all two or three of your incoming lines.

There is a way to BOND thrughput but that is expensive and requires your ISP to play along.
 
aoakeley
Member Candidate
Member Candidate
Posts: 171
Joined: Mon May 21, 2012 11:45 am

Re: Merging Multiple Wans

Mon May 14, 2018 3:54 pm

The short answer is no if you think you can triple the speed or throughput of one connection.

Not necessarily. Get a VM somewhere close to your location, install RouterOS on it, the use EoIP to bond the connections.

https://www.duxtel.com.au/docs/presenta ... -EoIP.ppsx

If you have an AWS datacentre nearby, one of their Free Tier servers would be suitable.
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: Merging Multiple Wans

Mon May 14, 2018 8:17 pm

Not necessarily. Get a VM somewhere close to your location, install RouterOS on it, the use EoIP to bond the connections.
That's a clever idea which however needs some pre-requisites to be met. In most cases, even bonding of physical links does not aggregate the bandwidth of the links between the same two switches for a single connection, but rather tries to stick each connection to a single particular link. The motivation is to avoid overtaking of packets.

If all the slow links take a common physical path (same ISP, same access concentrator), their mean transport delay is likely to be the same, so the situation may be similar to the one with physical links. But aggregating several links provided by different ISPs is very likely to provide different delays and if they do, distributing packets belonging to the same stream over several such links will generate packet overtaking. For TCP, it is usually not a big deal, for e.g. RTP, it should not be either but some implementations cannot handle it properly.
 
User avatar
todayheads
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 79
Joined: Wed Jul 27, 2016 2:18 pm

Re: Merging Multiple Wans

Thu May 17, 2018 3:53 am

ok, thank you guys and its really nice ideas. I have another idea by splitting traffic

1- can I split traffic using DST Addresses for example traffic going to FB go through Wan3 and youtube go through Wan1

2- can I split traffic across multiple WANs depending on specific incoming ether not meaning for ex: all FB traffic goes through ether 4, youtube goes through ether 5 and etc
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: Merging Multiple Wans

Thu May 17, 2018 8:49 am

For this approach, the key is policy routing as described here.

For each routing mark you define a routing table which has a different WAN as a default route with highest priority = lowest value of distance parameter. You can combine it with tracking WAN availability as used in the WAN failover explained here.

Bear in mind that
  • by destination IP address you cannot tell youtube from other Google services, and telling them from one another by TLS-host is possible but too late for choosing a WAN.
  • many worldwide services use short-lived DNS answers to control load on individual servers, so you have to add the domain name (youtube.com) as an address to the address-list, which makes RouterOS dynamically create other items on the same list and keep them up to date by sending a new DNS query as the old answer expires. Needless to say that the clients must use Mikrotik as their DNS server to get the same responses

Who is online

Users browsing this forum: Bing [Bot], Google [Bot], johnson73, m1s3rys1gn4l, Thechriss and 121 guests