FRR currently only has the ability to select one route entry as selected per prefix. Fixing this has implications for both route selection as well as nexthop tracking. Nothing insurmountable just programming and working through the places this would cause changes in behavior. As it stands this bugs me too but I have not come up with a scenario where this is truly affecting routing behavior other than from a display/small confusion perspective. donald On Wed, Dec 16, 2020 at 5:25 AM Stephen Glaus <snglaus@gmail.com> wrote:
Apologies if I'm missing something simple here, but can anyone tell me why (in the output below) only one link-local address is shown as selected when all have been installed in the FIB?
dut-2# sh ipv rou Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route
C>* 1::1/128 is directly connected, lo1, 00:14:00 C>* 1::2/128 is directly connected, lo2, 00:13:58 C>* 1::3/128 is directly connected, lo3, 00:14:01 C>* 10:1::/64 is directly connected, dp0p193p1, 00:06:42 S>* 10:2::/32 [1/0] via 192:168:1::2, dp0p256p1, weight 1, 00:06:41 S>* 51:1:1::/64 [1/0] via 192:168:1::2, dp0p256p1, weight 1, 00:06:41 C>* 192:168:1::/64 is directly connected, dp0p256p1, 00:06:42 S>* 200:1::/32 [1/0] via 10:1::2, dp0p193p1, weight 1, 00:06:41 C * fe80::/64 is directly connected, dp0p192p1, 00:06:41 C * fe80::/64 is directly connected, dp0p193p1, 00:06:42 C * fe80::/64 is directly connected, dp0p256p1, 00:06:42 C * fe80::/64 is directly connected, dp0p224p1, 00:06:47 C * fe80::/64 is directly connected, lo2, 00:13:59 C * fe80::/64 is directly connected, lo1, 00:14:00 C>* fe80::/64 is directly connected, lo3, 00:14:02 dut-2#
Thanks in advance...Steve
_______________________________________________ frog mailing list frog@lists.frrouting.org https://lists.frrouting.org/listinfo/frog