👍 cool. Since we've confirmed that as a solution, I think it's safe to close.

I ended up moving away from VyOS but the more that I think this problem, I wonder if it's due to mutihop being on and not having a route to the next hop.

Sorry about that @kroy. That was the default value when I fixed a typo in the title 😬. I didn't mean to update that value.

I'm not positive, but it seems that this only occurs when ebgp-multihop is enabled on the peer.

A user in Slack today pointed out that this only happens with V4 prefixes, V6 prefixes are properly installed into the FIB.

Ah, I see the problem. You can't have both ip and ipv6 in the same route-map match rule.

I have confirmed this does not happen in 1.1.8. Here is a sample working config in 1.1.8:

This appears to be a regression somewhere between 1.1.8 to 1.2.0-rc6.

I submitted a patch for this in https://github.com/vyos/vyos-1x/pull/56.

I believe this can now be marked as resolved.

I've opened a pull request to address this ticket in https://github.com/vyos/vyatta-cfg-system/pull/82.

Would something like this be suitable? I've tried searching for a canonical source of device naming conventions for Linux. I'm not sure that we'll have a single clean way to identify this in regex.