The only thing I could come up with, is redistribution. You would need to
setup your addressing so as to have the shorter masks (example: say /24's)
on the Classful RIP 1 side and the longer masks (example: say something
divisible like /26's) to be summarized on & from the Classless RIP 2 side.
Again- RIP Version 1 is going to only communicate updates using the Subnet
Mask of the interface it is advertising it's route table out of . So- once
you line up a Summarization into Version 1 & Redistribute on the Version 2
router (with an interface belonging to Version 1), the problem would be
solved. Had you ever thought about using EIGRP ???
Phil
----- Original Message -----
From: Rashid Lohiya
To:
Sent: Tuesday, May 08, 2001 5:46 AM
Subject: Re: RIPv2 vs. RIP [7:3404]
> Quote from Routing TCP/IP Jeff Doyle, Pg 281:
>
> Subnet masks carried with each route entry
> Authentication of routing updates
> Next-hop addresses carried with each route entry
> External route tags
> Multicast route updates
>
> I remember these by memorising the word/abbreviation S.A.N.E.M.
>
> Hope this helps
>
> Rashid Lohiya
> Snr Network Engineer
> Gobix Ltd (UK)
> European Network Services
>
>
> ""Thomas"" wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi All - What's the main feature of RIPv2 over RIPv1, beside the VLSM?
I
> am
> > trying to migrate to RIPv2, but some devices only support RIPv1. Is
there
> > any workaround to have RIPv2 and RIP compatable? Thanks all in advance!
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=3589&t=3404
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
