The description of RIP functionality in Mikrotik manual is precise but I didn’t believe it first. The /routing rip network items do not define networks that should be advertised but those in which RIP should run. I believed it is not that bad but I was wrong.
Now the problem is that you’ve said before that every time you get a new PPPoE connection established, the address at your end changes; is this the case also for the remote address or the remote address remains the same? Try several disconnections and reconnections and if the remote address you get is always the same, it will be a bit simpler, because it is the remote address of the PPPoE interface which must match the /routing rip network item. So if it is stable, remember it.
And it would be fine if both of you (@Najifares and @rabienz) could compare the results - if the address is stable, whether both of you get the same one.
So before I ask you for a Teamviewer ID and pin, try the following:
/routing prefix-lists add chain=output prefix=77.42.216.32 prefix-length=29 action=accept
/routing prefix-lists add chain=output prefix=0.0.0.0 prefix-length=0 action=drop
/routing rip interface set [find interface=pppoe-out1] out-prefix-list=output
/routing rip set redistribute-connected=yes
/routing rip network print
/routing rip network remove 0
Now depending on whether the remote address on the PPPoE connection is stable or changes, choose one of the following:
- if it is stable, use /routing rip network add network=the.remote.address/32
- if it is changing, use /routing rip network add network=0.0.0.0/0 and we shall deal with some minor consequences later on.
In any of the two cases, at this moment your 'Tik should start talking with ISP’s network using RIP. So provide again the output of the four /routing rip … print commands, and also of /routing prefix-lists print.