RIP on RoS 7.21.5 does not work as expected

RouterOS Forwarding Protocols
1

Hi all,

I know RIP does not widely used but still exist on RoS 7.x

I try RIP using 3 routers on lab environment with bus topologi (RoS 7.21.5)

R1 ----- R2 ----- R3

R1
/ip address
add address=192.168.1.1 interface=lo network=192.168.1.1
add address=10.1.1.1/30 interface=ether3 network=10.1.1.0
/routing rip instance
add afi=ip disabled=no name=rip-instance-1 redistribute=connected
/routing rip interface-template
add cost=5 disabled=no instance=rip-instance-1 interfaces=ether3
/system identity set name=R1

R2
/ip address
add address=192.168.2.1 interface=lo network=192.168.2.1
add address=10.1.1.2/30 interface=ether4 network=10.1.1.0
add address=10.1.2.1/30 interface=ether3 network=10.1.2.0
/routing rip instance
add afi=ip disabled=no name=rip-instance-1 redistribute=connected
/routing rip interface-template
add cost=5 disabled=no instance=rip-instance-1 interfaces=ether3,ether4
/system identity set name=R2

R3
/ip address
add address=192.168.3.1 interface=lo network=192.168.3.1
add address=10.1.2.2/30 interface=ether4 network=10.1.2.0
/routing rip instance
add afi=ip disabled=no name=rip-instance-1 redistribute=connected
/routing rip interface-template
add cost=5 disabled=no instance=rip-instance-1 interfaces=ether4
/system identity set name=R3

The result are:
* Router R1 and R2 know each other
* Router R2 and R3 know each other
* but R1 and R3 does not know each other

What could be wrong ?

Note: I try similar lab on RoS 6.49.20 and it works nicely; R1 and R3 well know each other.

P

3

the support ticket for this issue has been raised; #[SUP-221394]

4

Why in the world are you changing loopback (lo) from 127.0.0.1? I can't think of a single sane reason . . . Perhaps you meant to change the bridge IP?

5

on ROS 6.xx we do not have loopback interface so bridge without ports is the solution.

on ROS 7.xx mikrotik make interface lo as the replacement of bridge without ports.

loopback interface mostly used for OSPF, MPLS, i/eBGP, etc.

6

Maybe it's a Mikrotik thing, but queer as a 3 legged duck anywhere else . . . . Seems that if you want to route something, it would need to be on a real routable interface.

(I've used RIP for years, just not on a MikroTik, and generally it comes under "too dumb to break".)

7

yes, it's on the routerOS itself. they say that will fix this problem on next release.

at the moment, check redistribute-rip on the /routing/rip/instance of R2 to solve the problem while normally it should not.