Hello Kurt, > IMO, a CAN frame from another socket should be treated as coming from > another bus node. > I know (J1939 is still in the queue) that some protocols may benefit from > several sockets cooperating, but should that be exported to userspace?
I fully agree on that. Two different sockets shall behave as two different CAN nodes on the same CAN bus even if they are opened on the same hardware. Taking that in to account vcan shall be actually called "virtual CAN bus" and not "virtual CAN interface"... My understanding of "self-reception" per-socket option is that the messages send over the specific socket are not only received by other sockets on the same HW, but also by the original socket (so "echo" may be even better name for that). And the reason why I want to receive (some of) my own Tx messages is because I want to know *exactly* when whose messages where physically send over CAN bus. And that I am getting by reading the timestamp of my self-received message. And the per-message self-receive flag helps me to distinguish between Rx messages (coming from other CAN nodes or other sockets on the same CAN node) and my own Tx messages. Regards, Vladislav _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
