RIP routes ignored

RouterOS General
1

I want to propagate some simple routes on my network so configured RIP. With wireshark, I can see the RIP routes being multicast to 224.0.0.9, and in Torch, I can see the rip traffic. All traffic is allowed on that interface but no routing updates are imported. I turned on rip debugging but don’t see anything in the log. Here’s my configuration:

/routing rip export
/routing rip
set distribute-default=never garbage-timer=2m metric-bgp=1 metric-connected=1
metric-default=1 metric-ospf=1 metric-static=1 redistribute-bgp=no
redistribute-connected=no redistribute-ospf=no redistribute-static=no
routing-table=main timeout-timer=3m update-timer=30s
/routing rip interface
add authentication=none authentication-key=“” disabled=no in-prefix-list=“”
interface=all key-chain=“” out-prefix-list=“” passive=no receive=v1-2 \

Am I missing something obvious?

2

You don’t have any option set to distribute routes.
For example to distribute connected routes set redistribute-connected=yes

3

I don’t want to distribute the routes, I just want mikrotik to know about them. It’s the default gateway for everything so doesn’t need to distribute any routing information.

4

?? How could other router will know about the routes if they are not distributed? And if you have default gateway for everything and do not want any other routes, then why RIP is needed?

5

Let’s say I have the mikrotik with interface ether1 and address 192.168.1.1/24
I have a router with eth0 as 192.168.1.2/24 and eth1 as 192.168.2.1/24
I turn on RIP on the router so that it tells the mikrotik the route to 192.168.2.0/24

On the mikrotik I should now be able to ping 192.168.2.1 once it learns of the RIP route.

Is that not how it should work?

6

OK. Try to force RIPv2. On mikrotik you can do it in RIP interface configuration.

7

Tried that, no difference. I also tried adding a firewall rule specifically to allow traffic from port 520 and although I see the traffic in Torch, I don’t see any in the firewall counters. It seems like it’s not listening to multicast traffic. I should add this is on 5.0b6.

8

I decided to try rip v1 too. Now it’s broadcasting instead of multicasting, the firewall filter (accept) is seeing the packets, but still no updated routes listed. RIP is now configured to receive v1-2

9

Solved. Damn! I had to add a network in /routing rip network. I presumed the interface was sufficient. Thanks for your help.

10

If interface and rip neighbor is set up then network is not required, otherwise yes you need network.