ROS v.4 routing problem

Hi,
I upgraded one of our RB600 (Router 1) to the ROS v. 4 (4.4 and then 4.5). After several hours (minutes) it stops routing data to the clients (networks) which are not directly connected to it (with an exception of default route which always works). In the routing table (ip routes) it says that gateway is unreachable. With 3.30 everything works fine. My setup is following:

Router 1   ----   Router 2   ---   clients
(RB 600)          (Mikrotik)
reachable         reachable       unreachable
     |
     |
     |
 clients
reachable

Is it a bug?

Petr

Are you using OSPF, RIP, static routes, or what?

All routes are static.

Any ideas?

all links are wired and at the time when unreachable clients are unreachable , does networking work for them?

Any additional configuration, like, metarouter or something on the routers?

  1. All links are wired and networking does not work for unreachable clients (networks)
  2. No special configuration on routers - only routing with firewall and traffic shaping

Petr

can you post routing information on your Router2, since there lies the problem, because as you say, when clients dirrectly behind router1 still can use resources, while users behind router2 cannot.

Hi,

clients on router2 are connected either directly (gateway is on interface on router2) or through static route - this is same as on router1.

I don’t think, that the problem is on rotuer2, because:

  1. When I looked in Winbox to the routing table on router1 all (static) routes to the other router (router2) were blue (and unreachable), but router2 itself was reachable
  2. When I reset the router1 it started to work again for some time (several minutes/hours)
  3. Since I downgraded router1 back to the ROS v.3.30 it has been working without problem

Petr

So router2 was pingable from router1, but router1 said that router2 was unreachable in the routing table entries (until you rebooted router1?)

Was the check gateway thing set to arp, ping, or not enabled?

Check gateway was not enabled.

You could try adding a logging category of route,debug and see if anything shows up in the log.