T1 RIP IP Oh My!

Post #17,061 by boxley 11/6/01 10:13:45 PM Reply	T1 RIP IP Oh My! running 2 routers joined together by a T1 with ppp riding the rails. net1 192.168.1.1 mask 255.255.255.0 net2 10.1.1.1 mask 255.255.255.0 RIP is running at both ends with the networks put into the databases at both ends. RIP does not update the tables. Someone is insisting that there must be a common network on both routers. Bushwa, RIP broadcasts updates to port 520 listens on port 521 the broadcasts go out all interfaces, if the RIP knows about the other network because it is in the database, it should update. Update, it wont even route. Checked the RFC, mention of common network is not there. Went to the cisco rip reference, no mention of common networks, jagoff insists that there has to be. Anyone else know the answer or have an opinion? RIP is almost identical to the behavior of the bsd routed command. thanx, bill tshirt front "born to die before I get old" thshirt back "fscked another one didnja?"
Post #17,088 by pwhysall 11/7/01 2:06:27 AM Reply	Silly question There is a route on net1 for 10.1.1.0 pointing at the net1 WAN interface, and one on net2 for 192.168.1.0 pointing at the net2 WAN interface? Cuz if there ain't, those two boxes are never ever going to see each other, are they? Peter Shill For Hire [link\|http://www.kuro5hin.org\|There is no K5 Cabal]
Post #17,103 by boxley 11/7/01 8:47:35 AM Reply	Arguing with a CS Person of a large router company (not cisco) who doesnt unnerstand the concept of IP networks atall. Just wanted a sanity check. thanx, bill tshirt front "born to die before I get old" thshirt back "fscked another one didnja?"
Post #17,158 by Brandioch 11/7/01 1:53:51 PM Reply	Version of RIP? Cisco offers a few different ways to update the routing tables. They do NOT have to be the same network. They DO have to be able to route to each other (try with ping). They SHOULD BE the save way on all (RIP, RIP2, EIGRP, whatever).
Post #17,177 by boxley 11/7/01 3:05:38 PM Reply	RIP 2 #DEBUG 11/07/2001 15:21:56 ripRoute (test): sending v2 update to 255.255.255.255 DEBUG 11/07/2001 15:21:56 ripRoute (test): Tx 4.4.4.4/32->0.0.0.0,metric 1,tag 0 DEBUG 11/07/2001 15:21:56 ripRoute (default): source: 10.10.1.1 is not a directly-connected network 2 routers a T1 serial interface encapped ppp betwee them, RIPv2 is enabled on bothsides. Need to reconfigure a couple of ciscos cause I am sure they can do this. Although it prolly doesnt matte much because RIP is kinda falling away as OSPF and BGP are more prominent in large networks. Besides why have all that spamming every 30 seconds. thanx, bill tshirt front "born to die before I get old" thshirt back "fscked another one didnja?"
Post #17,349 by Brandioch 11/8/01 1:39:36 PM Reply	Let me check on this. I'll see what I can find.
Post #22,440 by Brandioch 12/26/01 2:07:26 PM Reply	Sorry for the delay. I just found this message again. Okay, there has to be a single network in common on both the serial interfaces. 10.1.1.0(eth0)cisco(serial0)192.168.1.1---t1---192.168.1.2(serial0)cisco(eth0)192.168.100.0 route rip2 network 10.1.1.0 network 192.168.100.0 redistribute route

Welcome to IWETHEY!