I posted a question about this problem a few days ago, but so far I haven't been able to solve it. I was hoping posting a different question might get me started in the right direction. I have two VRF fast Ethernet interfaces that need to talk to each other - I need the routing information to be kept separate, though. I know by default they cannot communicate, but I configured route leakage. What perplexes me is that I can ping across VRF's to the loopback addresses, but not to the Ethernet interfaces. I presume because they share the same IP space, as I can give Fa2/1 a different IP range and ping across the VRFs to reach it. The bottom line is that I think the problem will be solved if I can get "ping vrf MWC 66.210.189.15" to work. Thanks for your help.
ip vrf COX
rd 1:1
route-target export 1:1
route-target import 1:2
!
ip vrf MWC
rd 1:2
route-target export 1:2
route-target import 1:1
interface FastEthernet0/0
ip vrf forwarding MWC
ip address 66.210.189.13 255.255.255.224
interface Loopback0
ip vrf forwarding MWC
ip address 172.16.22.1 255.255.255.0
!
interface Loopback1
ip vrf forwarding COX
ip address 172.16.23.1 255.255.255.0
interface FastEthernet2/1
ip vrf forwarding COX
ip address 66.210.189.15 255.255.255.224
router bgp 1
no synchronization
bgp log-neighbor-changes
no auto-summary
!
address-family ipv4 vrf MWC
redistribute connected
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf COX
redistribute connected
no auto-summary
no synchronization
exit-address-family
