SocketCAN
The Linux CAN networking stack that exposes CAN controllers as network interfaces and accesses them through the Berkeley socket model.
SocketCAN turns CAN from a vendor-specific character-device API into a native part of the Linux networking model. Controllers appear as network interfaces such as can0, while user space communicates through PF_CAN sockets.
Multi-Process Access and Filtering
Multiple processes can bind to the same CAN interface. Raw-socket filters can be evaluated in the kernel, avoiding unnecessary delivery of every frame to user space. Timestamping and error frames are also useful for capture and diagnostic tooling.
The socket API resemblance to IP networking does not make CAN arbitration, frame size, or transport guarantees equivalent to Ethernet/TCP.
Source
- https://docs.kernel.org/networking/can.html