[74169] in North American Network Operators' Group
Re: RIP in Operation
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Thu Sep 16 10:07:25 2004
Date: Thu, 16 Sep 2004 14:06:25 +0000
From: bmanning@vacation.karoshi.com
To: Abhishek Verma <abhishekv.verma@gmail.com>
Cc: nanog@merit.edu
In-Reply-To: <ce8d90330409160649335e9421@mail.gmail.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Thu, Sep 16, 2004 at 07:19:24PM +0530, Abhishek Verma wrote:
>
> Hi,
>
> I am sure that there would be very few people running RIP in their
> networks, but since the IETF RIP mailing list is dead, and also
> because its more of an operational question, the Nanog list felt most
> appropriate to me for the following post.
i guess i'm among the very few then.
> Why would you, as an operator, recieve RIPv2 Request messages? The
> only reason that comes to my mind is when a remote RIPv2 router has
> just come up. That time its going to multicast this message on all its
> interfaces configured to run RIP. This is the *only* reason that comes
> to my mind.
thats the normal way
> However, there is text in the RFC 2453 that states that RIP can use
> this message to request specific networks also. It also states that
> such a request can only be made by a diagonistic software and cannot
> be used for routing. My doubt is, how can a diagnostic software, use
> the services of RIP for doing that?
kind of depends on the implementation of RIP you are using.
> I assume (please correct me if i am wrong) that the RIP requests are
> only then, used for requesting the entire routing tables, and nothing
> else. The 'diagnostics' story sounds too far fetched to me!
ripv2 allows for requesting specific prefixes. not too
far fetched.
>
> Thanks,
> Abhishek V.
>
> P.S.
> I tried googling but nothing came up.
>
> --
> Class of 2004
> Institue Of Technology, BHU
> Varanasi - India
