route leaking between vrfs and commits
-
I come from a heavy Juniper background so my questions are framed on that.
For route leaking between VRFs, i am reviewing the documentation here
https://docs.netgate.com/tnsr/en/latest/routing/route-tables.html#communicate-between-vrfsIs there a way to apply a prefix list (or route filter) instead of marking each route to be accessible through the next hop?
If i can use a range such as 192.168.1.0/24 ge 32 is much better than listing each route separately.Lastly, arguably the best feature of JunOS is the 'commit confirmed'. Adding guard rails to configuration helps the admin avoid potential pitfalls of a misconfiguration or device lockout. This would be my most requested feature for sure. Having a configuration commit while writing it in the cli is something that is insane.