Hello! While testing bird 2.13 with a bunch of non-default tables, including separate tables for flow specifications, I've found the output of 'show route' without additional parameters a bit annoying: # birdc show route BIRD 2.13 ready. Table FLOW4: flow4 { dst 109.68.40.15/32; proto 17; dport 123; } [FLOWSPEC 2023-06-08] * (200) So I had to add additional "table all" parameter to get route from non-default IPv4 table: # birdc show route table all BIRD 2.13 ready. Table master4: Table master6: Table IP4: 109.68.40.15/32 unicast [RS0 2023-06-07 from 193.25.180.255] * (100) [AS25372i] via 193.25.180.17 on bxe0 [...] Table FLOW4: flow4 { dst 109.68.40.15/32; proto 17; dport 123; } [FLOWSPEC 2023-06-08] * (200) Second example: -- default behavior: # birdc show route 109.68.40.15/32 BIRD 2.13 ready. Network not found # birdc show route 109.68.40.15/32 table all BIRD 2.13 ready. Table IP4: 109.68.40.15/32 unicast [RS0 2023-06-07 from 193.25.180.255] * (100) [AS25372i] via 193.25.180.17 on bxe0 ^^ have to always add 'table all' -- changed behavior looks more logical to me: # birdc show route 109.68.40.15/32 BIRD 2.13 ready. Table IP4: 109.68.40.15/32 unicast [RS0 12:31:26.621 from 193.25.180.255] * (100) [AS25372i] via 193.25.180.17 on bge1 Thus in my opinion, when no tables specified, it's reasonable to select not just default tables but all tables with routes. Such behavior should be closer to other vendors, at least JunOS. Attached patch changes default table selection. Have a nice day! -- Alexander Shikov Technical Staff, Digital Telecom IX http://dtel-ix.net/