The router doesn't store routing information in that way, or think in that way.
The math involved in doing so is actually pretty expensive. -Blake On Tue, Jul 2, 2013 at 4:00 PM, Jeffrey G. Fitzwater <[email protected]>wrote: > I have 0.0.0.0 pointing to one of our ISP so that any prefix < /24 ( which > we don't permit in from any ISP) would get pushed to that ISP which might > have route. > > I am just trying to figure out how may are being pushed to default. > > > > Jeff F. > On Jul 2, 2013, at 4:53 PM, Saku Ytti <[email protected]> > wrote: > > > On (2013-07-02 20:19 +0000), Jeffrey G. Fitzwater wrote: > > > >> I would like to find out what routes are NOT in my route table and > therefore follow the DEFAULT path to 0.0.0.0. > >> > >> Would "show ip cef unresolved" work ? I get nothing back when I run > it but maybe there is nothing to see. > > > > What you imagine is FIB covering all possibilities and then next-hop or > > null, it would not scale and makes no sense. 0.0.0.0 is branch when there > > is no matching top-level branch. > > > > You could produce such data offline and aggregate it to maximally. > > > > -- > > ++ytti > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
