Build #1,012

FreeRangeRouting Protocol Suite

Build: #1012 was successful Changes by Donald Sharp

Build result summary


105 minutes
bf2c7ef2a68b2df772233aaff5d8f63fb345a6bc bf2c7ef2a68b2df772233aaff5d8f63fb345a6bc
Total tests
Successful since
#1009 ()

Code commits

Author Commit Message Commit date
Donald Sharp Donald Sharp bf2c7ef2a68b2df772233aaff5d8f63fb345a6bc bf2c7ef2a68b2df772233aaff5d8f63fb345a6bc Merge pull request #2053 from LabNConsulting/working/master/bvl-bug-degenerate-no-label
bgpd: bugfix vpn->vrf leak: unicast-originated routes are local non-LSP
Paul Ziemba Paul Ziemba 513bf8d6c987fea03cb75a2e533cf55ade538a85 m 513bf8d6c987fea03cb75a2e533cf55ade538a85 bgpd: bugfix vpn->vrf leak: unicast-originated routes are local non-LSP
In general, routes leaked from the vpn rib to a vrf include any
labels that might have been attached to the vpn route. VRF routes
that have labels attached require a label-switched path and therefore
require nexthops with labels in order to be marked valid by the
nexthop-tracking logic.

However, some routes in the vpn RIB originated in vrfs local to this
router. Even though they may have labels, we must omit the labels
when leaking to a vrf because traffic using those resulting routes
will be carried by this router via IP routing and not label switching.
The nexthops of these routes do not need to indicate a label-switched
path, and thus the routes should be marked valid even when their nexthops
do not have labels.

This changeset omits labels from vpn->vrf leaked routes when the ultimate
source of the vpn route was a local vrf.

Signed-off-by: G. Paul Ziemba <>