The tcp client on the control panel currently is a custom implementation, (which also doesn't work). Instead we should link the the can-tcp-bridge-rs project and use it's implementations sending and receiving on tcp to make the communication consistant across the projects.
Important note here is that can-tcp-bridge-rs currently is using socketcan by default, which implies the libc dependency, which is only avaiable on linux. Therefor it is required to make socketcan an optional feature there!
The tcp client on the control panel currently is a custom implementation, (which also doesn't work). Instead we should link the the can-tcp-bridge-rs project and use it's implementations sending and receiving on tcp to make the communication consistant across the projects.
Important note here is that can-tcp-bridge-rs currently is using socketcan by default, which implies the libc dependency, which is only avaiable on linux. Therefor it is required to make socketcan an optional feature there!