Hello Joe: <snip> > > Is there something fundamental I'm missing, here? Why should a > transparent bridge behave differently with IPv4 than it does with IPv6? > > > Joe > > ! cisco bridge 1 > > cisco 2620 (MPC860) processor (revision 0x102) with 61440K/4096K bytes > of memory. > System image file is "flash:c2600-ik9o3s3-mz.123-26.bin" > > interface ATM0/0 > no ip address > no ip route-cache > no atm ilmi-keepalive > dsl operating-mode auto > ! > interface ATM0/0.1 point-to-point > no ip route-cache > bridge-group 1 > pvc 0/35 > encapsulation aal5snap > ! > ! > interface FastEthernet0/0.200 > encapsulation dot1Q 200 > no ip route-cache > bridge-group 1 > bridge-group 1 spanning-disabled > ! > bridge 1 protocol ieee > > > ! cisco bridge 2 > > cisco 2621 (MPC860) processor (revision 0x102) with 61440K/4096K bytes > of memory. > System image file is "flash:c2600-ik9o3s3-mz.123-26.bin" > > interface FastEthernet0/0 > description facing the telco > speed 100 > full-duplex > bridge-group 1 > bridge-group 1 spanning-disabled > ! > interface FastEthernet0/1 > description facing the exchange point > bridge-group 1 > bridge-group 1 output-pattern-list 1100 > bridge-group 1 spanning-disabled > ! > interface BVI1 > description a way to manage the bridge, v4-only is fine > ip address x.x.x.x y.y.y.y > ! > bridge 1 protocol ieee > bridge 1 route ip >
I don't think the bridge is really transparent due to the 'bridge 1 route ip' on your exchange-point side device. If possible, you might want to try removing that statement (if you're local to the device, of course) to see if that does it. I don't think there is a 'bridge 1 route ipv6'. Regards, Mike _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
