Hi Bryan, This is a known issue. There are issues with route recursion and IPv6 on MikroTik. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Bryan Tabb Sent: Wednesday, 12 August 2015 8:08 AM To: public@talk.mikrotik.com.au Subject: [MT-AU Public] ipv6 routes being unreachable Hi Having a problem with a CCR marking all the prefixes it's learning over an ibgp session as the gateway is unreachable. I've got an asr1k and a ccr. Each router has a /128 configured on a loopback (or bridge in mirkotik's case) and a /125 on each interface. /ipv6 address add address=x:x::13/128 advertise=no comment=loopback0 interface=loopback0 We are using ospfv3 for v6 and then building bgp sessions between the loopbacks. i.e. ospf carries the link nets and bgp carries the customer \ transit prefixes The ccr doesn't seem to be installing the loopback address learnt via ospf. However this is where things get a bit strange. For the snippets below ::8 = cisco & ::13 = ccr Looking at ospf routes on the CCR is lists the ::8/128 route [x@mdr-br1] /routing ospf-v3 route> print # DST-ADDRESS STATE COST GATEWAY INTERFACE 1 x:x::7/128 ext-2 20 fe80::72ca:9bff:fe88:5a00 ether1.40 2 x:x::8/128 ext-2 20 fe80::72ca:9bff:fe88:4181 ether1.40 3 x:x::9/128 ext-2 20 fe80::72ca:9bff:fe88:5a00 ether1.40 4 x:x::13/128 intra-area 10 :: ether1.40 I can even ping the cisco loop back from the ccr [xx@mdr-br1] > /ping x:x::8 SEQ HOST SIZE TTL TIME STATUS 0 x:x::8 56 64 8ms echo reply 1 x:x::8 56 64 35ms echo reply 2 x:x::8 56 64 19ms echo reply sent=3 received=3 packet-loss=0% min-rtt=8ms avg-rtt=20ms max-rtt=35ms [xx@mdr-br1] > /ping x:x::8 src-address=x:x::13 SEQ HOST SIZE TTL TIME STATUS 0 2402:7e00::8 56 64 10ms echo reply 1 2402:7e00::8 56 64 7ms echo reply Bgp sessions targeting the cisco loopback using the ccr loopback as the source establish and swap prefixes [xx@mdr-br1] /routing bgp peer> print Flags: X - disabled, E - established # INSTANCE REMOTE-ADDRESS REMOTE-AS 5 E default x:x::8 45280 6 E default x:x::7 45280 So all things being equal I'd say ::13 can reach ::8 and thus should install the v6 routes it is learning from v6. The ccr has v6.27 installed. Reading through the change log I can't see anything there that says we fixed it. Some of the tweaks I've done: * On the asr removed the ipv6 ospf from the loopback interface and add redistribute connected to get the /128 into the ccr * On the ccr added an admin mac onto bridge that I use as the "loopback" - this got the /128 advertised via ospf Has anyone had success get v6 ospf + bgp working with ccrs & ciscos? Cheers Bryan Tabb _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au