Confirmed on the 2020-12-31 build too.
Take this config:
route 0.0.0.0/0 { next-hop x.x.x.x { } } table 146 { interface-route 0.0.0.0/0 { next-hop-interface tun2 { } } } table 200 { interface-route 0.0.0.0/0 { next-hop-interface wg4 { } } }
Results in
S>* 0.0.0.0/0 [1/0] is directly connected, tun2, weight 1, 00:03:46 * is directly connected, wg4, weight 1, 00:03:46 * via x.x.x.x, eth0.7, weight 1, 00:03:46 (normal default gateway)
That's bad, it should look like:
S>* 0.0.0.0/0 [1/0] via x.x.x.x, eth0.7, 02:35:00
After a reboot, this is what vtysh looks like (missing the table options)
ip route 0.0.0.0/0 x.x.x.x ip route 0.0.0.0/0 wg4 ip route 0.0.0.0/0 tun2
If I delete the two table X configs and readd them, the appropriate config happens in vtysh
ip route 0.0.0.0/0 tun2 table 146 ip route 0.0.0.0/0 wg4 table 200 ip route 0.0.0.0/0 x.x.x.x
So something happens during a reboot that prevents the table from getting added to FRR, but it works fine if configing from the CLI (until a reboot)