HI First at all you should be sure that the networks that you are announcing in R5 are present in its rounting table. You can do this issuing the command "show ip route" and you should be able to see the two networks 192.168.0.80/28 and 192.168.0.96/28 directly connected. If you don't see one of the networks is because the port associated with the network is down, troubleshoot this problem first. If in fact you see both networks connected in R5's routing table, the next thing you should try is ping next hop  routers, if you can ping the next hop routers I'm sure you will be able to announce the directly connected networks to the surrounding routers. One thing that you shuold kno about RIPv2 is that RIPv2 perfoms autosummary at the mayor network boundary. ... View more

Hi Fabio: The first thing you must understand about peer-group is that they are a form to group a set of neighbors that have the same caracteristics applied. The peer-groups are local to the routers and you can declare diferents peer-groups in diferentes routers; for example you can aply the following configuration in R5 router bgp 65100 no synchronization bgp log-neighbor-changes neighbor other_peer_group peer-group neighbor other_peer_group  remote-as 65100 neighbor other_peer_group  update-source Loopback0 neighbor other_peer_group  next-hop-self neighbor 192.168.24.1 peer-group other_peer_group neighbor 192.168.25.1 peer-group other_peer_group neighbor 192.168.27.1 peer-group other_peer_group It doesn't matter if in R4 you declare the peer group internal wich is diferent to the peer group define in R5, R4 and R5 will be iBGP neighbors. What I'm trying to say here is that peer-groups is a way to group neighbors that have de same caracteristics applied; It is clear if you apply the same configuration in R5 without the use of peer-groups router bgp 65100 no synchronization bgp log-neighbor-changes neighbor 192.168.24.1 remote-as 65100 neighbor 192.168.24.1 update-source Loopback0 neighbor 192.168.24.1 next-hop-self ! neighbor 192.168.25.1 remote-as 65100 neighbor 192.168.25.1 update-source Loopback0 neighbor 192.168.25.1 next-hop-self ! neighbor 192.168.27.1 remote-as 65100 neighbor 192.168.27.1 update-source Loopback0 neighbor 192.168.27.1 next-hop-self As you can see here if you don't configure peer-groups the configuration is longer. Peer-groups are a form to group neighbors and don't have to be the same in all the router to become iBGP neighbors. ... View more