problem with routes and 2 pppoe on same gateway

RouterOS General
1

Hi i searched the forum but i couldn’t find a similar scenario so i decided to open a new thread.

till now i was using 2 adsl lines that connected via pppoe with load balancing via PCC without problems.

last week i tried to add a 3rd adsl line to my mikrotik server and when i add the new routes and the 3 pppoe are connected i don’t reach the local ip 192.168.9.1 anymore, as you can see on my images below when i disable the new route i begin to reach the mikrotik again.

i noticed that 2 of my pppoe are coming from the same gateway 200.63.148.37 and the new one is coming from a different one, maybe this is the problem?

reading mikrotik wiki i found this:

http://wiki.mikrotik.com/wiki/Manual:Load_balancing_multiple_same_subnet_links

but i don’t really know how to apply this to my scenario beacuse the routes for pppoe are automatically added whenn pppoe connects.


here i put the exports so you can see better my configuration:

[admin@Mikrotik] > ip address export
# jan/01/1970 21:11:52 by RouterOS 5.6
#
/ip address
add address=192.168.9.1/24 disabled=no interface=Clientes network=192.168.9.0
add address=192.168.10.2/24 disabled=no interface=speedy1 network=192.168.10.0
add address=192.168.11.2/24 disabled=no interface=speedy2 network=192.168.11.0
add address=192.168.12.2/24 disabled=no interface=speedy3 network=192.168.12.0


[admin@Mikrotik] > ip firewall nat export
# jan/01/1970 21:13:45 by RouterOS 5.6
#
/ip firewall nat
add action=masquerade chain=srcnat disabled=no out-interface=pppoe-out1
add action=masquerade chain=srcnat disabled=no out-interface=pppoe-out2
add action=masquerade chain=srcnat disabled=no out-interface=pppoe-out3


[admin@Mikrotik] > ip firewall mangle export
# jan/01/1970 21:12:34 by RouterOS 5.6
#
/ip firewall mangle
add action=mark-connection chain=input disabled=no in-interface=pppoe-out1 new-connection-mark=pppoe-out1_conn passthrough=yes
add action=mark-connection chain=input disabled=no in-interface=pppoe-out2 new-connection-mark=pppoe-out2_conn passthrough=yes
add action=mark-connection chain=input disabled=no in-interface=pppoe-out3 new-connection-mark=pppoe-out3_conn passthrough=yes
add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out1_conn passthrough=yes per-connection-classifier=both-addresses:3/0
add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out2_conn passthrough=yes per-connection-classifier=both-addresses:3/1
add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out3_conn passthrough=yes per-connection-classifier=both-addresses:3/2
add action=mark-connection chain=prerouting disabled=no dst-address-type=!local in-interface=Clientes new-connection-mark=pppoe-out1_conn passthrough=yes \
    per-connection-classifier=both-addresses:3/0
add action=mark-connection chain=prerouting disabled=no dst-address-type=!local in-interface=Clientes new-connection-mark=pppoe-out2_conn passthrough=yes \
    per-connection-classifier=both-addresses:3/1
add action=mark-connection chain=prerouting disabled=no dst-address-type=!local in-interface=Clientes new-connection-mark=pppoe-out3_conn passthrough=yes \
    per-connection-classifier=both-addresses:3/2
add action=mark-routing chain=prerouting connection-mark=pppoe-out1_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out1 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out2_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out2 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out3_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out3 passthrough=yes
add action=mark-routing chain=output connection-mark=pppoe-out1_conn disabled=no new-routing-mark=to_pppoe-out1 passthrough=yes
add action=mark-routing chain=output connection-mark=pppoe-out2_conn disabled=no new-routing-mark=to_pppoe-out2 passthrough=yes
add action=mark-routing chain=output connection-mark=pppoe-out3_conn disabled=no new-routing-mark=to_pppoe-out3 passthrough=yes


[admin@Mikrotik] > ip route export
# jan/01/1970 21:10:21 by RouterOS 5.6
#
/ip route
add comment=adsl1 disabled=no distance=1 dst-address=0.0.0.0/0 gateway=pppoe-out1 routing-mark=to_pppoe-out1 scope=30 target-scope=10
add comment=adsl2 disabled=no distance=1 dst-address=0.0.0.0/0 gateway=pppoe-out2 routing-mark=to_pppoe-out2 scope=30 target-scope=10
add comment=adsl3 disabled=yes distance=1 dst-address=0.0.0.0/0 gateway=pppoe-out3 routing-mark=to_pppoe-out3 scope=30 target-scope=10
add check-gateway=ping comment=adsl1 disabled=no distance=1 dst-address=0.0.0.0/0 gateway=pppoe-out1 scope=30 target-scope=10
add check-gateway=ping comment=adsl2 disabled=no distance=2 dst-address=0.0.0.0/0 gateway=pppoe-out2 scope=30 target-scope=10
add check-gateway=ping comment=adsl3 disabled=no distance=3 dst-address=0.0.0.0/0 gateway=pppoe-out3 scope=30 target-scope=10

thanks for any help and hope i don’t need to put my adsl modems on router mode or buying another mikrotik only for the new adsl line :S

2

i created this topic last week but it was approved today and i still have the same problem :S

3

Did nor see your ppp configuration hear, but sounds to me as though you default routes is enabled in PPPoE client. Disable them and create a default route manual and see what happens.

4

sorry i forgot to post the ppp configuration, but i’m not using default route on any of the pppoe interfaces, anything else i could do?

5

Remove this.

add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out1_conn passthrough=yes per-connection-classifier=both-addresses:3/0
add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out2_conn passthrough=yes per-connection-classifier=both-addresses:3/1
add action=mark-connection chain=output disabled=no new-connection-mark=pppoe-out3_conn passthrough=yes per-connection-classifier=both-addresses:3/2

Change this

add action=mark-routing chain=prerouting connection-mark=pppoe-out1_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out1 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out2_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out2 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out3_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out3 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out1_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out1 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out2_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out2 passthrough=yes
add action=mark-routing chain=prerouting connection-mark=pppoe-out3_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out3 passthrough=yes

to this

add action=mark-routing chain=prerouting connection-mark=pppoe-out1_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out1 passthrough=no
add action=mark-routing chain=prerouting connection-mark=pppoe-out2_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out2 passthrough=no
add action=mark-routing chain=prerouting connection-mark=pppoe-out3_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out3 passthrough=no
add action=mark-routing chain=prerouting connection-mark=pppoe-out1_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out1 passthrough=no
add action=mark-routing chain=prerouting connection-mark=pppoe-out2_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out2 passthrough=no
add action=mark-routing chain=prerouting connection-mark=pppoe-out3_conn disabled=no in-interface=Clientes new-routing-mark=to_pppoe-out3 passthrough=no