Blog

Use the ingress bus, frame format and message schema as part of a gateway route key. Two independent CAN segments can legitimately assign different meanings to the same numeric identifier. Forwarding both unchanged into one destination segment can erase that distinction and create conflicting producers. This guide uses Linux v6.12 SocketCAN provenance as the implementation…

Enable and validate socket-loss telemetry, then treat a positive loss indication as a gap in that consumer’s evidence. A CAN receiver can keep returning valid frames after its queue has dropped earlier ones. Those later frames do not prove that a state estimate built from every expected update remains correct. This guide pins the Linux…

Track a J1939 ECU by its protocol NAME within a bus context, and treat its current source address as a changeable mapping with a validity state. Reusing an address does not prove that the same ECU is still there. Seeing a NAME in a claim also does not authenticate a physical device cryptographically. This guide…

Budget complete-PDU storage separately from flow-control pacing, and impose an independent operation deadline when waiting must be bounded. In Linux v6.12, reducing ISO-TP block size does not turn the userspace receive API into a stream of application-consumed blocks. Nor does the presence of a wait-count option prove that every peer wait is bounded by it….

Classify an error frame before identifier routing, then decode only fields made meaningful by its error-class bits. SocketCAN error notifications use the same general receive mechanism as traffic, but their data bytes describe diagnostics. Passing them into an application’s measurement or command decoder can manufacture plausible values from unrelated status. This guide pins Linux v6.12’s…

Compare the realized timing tuple and its clock assumptions, not just the requested bitrate. Two CAN controllers can report the same bit rate while using different time quanta, sample points and synchronization limits. That difference requires a margin review; it does not automatically prove that the pair is incompatible. This procedure pins Linux v6.12’s timing…

Label a SocketCAN observation by where it was produced before using it as delivery evidence. A successful send, a locally echoed frame, a controller-level transmit completion and a remote application’s response are different events. Even the local echo’s timing depends on whether the driver or the CAN core produced it. This guide pins Linux v6.12…

Define a receive rule as identifier bits plus relevant frame flags, then test its Boolean combination with every other rule. Matching only the low eleven identifier bits can admit extended frames and remote-transmission requests that a standard-data consumer never intended to process. This guide pins Linux v6.12 CAN_RAW behavior. The worked examples concern ordinary Classical…

Choose one SocketCAN bus-off recovery owner and distinguish restart requests, early restart notifications, driver outcomes and application resynchronization.