<div dir="ltr"><div>My 2c</div><div><br></div><div>On MikroTik gear the optimal ways to do this sort of load balancing (with reference to Ross's situation) are:<br></div><div>a) src based static routing (send VoIP vlan/ip-range via Link1, send Office PC vlan/ip-range via Link2)</div>
<div>b) PCC based load-balancing (for 1 new connection-pair [based on src & dst ip] send this out connection 1, next out 2, next out 1, next out 2)</div><div><br></div><div>There's older methods and more complex ways of going about it but these are the 2 *best ways about it.</div>
<div><br></div><div>The PCC is best for balancing out over equal speed links and sharing available bandwidth.</div><div><br></div><div>The src based is good for controlling the bandwidth and performance of a given service type/group by explicitly defining what is allowed to go out where (IE: voip should go out this 512k/512k L2 service by default and fail over to a VPN path out the ADSL service)</div>
<div><br></div><div>Based on what you've asked Ross, I don't see any reason this would be a problem provided properly resourced devices are spec'd.</div><div><br></div><div>Lastly: it's worth noting that this is all "Load-balancing" vs "Aggregation". </div>
<div>Aggregating services would normally require an additional central point to spit out the service at the other end, back out to your Layer3 link.</div><div><br></div><div>*IMO</div><div><br></div><div>Cheers,</div><div>
Andrew</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 18 June 2014 13:30, Matt Ayre <span dir="ltr"><<a href="mailto:matt.ayre@bigair.net.au" target="_blank">matt.ayre@bigair.net.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Re "out of order segments", that is why pretty much all modern platforms include L3/L4 data points for flow hashing, whether routing/forwarding or bundle load balancing. <div>
<br></div><div>Even eeek MikroTik ;)<div>
<br></div><div><div>Cheers,</div><div>Matt</div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 18 June 2014 11:50, John Gavrilita <span dir="ltr"><<a href="mailto:jgavrilita@thesummitgroup.com.au" target="_blank">jgavrilita@thesummitgroup.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ross,<br>
The first thing that crossed my mind is the inevitable situation when packets will arrive out of order because the designed solution uses bandwidth aggregation / load balancing. For TCP it's ok, but for UDP it'll be a nightmare and the users will literally hear it.<br>
Mikrotik is a nifty platform, and as with any other device, one has to know how to cook it.<br>
Cheers :)<br>
<br>
<br>
<br>
<br>
<br>
John Gavrilita<br>
Network Engineer<br>
<br>
Summit IT Management | Summit Internet | Summit Creative - ‘reach your peak’<br>
Divisions of The Summit Group (Australia) Pty Ltd<br>
<br>
Phone (Australia): <a href="tel:1300%20049%20749" value="+611300049749" target="_blank">1300 049 749</a><br>
Phone (US & Canada): <a href="tel:%28321%29%20216%203844" value="+13212163844" target="_blank">(321) 216 3844</a><br>
E-mail: <a href="mailto:jgavrilita@thesummitgroup.com.au" target="_blank">jgavrilita@thesummitgroup.com.au</a><br>
Internet: <a href="http://www.thesummitgroup.com.au/" target="_blank">http://www.thesummitgroup.com.au/</a><br>
Address: Level 1, 39 Railway Road, Blackburn VIC 3130<br>
Postal: P.O. Box 3225, Doncaster East VIC 3109<br>
<div><div><br>
-----Original Message-----<br>
From: AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net" target="_blank">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Ross Wheeler<br>
Sent: Wednesday, 18 June 2014 11:04 AM<br>
To: <a href="mailto:ausnog@lists.ausnog.net" target="_blank">ausnog@lists.ausnog.net</a><br>
Subject: [AusNOG] Mikrotik routers and "VLAN trunking over WAN"<br>
<br>
<br>
Looking for someone with Mikrotik experience to confirm which devices (any? all?) might achieve the desired outcome here.<br>
<br>
Basically there are a number of sites of varying sizes, but for the purposes of argument, lets say 20 sites.<br>
<br>
Most sites are proposed to have at least two diverse paths. These could be ADSL, Microwave, 3G/4G/LTE etc. The point is, different providers, different paths.<br>
<br>
Each site has it's (n) paths connected to interfaces on a Mikrotik router which can aggregate bandwidth across (n) links (and reduce latency<br>
somewhat) while providing an ability to withstand (n-1) link failures.<br>
<br>
The user further intends making extensive use of VLANs to "isolate"<br>
services (eg, phones, computers, security devices, "public" devices etc).<br>
Thus it would be entirely likely that there could be 40 switches at 20 sites, each with <a href="http://10.10.8.0/22" target="_blank">10.10.8.0/22</a> for "phones" all on VLAN8.<br>
<br>
Not withstanding how YOU might do it, is there an intrinsic problem with the design (or Mikrotik as the each sites 'edge device') as it stands?<br>
<br>
Thanks in advance,<br>
RossW<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br></blockquote></div><br></div>