From: gladston@br.ibm.com
Date: Wed Aug 17 2005 - 17:09:07 GMT-3
============
quoted
RIP advertises a route to 0.0.0.0 if a gateway of last resort is selected using the ip default-network command.
This network specified in the ip default-network command need not be explicitly advertised under RIP. For example, note that the gateway of last resort on this router was learned using the combination of the ip route and ip default-network commands. If you enable RIP on this router, RIP advertises a route to 0.0.0.0
http://www.cisco.com/en/US/customer/tech/tk365/technologies_tech_note09186a0080094374.shtml#ipnetwork
============
This is not the behaviour on 12.2T
RIP only advertises 0.0.0.0 if the default network is under RIP.
Is that what you got on tests?
Tests:
150.100.1.0 is under RIP
69.69.10.0 is not
R4 receives routes from R1
Rack2R1(config)#ip default-network 150.100.1.0
Rack2R1(config)#ip default-network 150.100.0.0
Rack2R1#sh ip route
Gateway of last resort is 150.100.1.0 to network 150.100.0.0
Rack2R4#sir
Gateway of last resort is 148.5.14.1 to network 0.0.0.0
Rack2R1(config)# ip default-network 69.69.10.0
Rack2R1(config)# ip default-network 69.0.0.0
Rack2R1#sh ip route
Gateway of last resort is 69.69.10.0 to network 69.0.0.0
Rack2R4#sh ip route
Gateway of last resort is not set
Tested on C2600-J1S3-M, Version 12.2(15)T5
(eheh, I am wondering if Cisco guys will stop changing the behaviour, or keep the documentation up to date)
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3