From: Sikander Shahzad (Sikander@xxxxxxxxxx)
Date: Tue Feb 12 2002 - 02:24:11 GMT-3
Well, I think one can easily observe this even with ppp encap on serial
links. Remember, ppp adds host routes of connected devices in the routing
table and RIP does understand them and advertise them.
Regards,
Sikander
-----Original Message-----
From: StudyManiac [mailto:groupstudy1@home.com]
Sent: Tuesday, February 12, 2002 7:53 AM
To: 'Steven Weber'; ccielab@groupstudy.com
Subject: RE: RIP and Loopbacks in OSPF.......
Per the RFC, RIP was designed to understand host routes, hence the
understanding of /32's. It's not mandatory to implement this functionality,
but Cisco chose to do so.
- Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Steven Weber
Sent: Monday, February 11, 2002 12:55 PM
To: ccielab@groupstudy.com
Subject: RIP and Loopbacks in OSPF.......
I made an interesting observation, I wanted to know if other people are
experiencing the same thing, and the logic behind it. When redistributing
between OPSF and RIP I noticed that the loopbacks in OSPF don't need to be
summarized in order for RIP to see them. OSPF advertises a loopback as a /32
by default and RIP has no problem with this. However, once I add the ip ospf
network point-to-point command on the loopbacks thereby changing them from a
/32 to their true mask, once again RIP cannot see them unless there is some
sort of summarization or default route in place. I don't understand why RIP
sees these routes as a /32, shouldn't they need the mask native to RIP in
order to be seen in RIP ?
Does anyone have insight on this one?
Regards,
Steve
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:20 GMT-3