Hello Chris,
Thanks for update. I currently have no access to a real CAN, but I can
setup vcan/socketcan interface over weekend and give a spin to the
effort you did. By this way I will be able to confirm if both reading
and writing is working.
I know that netty forced us to do quite a lot of wrapping around
JavaCAN, so with plain IO it should be much simpler!
Cheers,
Łukasz
On 3/20/26 18:41, Christofer Dutz wrote:
Hi all,
I just wanted to inform you that I’ve finished my work on porting the remaining
transports to the new SPI3 structure.
I’ve also added a new transport (TLS), which is just the short form of
TLS-over-TCP … this contains two transport: tls and tls-psk
TLS is for certificate-based TLS and can handle both self-signed-certificates
as well as a shared trusted authority.
TLS-PSK uses a pre-shared key for securing the connection.
I have been extensively using the:
*
TCP
*
UDP
*
Serial
*
TLS
*
Test
Transports and am pretty confident that they are rock-solid.
*
Raw-Sockets
*
Pcap-Replay
Not quite tested that well in real life scenarios, but I’m hoping to get to
that point pretty soon.
With CAN, I would like to ask Lukasz to have a look, as I don’t have any CAN
equipment for testing.
So .. please have a look at the PR and leave some comments and feedback there.
Chris
