The 2001:19f0:ffff::1 is the neighbour, it is accessible via the Kernel route and I'm able to pull routes from it. The setup is multihop. But I think you are on something. I think the peer should return the gateway as the next hop and not itself. I'm experimenting with Vultr and their setup is questionable, so this is just one more thing that they messed up. Anyhow, thanks for your help. Feel free to close the ticket.
Sun, May 2
Sat, May 1
Hmm, all other routes have longer prefixes, so they should take precedence. As far as I understand the priority is prefix length (longest first) -> admin distance -> metric. So, it must be something else.
Mon, Apr 12
Sorry for the late reply, I've dismantled the setup as I needed to put the PPP link back in use, I will look into it again tonight. In essence, it would be good to see something like this on terse view:
Apr 2 2021
I think the presence of the kernel default route may be the problem. It comes from RA through autoconf option on the interface. I will do some more testing.
Mar 30 2021
I still see it in frr after the reboot but it is not showing in the output of show ipv6 route, so it seems like just a visualization problem.
What command do you use to get this?
Mar 29 2021
Mar 25 2021
I will give it a try once the image is out. The latest right now is still showing 2021-03-23.
Mar 24 2021
Mar 23 2021
Yes, I made mistake when adding the command to the ticket and I corrected it now. It should read: