Load Balancing 2 Isp Mikrotik Full Based On

This is very much important to know the load balancing method between 2 isps.

There are many ways to configure the Load balancing between 2 wan link.But here i am going to show a simple way to make it configure.

Also, because one of my links uses dynamic public IP, I modified the DynDNS update script to insert the obtained address and gateway into the lokal address-list. That it. Reply Delete Replies Reply Unknown June 18, 2014 at 8:02 PM Nice Work Thanks Reply Delete Replies Reply Unknown June 27, 2014 at 8:58 PM Hello, I am using above script for PCC with webproxy.

During this time many of us who think wrong, that by using loadbalance two connection lines, the large bandwidth that well get double the bandwidth before using loadbalance (accumulation of both the bandwidth).

This needs to be clear first, that loadbalance will not add much bandwidth we get, but only served to divide the traffic from both the bandwidth so they can be used in a balanced manner.

With this article, we will prove that the use of mathematical formulas loadbalancing does not like 512 256 768, but 512 256 512 256, or 512 256 256 256 256.

In this article we use RB433UAH with conditions as follows: Ether1 and ether2 connected to different ISPs with large bandwdith different.

If you use DNS from one of your isp, then there will be additional mangle shall we give sign of thickness After pengkonfigurasian IP and DNS are correct, we must pair the default route to each of our ISP gateway IP for the router to forward all traffic that does not connect him to the gateway.

Here we use feature check-gateway and gateway is useful if one of us dropped out, then the connection will be diverted to other gateways.

In the next example, we will use the usb flash is attached to a USB slot.

For the first time installation, this additional storage will be read status invalid in the system store.

To be used as storage media cache, then the storage must be formatted in advance and activated Later we live webproxy activate and set the cache-on-disk yes to use our storage media.

With the PCC we can categorize traffic or outgoing connection through a router entry into several groups.

These groupings can be distinguished on the basis of src-address, dst-address, src or dst-port and-port.

The router will remember the beginning of the path through which the traffic gateway connections, so that the subsequent packets that are still associated with the connection initially will be passed on the same gateway route.

The advantages of this PCC is to answer many complaints often break the connection on the other loadbalancing techniques prior to the PCC because of the displacement gateway.

Before making mangle loadbalance, to prevent routing loops in the traffic, then all client traffic to the networks that connect directly to the router, should we bypass the loadbalancing.

We can make a list of IP that are still in a network router and install the first time following mangle ip firewall address-list add address192.168.101.030 listlokal add address192.168.102.030 listlokal add address10.10.10.024 listlokal ip firewall mangle add actionaccept chainprerouting dst-address-listlokal in-interfacewlan2 commenttrafik lokal add actionaccept chainoutput dst-address-listlokal In certain cases, the first traffic can come from the Internet, such as the use of remote Winbox or telnet from the internet and so, therefore we also need to mark the mark-connection traffic so that traffic can pass through it also the interface where the incoming traffic.

If you are using a public DNS independent, such as OpenDNS, you do not need a mangle below.

To be more structured and easier in the reading, we will use custom-chain as follows: ip firewall mangle add actionjump chainprerouting commentjump to client-lb connection-markno-mark in-interfacewlan2 jump-targetclient-lb add actionjump chainoutput commentjump to lb-proxy connection-markno-mark out-interfacewlan2 jump-targetlb-proxy In the mangle above, to make sure the client loadbalance traffic parameters in-interface is the interface that is connected with the client, and for traffic loadbalance webproxy, we use the output chain with out-interface parameters which are not connected to the interface client.

After a custom chain for loadbalancing made, we can create custom mangle in the following chain.

Because we are a different ISP traffic (512kbps and 256kbps), we divide the traffic load into 3 parts.

ISP1 gateway, and a final section will pass through the gateway ISP2.

If the traffic of each client and proxy is selected, the next step we need to create mangle mark-route to be used in the routing process will.

Here we will also make a backup routing, so that if a gateway is lost, then all connections will go through gateways that connect each.

From this test looks can be concluded that 512kbps 256kbps 768kbps Note: Load balancing using this PCC technique will be effective and balanced approach when more and more connections (from clients) that occurred.

Load Balancing 2 Isp Mikrotik Full Based On

Congratulations I made some adaptations for my scenario, full based on this post.

Also, because one of my links uses dynamic public IP, I modified the DynDNS update script to insert the obtained address and gateway into the lokal address-list.

That it. Reply Delete Replies Reply Unknown June 18, 2014 at 8:02 PM Nice Work Thanks Reply Delete Replies Reply Unknown June 27, 2014 at 8:58 PM Hello, I am using above script for PCC with webproxy.