From: Hunt Lee (ciscoforme3@yahoo.com.au)
Date: Thu Jan 16 2003 - 08:12:54 GMT-3
Rafa,
Yes ;) It does make much more sense now.
Since my interfaces between R4 & R5 are on a different major network (140.100) than
the route update 151.100.0.0/15, RIPv1 will automatically tried to auto-summarize it
into it's classful network. And like you said, since 151.100.0.0/15 doesn't have
any major network (since it is already less specific than a /16 for 151.100), as a
result, R4 will just not bother to pass it as an update.
And since the route update is already a /15 for 151.100, this makes it impossible to
have an interface (as Secondary) to belongs to the same classful network as the
route update 151.100.
Please correct me if I'm wrong ;)
Hunt
--- "Valiente, Rafael" <rafael.valiente@bt.es> wrote: > Hi
>
> I think that is normal that R4 does not redistribute 151.100.0.0/15 network
> into RIPv1 because RIPv1 is a classfull protocol.
>
> What is the major network of 151.100.0.0/15 ? None. So there is nothing to
> redistribute
>
> RIPv1 summarise a subnet to its major network, but in your case, you have a
> summary of two class B networks
>
> If you mask should be /17, R4 will redistribute it as the major network /16
>
>
> I hope this help you
>
> Regards
>
> Rafa
>
>
> -----Mensaje original-----
> De: Hunt Lee [mailto:huntl@webcentral.com.au]
> Enviado el: jueves 16 de enero de 2003 3:17
> Para: 'ccielab@groupstudy.com'
> Asunto: Please help!!! EIGRP to OSPF to RIP
>
>
> Hi guys,
>
> I thought this is easy, but I have spent hours on it & still couldn't solve
> it.
>
> 151.100.0.0/15 ---- R1 ----- R2 ------- R3 --------- R4 --------- R5
> (EIGRP)
>
> R1 - using EIGRP
> R2 - using both EIGRP & OSPF (mutual redistributeion)
> R3 - using OSPF
> R4 - using OSPF & RIPv1 (mutual redistribution)
> R5 - using RIPv1
>
> The network 151.100.0.0/15 is generated by EIGRP summary-address command in
> R1 (not allowed to change).
>
> The IPs for the transfer network is as follows:-
>
> R1 to R2 :- 140.100.3.1 /30 & 140.100.3.2 /30
>
> R2, R3 & R4 (Hub & Spoke topology, where R3 is the hub, while R2 & R4 are
> spokes - 140.100.1.1 /24, 140.100.1.2/24 & 140.100.1.3/24
>
> R4 to R5:- can be set to any IPs here... currently I'm using 140.100.5.1/24
> & 140.100.5.2/24
>
> I couldn't get R5 to see 151.100.0.0/15 or 151.100.0.0/16 at all. Assume
> that I'm not allowed to use any "summary-address" or aggregate commands from
> any routing protocols, is there any other way I could get R5 to see this
> route?
>
> Lee
> .
> **********************************************
> Noticia legal
> Este mensaje electrsnico contiene informacisn de BT Ignite Espaqa S.A.U. que
> es privada y confidencial, siendo para el uso exclusivo de la persona (s) o
> entidades arriba mencionadas. Si usted no es el destinatario seqalado, le
> informamos que cualquier divulgacisn, copia, distribucisn o uso de los
> contenidos esta prohibida. Si usted ha recibido este mensaje por error, por
> favor borre su contenido lo antes posible.
> Gracias.
> .
http://movies.yahoo.com.au - Yahoo! Movies
- What's on at your local cinema?
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:50 GMT-3