From: bigb97750 (bigb97750@aol.com)
Date: Tue Mar 18 2008 - 20:52:33 ART
Try a ipv6-ipv4 tunnel to route packets
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
YourPal
Sent: Monday, March 10, 2008 3:52 PM
To: Carlos Alberto Trujillo Jimenez
Cc: Todd, Douglas M.; Cisco certification
Subject: Re: Can't receive RIPng routes on LAN interface configured with
"bridge-group" command
True, Carlos.
R2(config)#bridge 1 route ?
appletalk AppleTalk
clns ISO CLNS
decnet DECnet
ip IP
ipx Novell IPX
Moving the IPv6 config to interface BVI1 didn't solve the issue.
Thank you.
BR,
Emil
On 3/11/08, Carlos Alberto Trujillo Jimenez <
carlos.trujillo.jimenez@gmail.com> wrote:
>
> Todd.
>
> IRB does not support ipv6.
>
>
>
>
> 2008/3/10, Todd, Douglas M. <DTODD@partners.org>:
> >
> > Move
> > ipv6 address 2001:192:10:1::2/64
> > ipv6 rip RIPng enable
> >
> > to the BVI interface. That will do the trick.
> >
> > DMT
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > YourPal
> > Sent: Monday, March 10, 2008 9:17 AM
> > To: Cisco certification
> > Subject: Can't receive RIPng routes on LAN interface configured with
> > "bridge-group" command
> >
> > Hi Group,
> >
> > I have the following IPv6 RIPng scenario:
> >
> > R2 (fa0/0) -----VLAN22----- (fa0/0) BB2
> >
> > R2:
> > !
> > ipv6 unicast-routing
> > bridge irb
> > bridge 1 protocol ieee
> > bridge 1 route ip
> > !
> > interface FastEthernet0/0
> > no ip address
> >
> > bridge-group 1
> > !
> > interface BVI1
> > ip address 192.10.1.2 255.255.255.0
> > !
> >
> >
> > BB2:
> > !
> > interface FastEthernet0/0
> > ip address 192.10.1.254 255.255.255.0
> > ipv6 address 2001:192:10:1::254/64
> > ipv6 rip RIPng enable
> > !
> > interface Loopback0
> > ipv6 address 2001:220:20:3::1/64
> > ipv6 rip RIPng enable
> > !
> > interface Loopback1
> > ipv6 address 2001:222:22:2::1/64
> > ipv6 rip RIPng enable
> > !
> > interface Loopback3
> > ipv6 address 2001:205:90:31::1/64
> > ipv6 rip RIPng enable
> > !
> >
> > Outputs of "deb ipv rip" on BB2:
> >
> > RIPng: Sending multicast update on FastEthernet0/0 for RIPng
> > src=FE80::21B:54FF:FECE:1F84
> > dst=FF02::9 (FastEthernet0/0)
> > sport=521, dport=521, length=72
> > command=2, version=1, mbz=0, #rte=3
> > tag=0, metric=1, prefix=2001:220:20:3::/64
> > tag=0, metric=1, prefix=2001:222:22:2::/64
> > tag=0, metric=1, prefix=2001:205:90:31::/64
> >
> > However, R2 did not receive those RIPng routes from BB2 until I removed
> > the
> > "bridge-group 1" command from its Fa0/0 interface.
> >
> > Anyone be kind enough to explain why and advise a solution. The bridge
> > group
> > can't be removed because that will violate the requirement of an earlier
> > task.
> >
> >
> > Thank you.
> >
> > BR,
> > Emil
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
> > 3/10/2008 11:07
> > AM
> >
> >
> > No virus found in this outgoing message.
> > Checked by AVG.
> > Version: 7.5.518 / Virus Database: 269.21.7/1323 - Release Date:
> > 3/10/2008 11:07
> > AM
> >
> >
> > The information transmitted in this electronic communication is intended
> > only
> > for the person or entity to whom it is addressed and may contain
> > confidential
> > and/or privileged material. Any review, retransmission, dissemination or
> > other
> > use of or taking of any action in reliance upon this information by
> > persons or
> > entities other than the intended recipient is prohibited. If you
> > received this
> > information in error, please contact the Compliance HelpLine at
> > 800-856-1983 and
> > properly dispose of this information.
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:53 ART