Routing

Hi folks,

Just started out with RIP. Was not able to find much info on the following points. Any help is appreciated. I have defined 2 RIP groups, both in the same routing instance:

root@rip-host-re0# show protocols rip
group rip-group1 {
    export advertise-routes-through-rip;
    neighbor et-2/0/25:2.0;
}
group rip-group2 {
    neighbor et-2/0/25:3.0;
}

1. Do we have a command to check RIP routes for each rip group? I believe the RIP routes will get added to the inet.0 table, but how do I verify which rip group does the route belong to? Found a reference to "show route protocol rip group rip-group1" cli command by chatgpt, however I don't see it on my device.
2. Is it possible to import routes from one group to another. I found 2 possible solutions:
   1. Define a policy and export it from group1
      1. set policy-options policy-statement EXPORT-TO-RIP2 term 1 from protocol rip-group rip-group1
set policy-options policy-statement EXPORT-TO-RIP2 term 1 then accept
         
      2. set protocols rip group rip-group1 export EXPORT-TO-RIP2
      3. Won't this just  re-advertise rip-group1 routes again via rip-group1? I don't see any references to rip-group2
   2. Define a polic and import from group 2
      1. set policy-options policy-statement IMPORT-TO-RIP2 term 1 from protocol rip-group rip-group1
      2. set policy-options policy-statement IMPORT-TO-RIP2 term 1 then accept
      3. set protocols rip group rip-group2 import IMPORT-TO-RIP2
      4. Will this be a more appropriate solution?

Thanks.

«rip-group rip-group1» is not a protocol :D

All RIP routes are going to the same inet.0 table (or yourvrf.inet.0).

Your best option is to add tags to incoming routes, with an inbound policy, by example then accept + then tag 10001 ; and match both protocol RIP and this tag for outgoing routes to another rip group (your group 2):

policy-statement rip-group2-export {
    term from-group1-rip {
        from {
            protocol rip;
            tag 10001;
        }
        then {
            accept;
        }
    }
    term default-deny {
        then reject;
    }
}