Pingable Static route unreachable. I'm baffled.

Simp · August 9, 2012, 5:29pm

I'm new at RouterOS, but I'm learning. Unfortunately I'm stumped.

I've got an RB750G with OS v5.15. It has 4 interfaces currently configured.
1_HTC, 3_TWC, 4_RMC, 5_Conway

The 4_RMC is the interface I'm interested in in this case. It's ip is 10.34.17.44 and belongs to the 10.34.17.32/27 subnet.
There is another router on this subnet at 10.34.17.62

I need to add a static route for 10.34.33.0/24 through my 10.34.17.32/27 subnet to 10.34.17.62.

I can ping 10.34.17.62 no problem. But when I add a static route, Winbox lists the route as unreachable?!?
And the terminal won't show it as active (but doesn't show unreachable. I haven't figure that out either.)

======================================================================================

[admin@MikroTik] /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 A S 10.34.17.32/27 4_RMC 1
1 S 10.34.33.0/24 10.34.17.62 1
2 A S 192.168.1.0/24 1_HTC 1
3 A S 192.168.41.0/24 5_Conway 1
4 A S 192.168.200.0/24 3_TWC 1
5 ADC 255.255.255.0/32 192.168.41.3 5_Conway 0
3_TWC
1_HTC
6 ADC 255.255.255.224/32 10.34.17.44 4_RMC 0

======================================================================================

I've got some NAT stuff in the firewall as well, listed below. But I've disabled all the NAT rules and still the static route lists as unreachable.

======================================================================================

[admin@MikroTik] /ip firewall nat> print
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=src-nat to-addresses=10.34.17.44 dst-address=10.34.0.0/16 out-interf

1 chain=srcnat action=src-nat to-addresses=10.34.17.44 dst-address=10.39.0.0/16 out-interf

2 chain=dstnat action=dst-nat to-addresses=192.168.1.3 dst-address=10.34.17.44 in-interfac

3 chain=dstnat action=dst-nat to-addresses=192.168.1.3 dst-address=192.168.41.3 in-interfa

4 chain=dstnat action=dst-nat to-addresses=192.168.1.3 dst-address=192.168.200.250 in-inte

Any ideas? What am I doing wrong?
Can the router not figure out how to get to 10.34.17.62? Is there something else I should be adding somewhere?

Thanks,
Donald

biomesh · August 9, 2012, 5:38pm

Have you tried to set the preferred source on the 10.34.33.0/24 subnet to 10.34.17.44?

Could there also be a routing issue on the router at 10.34.17.62? It should of course be able to respond to pings, but might not route between subnets properly.

Simp · August 9, 2012, 5:40pm

Yep. No difference unfortunately.

Feklar · August 9, 2012, 6:54pm

Is 10.34.33.0/24 or any larger subnet that contains that subnet local to the router? If so, the local route will always have a smaller weight.

Simp · August 9, 2012, 7:47pm

@Feklar:
Nope (although that shouldn’t make the route unreachable, just unpreferred, correct?)

10.34.33.0/24 is actually 3 hops away through the network.

I have 3 - 192.168.x.x/24 networks local to the RB750G and the 10.34.17.32/27 network which links to 10.34.17.62 router.

@Biomesh:
True, but if it can ping it shouldn’t show unreachable, just fail to route, correct?
And I actually do know that it can route successfully. In testing I replaced the router interface with a PC.
Used same IP and set gateway of PC to be 10.34.17.62. Can ping and tracert 10.34.33.0/24 network successfully with PC, so routing appears fine.

Since router itself can successfully ping 10.34.17.62, I guess the real question is what case(s) would make the Mikrotik mark the route as unreachable?

Thanks guys for the time on this,
Donald

psamsig · August 9, 2012, 9:38pm

6 ADC 255.255.255.224/32 10.34.17.44 4_RMC 0

The IP adress for this interface 4_RMC is configuret wrong, someone put a netmask (and that is almost never used in RouterOS) as network.

This is how it is now:

/ip address add address=10.34.17.32/32 interface=4_RMC network=255.255.255.224

this is how it should have been:

/ip address add address=10.34.17.32/27 disabled=no interface=4_RMC network=10.34.17.32

On second though, all adresses seems to be configured in that way.

Simp · August 10, 2012, 1:47am

Those are dynamic routes. I didn’t add those.

…Though you are right, it is a bit strange.

Not sure I’ll be able to change those, but it is worth taking a look at.
I’ll try to take a closer look at it tomorrow.

Donald

Simp · August 10, 2012, 2:07pm

The enigma grows.

It isn’t just the 10.33.17.62 gateway that is unreachable.
It is ANYTHING that is an IP. Any IP I put in as the gateway is unreachable.
Even the IP address of one of the Mikrotik interfaces is unreachable. I can use the name of the interface, but not the IP address.
If I don’t use an interface name for the gateway, it is declared unreachable.

I simply must be doing something wrong here.

Donald

Simp · August 10, 2012, 2:25pm

Thanks guys for the time. And thanks especially to you psamsig!

You got me started in the right direction. Looks like nothing is wrong with the static routes. It’s the interfaces’ ip addresses. I entered them wrong and thus had the bad masks in the routes.

Thanks again psamsig for the spot. I karma’d you.

Just for future reference, or anybody tracking this post for answers…
in the IP Address List for the interfaces, put the ip address of the interface and the decimal notation of the mask… i.e. 192.168.1.1/24 in the address list box.
Leave blank the network. Winbox will auto fill it. Same thing for command line. I misunderstood the network box to be the subnet mask but it is instead looking for the actual network, e.g. 192.168.1.0. This is why I had screwy results in the dynamic routes. I had /32 networks on the interfaces and network masks for the network IDs.

Static route works now. Thanks again guys.

Donald