From: George Goglidze (goglidze@gmail.com)
Date: Sat Feb 09 2008 - 12:08:06 ARST
Hi there,
recursive lookup has NOTHING to do with VLSM or anything like that.
recursive lookup is something like following.
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip route 192.168.0.0 255.255.0.0 176.1.1.1
ip route 176.1.1.1 255.255.255.255 f0/0
this way, when it tried to find 0.0.0.0 network(DEFAULT GW),
it will see it's pointing to 192.168.1.1, and as it's not directly connected
network,
it will need to find where it is and it will recursively lookup 176.1.1.1,
and as it's not directly connected neither, it will recursively see
the last route 176.1.1.1 -> f0/0
and send the packet out f0/0
that's all,
On Feb 8, 2008 6:55 PM, John <jgarrison1@austin.rr.com> wrote:
> I've always had trouble getting the logic of recursive lookups. My new
> "theory" (I use the word lightly) is that if I advertise an ip default
> network of 150.1.5.0/24, which is a VLSM on the 150.1.0.0 network. When
> I do
> a sh ip route 150.1.5.0 I will get a recursive lookup to 150.1.0.0/16(in<http://150.1.0.0/16%28in>RIPv2
> and EIGRP). My conclusion is that the only time I will get a recursive
> lookup
> is when I've applied a VLSM mask on a classful network and I do a sh ip
> route
> on that subnet.
>
> I'm I thourghly confused???
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:48 ARST