From: Craig Dorry (chdorry@yahoo.com)
Date: Thu Sep 12 2002 - 11:10:18 GMT-3
Dimitris,
On a side note, for some reason R4 is advertising the
200.0.0.0/24 back to R2 (Split horizon perhaps?).
Now for the routing "problem", this appplies to only
IGRP and not rip. I believe this is related to the
fact that IGRP doesn't understand host routes and
therefore doesn't recognize 200.0.0.4/32 as a route in
the routing table, allowing it to accept the /24
route.
Try this out:
On R2 add two more loopbacks with /32 masks. Make
each part of a Class B network. I used 172.16.1.1/32
and 172.17.1.1/32. These will be redistributed to R4
due to redistribute connected.
Create similar loopbacks that are part of that class B
on R4, but make one a /24 mask (or any mask other than
/32) and one a 32 mask. I used 172.16.2.2/24 and
172.17.2.2/32. Then you will see the major net
received on R4 for the 172.17.0.0/16 but not the
172.16.0.0/16 confirming that IGRP doesn't appear to
recognize the /32 loopback.
Hope this helps.
Craig
--- Dimitris Vassilopoulos
<Dimitris.Vassilopoulos@eurodyn.com> wrote:
> Craig,
>
> I understand the discontiguous networks issue...
>
> Still, why IGRP has the 200.0.0.0/24 route ? It
> souldn't, as isn't in
> RIP...
>
>
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:49 GMT-3