Router RIP ???????

Gang,

I have a bisic coniguration for routing rip but when I do a sh ip route rip or sh ip route the table is empty as far as rip (R) updates go. I thought I would except to show R on the route table as the networks are connected. When I looked at the debug, shown below, and see that the e0 is sending but the receiving updates are getting suppressed ...null update. I cant figure out why this is happening can anyone put some light on the subject. Also the routing table below just shows the networks connected, networks on each router....router a and router b. See the show run below ios 12.x for all routers.

I did not give the other router's config as the are the same except for the ip address which is 192.168.0.100 /24 on the othe routers e0

Router A

iterface Ethernet0 ip address 192.168.0.201 255.255.255.0 no mop enabled ! interface Ethernet1 no ip address no cdp enable ! interface Serial0 no ip address shutdown no fair-queue ! interface Serial1 no ip address shutdown no cdp enable ! router rip network 192.168.0.0 ! ip classless ip http server ! ! ! line con 0 exec-timeout 0 0 password cisco login line aux 0 line vty 0 4 password cisco login ! end

RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.0.201 )

02:33:23: RIP: build update entries - suppressing null update 02:33:49: RIP-TIMER: periodic timer expired 02:33:49: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.0.201 ) 02:33:49: RIP: build update entries - suppressing null update 02:34:19: RIP-TIMER: periodic timer expired 02:34:19: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (192.168.0.201 ) 02:34:19: RIP: build update entries - suppressing null update

***********Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is not set

C 192.168.0.0/24 is directly connected, Ethernet0************************************************************

Reply to
John Smith
Loading thread data ...

Thats right I think i remember from my ccna course that routes that are directly connected will not be in the R routing table

THanks

Reply to
John Smith

Ivan

I did like you recomended and everything works see route table below. The way I got it to work is to add another network just like you said 68.0.0.0 to another interface and the route came up fine.

Question for you though I tryed the loopback like you said to but it would not work as far as the rouing table being updated.

Basically, I configured the interface int e1 ...with the loopback command, (this is the other eth interface on the same router) but nothing happened in terms of rip any thoughts? See below the config on the interface shows loopback. The only way to get the R to show in the routing table was to plug in a ethernet cable into the interface in question.

I thought the function of the loopback command made it so you would not needing to have a physical cable pluged into it and it would be ping able interface hence working with RIP (R)?

Thanks for your help

interface Ethernet0 ip address 192.168.0.201 255.255.255.0 loopback no mop enabled

R 68.0.0.0/8 [120/1] via 192.168.0.201, 00:00:00, FastEthernet0/0 C 192.168.0.0/24 is directly connected, FastEthernet0/0

Reply to
John Smith

Never mind ....lol

config t interface loopback 0 ip address a.b.c.d 255.0.0.0

hey the R shows up

THanks

Reply to
John Smith

The router is suppresing the update because what it gets is the same network to which is connected. Try adding some additional interfaces on one of the routers (loopback will be just fine) and add their networks to RIP. Then you will se on other routers routing table some "R" routes.

Reply to
Ivan Ostreš

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.