RE: RIP default routes (& default-information originate)

From: Philip Neeson (Philip.Neeson@xxxxxxxxxxxxx)
Date: Sun Nov 05 2000 - 17:18:41 GMT-3


   
   HI,
   
   I've tested this just now and didn't have any problems. I found that
   aslong as there was a route in the routing table toward the network
   I'm pointing to with the "ip default-network" command things work ok.
   I did find however that I needed to enter the command with a classfull
   ip address otherwise it would simply convert my command into a static
   route. (11.3.9T)
   
   Also the rule of split-horizon applies, If I have routers A--B--C and
   place the "default-network" command on A pointing to a network hanging
   off C the candidate route is tagged in A's routing table but no
   propagated as a default router to B or C.
   
   I'm also trying to understand what use the "default-information
   originate" is with rip. It doesn't seem to have any effect with either
   a "default-network" or "ip route 0.0.0.0 0.0.0.0 x.x.x.x"
   
   Why & how would I use "default-information originate" under rip??
   
   Thanks,
   
   Philip.
   
   -----Original Message-----
   From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
   LBOng
   Sent: 18 October 2000 21:29
   To: ccielab@groupstudy.com
   Subject: RIP default routes
   
   Hi Group,
   
   
   
   I am going through Jeff Doyle book on pg. 755. In his case study using
   "ip default-network command" for rip routing, he stated that the
   router that source the default route does not have to its gateway of
   last resort set for it to advertise the candidate route out.
   
   
   
   When I tried his example I have the following error:
   
   
   
   04:59:09: RT: 1.0.0.0 is now exterior
   04:59:09: RIP-DB: add 0.0.0.0/0 (metric 0) via 0.0.0.0 on Null0
   (permanent)
   04:59:11: RIP: sending v1 flash update to 255.255.255.255 via Serial2
   (130.10.2.2)
   04:59:11: RIP: build flash update entries
   04:59:11: RIP-ERROR: route 0.0.0.0/0 not in routing table. -
   suppressing null update^Z
   test1#
   04:59:18: %SYS-5-CONFIG_I: Configured from console by console
   test1#
   04:59:27: RIP: sending v1 update to 255.255.255.255 via Serial2
   (130.10.2.2)
   04:59:27: RIP: build update entries
   04:59:27: RIP-ERROR: route 0.0.0.0/0 not in routing table.
   04:59:27: subnet 130.10.3.0 metric 1
   04:59:27: subnet 130.10.5.1 metric 2
   04:59:27: subnet 130.10.5.17 metric 2
   04:59:27: subnet 130.10.5.33 metric 2
   04:59:27: subnet 130.10.10.1 metric 2
   04:59:27: subnet 130.10.11.0 metric
   
   
   
   below is my routing table:
   
   
   
   test1#sh ip route
   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, * -
   candidate default
          U - per-user static route, o - ODR, P - periodic downloaded
   static route
          T - traffic engineered route
   
   
   
   Gateway of last resort is not set
   
   
   
   C* 1.0.0.0/8 is directly connected, Serial3
        130.10.0.0/16 is variably subnetted, 7 subnets, 2 masks
   O IA 130.10.11.0/24 [110/74] via 130.10.3.1, Serial1
   O 130.10.10.1/32 [110/65] via 130.10.3.1, Serial1
   C 130.10.2.0/24 is directly connected, Serial2
   C 130.10.3.0/24 is directly connected, Serial1
   O IA 130.10.5.1/32 [110/65] via 130.10.3.1, Serial1
   O IA 130.10.5.17/32 [110/65] via 130.10.3.1, Serial1
   O IA 130.10.5.33/32 [110/65] via 130.10.3.1, Serial1
   test1#
   
   
   
   Any help or comments is much appreciated.
   
   
   
   Rgds
   
   
   
   LB
   
   
   
   



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:41 GMT-3