no pings whith PCC Load balancing

RouterOS Beginner Basics
1

Hi all

I am trying to load balance two ADSL connections here at home. I have followed a few guides from the internet however no matter what i tried when i open the ping tool (from routerOS) and ping 8.8.8.8 it fails with “no route to host”

When i also trying to ping the one ADSL Line (modem) it gets “timeout”

Also on my route list all defaults (0.0.0.0) are unreachable…

Any ideas?

My config is:

/interface ethernet
set 0 arp=enabled auto-negotiation=yes disabled=no full-duplex=yes  name=WAN1 
set 1 arp=enabled auto-negotiation=yes disabled=no full-duplex=yes  name=WAN2 
set 2 arp=enabled auto-negotiation=yes disabled=no full-duplex=yes  name=Local

/ip address
add address=192.168.0.1/24 network=192.168.0.0 broadcast=192.168.0.255 interface=Local
add address=192.168.1.2/24 network=192.168.1.0 broadcast=192.168.1.255 interface=WAN1
add address=192.168.2.2/24 network=192.168.2.0 broadcast=192.168.2.255 interface=WAN2

/ip dns set allow-remote-requests=yes cache-max-ttl=1w cache-size=5000KiB max-udp-packet-size=512 servers=221.132.112.8,8.8.8.8

/ip firewall mangle
add chain=input in-interface=WAN1 action=mark-connection new-connection-mark=WAN1_conn
add chain=input in-interface=WAN2 action=mark-connection new-connection-mark=WAN2_conn
add chain=output connection-mark=WAN1_conn action=mark-routing new-routing-mark=to_WAN1
add chain=output connection-mark=WAN2_conn action=mark-routing new-routing-mark=to_WAN2
add chain=prerouting dst-address=192.168.1.0/24 action=accept in-interface=Local
add chain=prerouting dst-address=192.168.2.0/24 action=accept in-interface=Local
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses-and-ports:2/0 action=mark-connection new-connection-mark=WAN1_conn passthrough=yes
add chain=prerouting dst-address-type=!local in-interface=Local per-connection-classifier=both-addresses-and-ports:2/1 action=mark-connection new-connection-mark=WAN2_conn passthrough=yes
add chain=prerouting connection-mark=WAN1_conn in-interface=Local action=mark-routing new-routing-mark=to_WAN1
add chain=prerouting connection-mark=WAN2_conn in-interface=Local action=mark-routing new-routing-mark=to_WAN2

/ip route
add dst-address=0.0.0.0/0 gateway=192.168.1.1 routing-mark=to_WAN1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.2.1 routing-mark=to_WAN2 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.1.1 distance=1 check-gateway=ping
add dst-address=0.0.0.0/0 gateway=192.168.2.1 distance=2 check-gateway=ping

/ip firewall nat
add chain=srcnat out-interface=WAN1 action=masquerade
add chain=srcnat out-interface=WAN2 action=masquerade
2

It would seem that the ping gateway is failing.
Try disabling that, and manually enabling one WAN link at a time to test each.
Once you know the setup is working right, other than the pings, then troubleshoot that.
If you had to fix something, try re-enabling the ping gateway test - maybe that will be fixed too.

3

Thanks for your comment. In the routes are unreachable (appart from the route of the wan ip of the interface).

I have tried disabling one WAN link and manually enabling the the other and it did worked, also the ping worked, but after a few seconds it got disabled by itself…!!

I re-anbled it and it showd route as reachable but then it got disabled by itself again!!!

Any ideas? Why is the route disabled after a few seconds?

Question, does PCC need a higher licence apart from level 3?

Thanks

4

No - you don’t need a license for PCC.

It sounds like your gateway is blocking pings. In your testing, did you turn off all possible gateway testing?
Use static only. If THAT is still failing, then you have something strange indeed going on.

5

No route to host, seems you dont have route to host. :smiley:
On PCC setups, usualy you havê 4 default routes, two for each upstream on main routing table and two on each routing table for PCC.

“/Ip Route print” should help US to help you.

6

I replied to a similar problem on a different thread. I think I realized why the problem is happening - try adding this to your configuration:

#make wan segments available in every routing table:
/ip route
add dst=192.168.1.0/24 gateway=WAN1 routing-mark=to_WAN1
add dst=192.168.1.0/24 gateway=WAN1 routing-mark=to_WAN2
add dst=192.168.2.0/24 gateway=WAN2 routing-mark=to_WAN1
add dst=192.168.2.0/24 gateway=WAN2 routing-mark=to_WAN2

I think your router is marking the ping tests with a route mark, and then the local WAN networks are not visible to the route marks… or pings are being forced out the wrong interface, etc…

Let both WAN networks be directly reachable regardless of PCC decisions.

7

I found the problem..after many hours of banging my head on the wall and pulling my hairs off…it was the dam ADSL/Router…it doesnt accepts pings…hence why routes where unreachable

8

Well, that just goes to show everyone - never forget to check the simple things, especially if you’re doing something more complicated.

Heh - it’s like that scene from Sling Blade when Carl looks at the tiller and immediately says “It ain’t got no gas in it.”

9

Hahaha yes indeed. I only figured out because i set up another MT box on another location and it was working fine so i thought it could br some sort of network issue. I then tried to ping from my laptop the gateway but i had no reply despite the fact i was online.

I then googled and saw that the specific ADSL modem does not accept pings and its a factory setting that cant change,

When i disabled the checks on the gateways it worked like a charm.

Thanks everyone for your help

10

You can look into recursive routing lookups as a workaround (and probably better) solution.

Force 8.8.6.6 via ISP 1, set mark_isp1 default GW to be 8.8.6.6 (in stead of adsl modem IP)
Force 8.8.6.7 via ISP 2, set mark_isp2 default GW to be 8.8.6.7 (in stead of adsl modem IP)

Ping these targets for up/down test - in fact, this also makes sure you can reach the Internet via the ISP, so if the ISP has an internal outage but your DSL line is still up, you would detect this condition and stop using that ISP.

One of the load balancing presentations at MUM USA 2012 did this, so you might check those slides for more specific details.

11

Zerobyte

Thanks alot for the help and for the information

Much appriciated