- User Since
- Nov 5 2018, 2:37 AM (211 w, 6 d)
Dec 5 2018
👍 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.
Nov 29 2018
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.
Nov 18 2018
I'm not positive, but it seems that this only occurs when ebgp-multihop is enabled on the peer.
Nov 13 2018
A user in Slack today pointed out that this only happens with V4 prefixes, V6 prefixes are properly installed into the FIB.
Nov 9 2018
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:
Nov 8 2018
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.
Nov 7 2018
I believe this can now be marked as resolved.
Nov 6 2018
I've opened a pull request to address this ticket in https://github.com/vyos/vyatta-cfg-system/pull/82.
Nov 5 2018
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.