Libuavcan does not handle CAN error states – it plows through regardless. If a different behavior is desired, consider implementing it in the application by querying the underlying driver directly. I feel like paging @scottdixon just to keep him in the loop.
This is correct. In v1 we continue with this design where the media layer does not abstract CAN error states but encourages the integrator to expose them from the concrete driver so applications can apply any “back on bus” logic or other bus error state handling that is appropriate for their system.