ISOTP module does not ignore the priority bits (high 3 bits of extended ID) about can-isotp HOT 4 CLOSED

Looks like as a quick fix, patching the ISOTP module locally to mask off the J1939 priority bits works, and we'll look into a kernel upgrade. Thanks again for your help!

from can-isotp.

This reference from Annex A is a J1939 addressing topic - you can check for the CAN_J1939 protocol inside the kernel, see priority handling here:

https://github.com/torvalds/linux/blob/master/net/can/j1939/main.c#L330

The native ISO15765-2 protocol is a point-to-point transport protocol on two single CAN Identifiers, not to a bunch of CAN IDs.

from can-isotp.

Thanks for the quick reply! I did not know there was J1939 support within the kernel. I'm not sure we can use it on our old kernel (3.18) but I'll look into it.

from can-isotp.

You should really try to upgrade your 3.18 (Android??) kernel!
The J1939 implementation had several implementation and integration steps until it was upstreamed for the mainline kernel.
So it could be that you find an older version, which probably fits into the 3.18, but which might have an outdated user-space socket API.

from can-isotp.