Help configuring IPv6, no router to host

RouterOS General
1

Hi,

I received /126 from my ISP to configure IPv6 on my routeros, and want to configure it to connect bgp peer v6.

WAN of ISP: 2804:7f4:4001:28::1/126
My LAN: 2804:7f4:4001:28::2/126

Look what I did:

[radionet@BORDA-RADIONET-BGP] > ipv a pr
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE      ADVERTISE
 0  G 2804:7f4:4001:28::2/126                               ether1         no

ether1 is my WAN where I have IPv4 running with BGP.

IPv6 routes:

[radionet@BORDA-RADIONET-BGP] > ipv r print detail 
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable 
 0 A S  dst-address=2000::/3 gateway=2804:7f4:4001:28::1 gateway-status=2804:7f4:4001:28::1 reachable via  ether1 distance=1 scope=30 target-scope=10 

 1 ADC  dst-address=2804:7f4:4001:28::/126 gateway=ether1 gateway-status=ether1 reachable distance=0 scope=10




[radionet@BORDA-RADIONET-BGP] > ping 2804:7f4:4001:28::1 c=1
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                                                                                                                                       
    0 2804:7f4:4001:28::1                                     timeout                                                                                                                                                                                      
    sent=1 received=0 packet-loss=100%

And the log of BGP says:

15:18:49 route,bgp,info Failed to open TCP connection: No route to host 
15:18:49 route,bgp,info     RemoteAddress=2804:7f4:4001:28::1

What am I missing?

Thank you!

2

A couple of things -
Does the ISP’s router show up in ND?
Your wording in the question makes me wonder:
You used the word ‘wan’ to refer to the ISP, and ‘lan’ to refer to your own Interface.
I see in the configs that ether1 is the interface where you put the address - This is the interface that is connected to the ISP, right? (sorry to ask - I’ve seen some strange things on these forums)

Can you ping the ISP’s router on its link-local address?
ping fe80::abcd:efff:0123%ether1

Make sure that you’re not blocking ICMPv6 on your ether1 interface. ICMPv6 includes ND (the new ‘arp’ protocol)

3

No, the ISP router show as failed in ND.

When I mean WAN/LAN is the /126 from ISP. WAN is the ISP and LAN is me.

And no, cant ping the ISP through ether1.

My RB is 1100AHx2 with 6.27 ros, and no firewall.

4

Make sure icmpv6 is not being blocked in your input chain.
Neighbor Discovery uses ICMP to work.
Also make sure icmpv6 is not being dropped from your output chain.

Another interesting thing to try:
from the command line:
/ping ff02::1%ether1
(really include the %ether1 because you have to specify which interface)
ff02::1 is “all ipv6 speakers on the network” - pretty much a broadcast.
ff02::2 is “all routers on the network” - see if you can ping those and get any responses.
Whichever unicast hosts respond, try pinging them on link-local:
e.g. /ping fe80::0204:0608:0a0c%ether1

Maybe the default gw blocks pings - try to ping 2001:470:20::2 (Hurricane Electric’s anycasted IPv6 public dns server) just in case.

Otherwise, make sure you and your ISP are actually using the same /126 prefix - that is obviously a manually-configured thing (I hate the idea of burning a /64 on a p2p interface or on a loopback interface, but apparently, that’s the current "best practice for now. On the other hand, Level3 uses /126 for attachment circuits, so who’s to say?)

Most likely: firewall blocking traffic
Second most likely: either you or the ISP’s provisioner has mis-typed the IPv6 address of your WAN circuit.
Third most likely: ? - before delving into the bizarre, try connecting your computer directly with the right config to see if you get the same results.