Configured RIPv2, but still can not ping to the other networks

[CireNozid6382]

I have 3 different offices which comprises of vlans. I have successfully made the rips through the routers, but when I try to ping from one office to another, I somehow can't.

[Georg Pauwen]

Hello,

there were numerous issues with your configuration:

1. The links (FastEthernet0/24) on the yellow and green switches were not configured as trunks

2. The WesternOffice router did not announce the 192.168.5.0 network

3. The IP addresses of the DHCP servers were identical with those of the default gateways

I changed your configurations, please review the attached lab...

[luis_cordova]

Hi @CireNozid6382 ,

I'll show you the changes you should make:

yellow switch

Switch(config)#interface fastEthernet 0/24

Switch(config-if)#switchport mode trunk

WesternOffice router

Router(config)#router rip

Router(config-router)#network 192.168.5.0

green switch

Switch(config)#interface fastEthernet 0/24

Switch(config-if)#switchport mode trunk

all servers

ip address 192.168.X.3 -> the IP .1 corresponds to the gateway, so it can not be used in another device

After those little changes, everything looks ok

Regards

[Edwin Portillo]

Hi friend,

Effectively you need to truncate ports fa0/24

Switch0<--->WesternOffice
Switch1<--->NorthernOffice

interface fa0/24

switchport mode trunk

In addition, you must add the 192.168.5.0 network to RIP in router WesternOffice

WesternOffice<--->NorthernOffice

router rip

net 192.168.5.0

You are using subinterfaces and there you have defined an ip address that serves as a gateway for all the devices that connect to that vlan, for example on the NorthernOffice router:

If you see on the PC5 that this VLAN is connected, it has defined the address 192.168.30.1 as the gateway and the IP 192.168.30.2 via DHCP.

The subnet mask is / 24 which determines that there are only 256 addresses available, removing ID and BROADCAST only assignable 254:

ID	CIDR	MASK	RANGE	BC
192.168.30.0	/24	255.255.255.255.0	192.168.30.1 - 192.168.30.254	192.168.30.255

See what you have assigned: 192.168.30.1 which is the same address as the gateway.

If it realizes within the assignable range, it has already used 192.168.30.1 in the fa0/0.10 interface that serves as the gateway for VLAN 10 and the PC5 that is connected in the range of the ports of that VLAN has the address 192168.30.2 from that address you can assign up to 192.168.30.254.

As @luis_cordova say, that revision must be done on the servers and that's where you entered the address manually.