Hello all,
I looked at the code of can-utils and more precisely jacd.c.
In the way it is implemented, the deamon's only objective is to change
its address according to the different requests it receives.
More precisely, the socket is blocked until the next received claiming
address request (recvfrom).
In a real implementation, do you need two sockets?
- one to receive and write messages
- another dedicated only to the claiming address
Or did you have another solution?
In the documentation, it says: "If another ECU claims the address, the
kernel will mark the NAME-SA expired", how can this be checked?
Do you plan to integrate the management of the claiming address (jacd.c)
into the kernel or leave it to the user?
Thank you very much.
Best regards
--
Arthur Guyader - Embedded Engineer - IoT.bzh
