🚀 go-pugleaf

We have several subnets set up as follows:

           (default)
               |
             cisco
               |
    ----+------+----  134.79.240.0
        |
      cisco
        |
    ----+-----------  134.79.248.0

RIP is used on both subnets and the router between them only speaks
RIP.  The other router speaks IGRP with the outside world and only
advertises a default route into this portion of our network.

Unfortunately, the RIP-only router sees the default advertisement
but only partially understands it.  The following output shows that
it sees the route and has used it to set a gateway of last resort,
yet it's rather peculiar that the route is not flagged as a candidate
default route.  Of rather more concern is that this router acts as if
there *isn't* a default route.

    router>show ip route

    Codes: I - IGRP derived, R - RIP derived, H - HELLO derived
           C - connected, S - static, E - EGP derived, B - BGP derived
           * - candidate default route

    Gateway of last resort is 134.79.240.3 to network 0.0.0.0

    C Net 134.79.0.0 is subnetted (mask is 255.255.252.0), 2 subnets
    C     134.79.248.0 is directly connected, Ethernet1
    C     134.79.240.0 is directly connected, Ethernet0
    R Net 0.0.0.0 [120/2] via 134.79.240.3, 10 sec, Ethernet0

We have set 'ip default-network 0.0.0.0' on the router, though that
appears to be the default anyway.  What are we missing?

-- 
Karl Swartz		|INet	kls@unixhub.slac.stanford.edu
SLAC Computing Services	|	   or kls@ditka.chicago.com
1-415/926-3630		|UUCP	uunet!lll-winken!unixhub!kls  -or-  ditka!kls
(SLAC and the US Dept. of Energy don't necessarily agree with my opinions.)