I've recently added a PepLink Balance One to the mix as we are getting to more sites that can only provide slow DSL lines. While I know I can do the load balancing in the Mikrotik, since the WAN connections (and number) change every time we move, its too much work to write the queues, mangle rules and firewall rules every time we have a network topology change.
So the PepLink seemed like the best solution. It is doing well, but I feel that it isn't doing the best job balancing as it could as it only see's 1 client (the wan port on my Mikrotik). I still need to use my Mikrotik for DHCP / firewall etc, but is there a way to use the Peplink as my main gateway so that it see's all of my internal clients? Or am I asking for the impossible if I still want to use the Mikrotik for the mangle rules, speed Queue's and firewall?
I know that the real answer is probably that I should have bought one of the Peplinks that supposed "dropin" mode, but I was looking at price first and made a mistake.
So current setup (today)
Peplink -
10.168.222.1 with 3 DSL modems
Static reservation for my Mikrotik (10.168.221.20)
Static route for 192.168.222.0/23 to 10.168.221.20
Ether2-Wan is plugged to the Peplink
Relevant code snippets from the Mikrotik below. I've left out the mangle,queues, firewall as I assume they don't apply to the base need if its possible as I assume this is a NAT/route issue if it can be done?
I only care about the the PepLink seeing the 192.168.222.0/23 network on BR_DATA.
Code: Select all
[travis@BS NEW CORE] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK INTERFACE
0 192.168.222.1/23 192.168.222.0 BR_DATA
1 192.168.221.1/24 192.168.221.0 BR_VOIP
2 D 10.168.222.20/23 10.168.222.0 ether2-WAN
[travis@BS NEW CORE] /ip dhcp-server> print
Flags: X - disabled, I - invalid
# NAME INTERFACE RELAY ADDRESS-POOL LEASE-TIME ADD-ARP
0 Main_dhcp BR_DATA 222_Pool 30m
[travis@BS NEW CORE] /ip dhcp-server network print
# ADDRESS GATEWAY DNS-SERVER WINS-SERVER DOMAIN
1 192.168.222.0/23 192.168.222.1 192.168.222.1
[travis@BS NEW CORE] /ip firewall nat print
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=masquerade out-interface=ether2-WAN log=no log-prefix=""
[travis@BS NEW CORE] /ip route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADS 0.0.0.0/0 10.168.222.1 0
1 ADC 10.168.222.0/23 10.168.222.20 ether2-WAN 0
2 ADC 192.168.221.0/24 192.168.221.1 BR_VOIP 0
3 ADC 192.168.222.0/23 192.168.222.1 BR_DATA 0