From: James Matrisciano (jmatrisciano@kenttech.com)
Date: Thu Jan 19 2006 - 10:35:26 GMT-3
You can also use the "include-connected" command at the end of the
redistribute command.
redistribute rip NAME metric 1 include-connected
Also, when redistributing in IPv6 BGP, make sure you use the
redistribute internal as well as the redistribute connected.
address-family ipv6
neighbor 2100::40:4 activate
bgp redistribute-internal
redistribute connected metric 1
redistribute rip NAME metric 1 include-connected
no synchronization
exit-address-family
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
CCIEin2006
Sent: Wednesday, January 18, 2006 12:52 PM
To: Edmundo Bodero
Cc: ccielab@groupstudy.com
Subject: Re: IPv6 redistribution
Really? I've never heard of connected interfaces being automatically
being redistributed?!? Do you mean directly connected interface that are
advertised via network statements in the routing protocol?
On 1/18/06, Edmundo Bodero <bodero.edmundo@googlemail.com> wrote:
>
> Hi group,
>
> When we redistribute one routing protocol into another in IPv4, the
> directly connected interfaces of the first protocol are automatically
> included in the redistribution (except for ISIS). I think this is
> called implicit redistribution rule. I have been playing with
> redistribution in IPv6 (between OSPF and RIP both ways) and I think
> that this rule doesn't apply to IPv6. The only way to include the
> connected networks in the redistribution is to use the redistribute
> connected statement. Is that correct or Am I missing something?.
>
>
> Thanks for your help,
>
> Edmundo
>
> ______________________________________________________________________
> _ Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:49 GMT-3