@ cbrown
I see the difference but am not sure personally with one would be better.
currently the setup seems to be tracking connections and then making sure that they go out through the same place they came in.
Here is the code for it.
/ ip firewall mangle
add chain=prerouting in-interface="Internet-Dale" connection-mark=no-mark action=mark-connection new-connection-mark=Dale_conn
add chain=prerouting in-interface="Internet-Richmond" connection-mark=no-mark action=mark-connection new-connection-mark=Richmond_conn
add chain=prerouting in-interface="Internet-Firestop" connection-mark=no-mark action=mark-connection new-connection-mark=Firestop_conn
add chain=prerouting in-interface=Bridge connection-mark=no-mark dst-address-type=!local per-connection-classifier=both-addresses:3/0 action=mark-connection new-connection-mark=Dale_conn
add chain=prerouting in-interface=Bridge connection-mark=no-mark dst-address-type=!local per-connection-classifier=both-addresses:3/1 action=mark-connection new-connection-mark=Richmond_conn
add chain=prerouting in-interface=Bridge connection-mark=no-mark dst-address-type=!local per-connection-classifier=both-addresses:3/2 action=mark-connection new-connection-mark=Firestop_conn
add chain=prerouting connection-mark=Dale_conn in-interface=Bridge action=mark-routing new-routing-mark=to_Dale
add chain=prerouting connection-mark=Richmond_conn in-interface=Bridge action=mark-routing new-routing-mark=to_Richmond
add chain=prerouting connection-mark=Firestop_conn in-interface=Bridge action=mark-routing new-routing-mark=to_Firestop
add chain=output connection-mark=Dale_conn action=mark-routing new-routing-mark=to_Dale
add chain=output connection-mark=Richmond_conn action=mark-routing new-routing-mark=to_Richmond
add chain=output connection-mark=Firestop_conn action=mark-routing new-routing-mark=to_Firestop
/ ip route
add dst-address=0.0.0.0/0 gateway=192.168.105.52 routing-mark=to_Dale check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.105.62 routing-mark=to_Richmond check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.105.58 routing-mark=to_Firestop check-gateway=ping
/ ip firewall nat
add chain=srcnat out-interface="Internet-Dale" action=masquerade
add chain=srcnat out-interface="Internet-Richmond" action=masquerade
add chain=srcnat out-interface="Internet-Firestop" action=masquerade
Internet-Dale, Internet-Richmond and Internet-Firestop are my three incoming PPTP's ...
This setup works well ... Right up until what cyberT said.
Secure Banking sites break ...
I think if i understand this correctly I am tracking connections here?
I basically just used your link from earlier cbrown and made it work for me.
@CyberT
My lines are all through our south african DSL provider telkom. The accounts on those lines are all through a single provider aswell.
Please tell me if i am wrong but for mlppp i would need to EoIP tunnel to each router attached to the DSL Modems and then set up a mlppp. Is that about right?
The reason I am going with the load balancing is because everything comes to my central HO and then out from there and so a single line at a time is not only a waste but gets maxed out pretty quickly.
Please let me know what you guys think ...