Reference Notes:
Mikrotik is a very powerful router that can perform variety of functions in one box. It’s fun to do complex configuration with customized scriptings to achieve our desired results. Just wanted to share some thoughts on one scenario where we used multiple wan links and use it one router and have done routing+natting all together. Later we added failover so that if pcc wan links fails it should switch to fiber link, and if fiber link fails, it should failover to dsl.
Mikrotik have 4 DSL links which are configured in PCC (Load balancing) and serving local pppoe clients.
We have added another WAN Link via Fiber which is 1 STM (155mbps) and have acquire another large public pool for users which is routed to our /29 ip on mikrotik.
We have configured services in such a way that normal users gets private ip upon pppoe connectivity, and goes via PCC/Natting. and few services are configured in such a way that user gets public ip and goes to internet via public ip Routing, (bypass natting, preserving his public ip)
We have configured VLANs to isolate the different areas/networks to minimize the broadcast and for better network management.
We need to connect some corporate clients, which of course should not be connected via pppoe method, they want direct public ip that they can configure in there own router/system. So we do it by connecting that client on our vlan switch, and on mikrotik we add new vlan interface (accordingly ) and assign public ip (as required like /30) and assign it to this new vlan interface, and give appropriate ip to the client.
We have configured FAILOVER by using following techniques
4 vdsl links are configured as PCC. For fail over we are using script that monitor 2 internet hosts for each wan link. we have also created forced route for those hosts with black holes as well to make sure the hosts goes via specific wan link only. once the script failed to ping those 2 hosts, it will simply enable rule in (ip/route/rules) TABLE to lookup the speciifc wan marked packets via main table where fiber link have distance value of 1 which will be default rule. thus traffic for that failed dsl link will start natting via fiber link. of course there are various other measurements need to be done, like proper natting rules, etc.
For fiber fail over (public ips) to dsl, we have script that checks for 2 hosts, if it fails, it will simply add the public ip pool to pcc pool as well, so the public pool also starts mixing with the pcc quern😀
CCR performed amazingly good with complex configuration , lots of dynamic queues, and CPU usage usually remains under 10%. We can use PCQ base queues to lower the cpu usage in specific circumstances.
Regard’s
JZ
Filed under: Mikrotik Related
