PCC Problems w/ quasi/pseudo connection states

Hello, I have 8 lines I’m using PCC on to balance/share the bandwidth. They seem to work well until my ISP has issues w/ a line (more common then not these days). The issue I’m having is the line’s don’t go completely down, you can ping the gateway, just not get anywhere, so the normal “ping-gateway” check that happens on the PCC stuff doesn’t do the trick, line appears “up” even tho its not.

How i can set this up so it pings something else and disable it if it can’t ping it?

TIA

Make a NetWatch item that pings something further down the chain and on down disables the routes with the associated routing marks. Since it’s router generated traffic it won’t be affected by the PCC routing marks and will just use the normal routing table, so you can make /32 routes to the ping targets via the gateways you need to test.

That’s where you lose me..

Let’s say you have two circuits balanced via PCC. 1.1.1.2/30 (gateway 1.1.1.1) and 2.2.2.2/30 (gateway 2.2.2.1). You want to ping test further down the line than just the gateway. You pick 8.8.8.8 for monitoring for the first circuit, and 9.9.9.9 for the second circuit.

To force traffic out via a specific circuit when testing you just add a route for the IPs you are testing as host addresses, and use the appropriate gateway:

/ip route
add dst-address=8.8.8.8/32 gateway=1.1.1.1
add dst-address=9.9.9.9/32 gateway=2.2.2.2

That way the router only tests via those specific circuits.

Ahh, I know the concept, just the /32 was throwing me off. (relatively new to all the subnet stuff)

Thanks, will give it a shot
**
edit
I’m amusing I’ll need to do some scripting to enable/disable routes?

Hi Fewi

Trying to do the same but was wondering. If the ip can’t be reached through the specified route, wont it fall back to the default route and ping the ip any way?