Hi, This patch proposes a new feature for BFD controlled static routes. Normally, the BFD sessions are created to the route next hop. However, in some scenarios, e.g. when the next hop itself does not support BFD, or when it might be more meaningful to create the session to a remote monitoring station, we need more flexible relationship between a static route nexthop and its controlling BFD session. In this patch, a numeric label value can be specified with manually configured BFD neighbors, and a static route nexthop can be configured to track a certain BFD session using that label. The detailed behavior is updated in the user's guide. This feature may also be added to other protocols, but it seems not so meaningful. This feature will be useful when it is required to monitor the liveness of a link using a multihop bfd session with a remote host. Suppose a router box is using multiple routing tables and the traffic coming from the user side and generated locally is splited into two tables, and a bfd daemon is running on a remote monitoring station 192.0.2.1 and is used to monitor the link through the gateway 203.0.113.1. An example configuration might be: # Locally generated traffic ipv4 table main; # Traffic from user ipv4 table user; protocol static { ipv4 { table main; }; # Force route the traffic to the monitoring station # through the gateway to be monitored route 192.0.2.1/32 via 203.0.113.1; }; protocol bfd { # Establish a bfd session with the monitoring station labeled with 10 neighbor 192.0.2.1 multihop on label 10; } protocol static { ipv4 { table user; }; # When the bfd session comes up, the route will be installed # and removed when down route 0.0.0.0/0 via 203.0.113.1 bfd track 10; }; base-commit: 4bee51c82f0f119e52d3bf58a4416f00c004e8dd commit: https://github.com/shankerwangmiao/bird/commit/2991bf79067331a411bdc595728a7... Cheers, Miao Wang