Problem with RIP routing

Hi,

I’m trying to setup very simple RIP setup with 2 routers and only few subnets (yes, I can do it with static routes and it works, but I really want to know what is wrong in this anyway). My setup is kind of one-direction setup, where another router (router1) sends static-routes & connected-routes and another is in passive mode (router2), just receiving the routes and adding them to its own routing table.

So far so good, I can see routes coming:


[admin@router2] > /routing rip route print
Flags: C - connect, S - static, R - rip, O - ospf, B - bgp
 #   DST-ADDRESS        GATEWAY         FROM                METRIC
 0 R 1.1.1.0/24                         192.168.1.10             2
 1 R 192.168.2.0/24                     192.168.1.10             2
 2 R 192.168.4.0/24                     192.168.1.10             2

..And I can also see routes in main routing table:

[admin@router2] > 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
 2  Dr  1.1.1.0/24                         192.168.1.10            120
11  Dr  192.168.2.0/24                     192.168.1.10            120
12  Dr  192.168.4.0/24                     192.168.1.10            120

The problem is that actual routing is not working anyway. Packets never reaches the target because they are still routed via router2’s default route to another direction.

I have a feeling its something to do with that fact that GATEWAY column is empty in upper printout and DISTANCE is definitely too big in lower printout (although it shows gateway-address as it should be), but what can I do for that?

Both routers are running ROS6.9.

Sorry about scrappy explanation, but maybe someone understood what is my problem and how can I fix it. :slight_smile:

I had a similar problem as you. I run a RIP protocol bringing in about 65~ routes (That change weekly, hence wanted dynamic not static routing). It is passive mode with this router just receiving the routes and not handing back.

It was working great for many months, then after my first upgrade to 6.9 it completely stopped working in the way you describe. Routes would load into the table but not become active. Nothing seemed different and I even compared to previous backups. I tried stopping/starting RIP many times but couldn’t find a cause.

I then rebooted the router again after a while, and on its fresh boot the routes installed fine.

For peace of mind, this is a few of the routes received by RIP that are now working:
[admin@home] > /routing rip r p
Flags: C - connect, S - static, R - rip, O - ospf, B - bgp

DST-ADDRESS GATEWAY FROM METRIC TIMEOUT

0 R 10.0.3.0/24 192.168.68.1 2 2m39s
1 R 10.1.0.0/16 192.168.68.1 2 2m39sNotice the GATEWAY is empty, as it defaults to the router it received the route FROM (GATEWAY would be filled if it is reflecting a different router for you).

And the now active routes:
[admin@home] > /ip r p
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

2 ADr 10.0.3.0/24 192.168.68.1 120
3 ADr 10.1.0.0/16 192.168.68.1 120

Hmm.. Thank you, reboot solved my case too. First I rebooted only sending router (router1), but it didn’t help. Then I rebooted receiving one (router2) too, and that made the trick.
Sounds like a bug in ROS6.9?

Mine only occurred on first boot from upgrade. Likely is some type of bug, but easy fix with a reboot so unlikely to be high priority.