#socket-can #tokio #sockets #linux #future #stream

tokio-socketcan

Asynchronous Linux SocketCAN sockets with tokio

7 releases

0.3.1 Nov 17, 2021
0.3.0 Feb 10, 2021
0.2.0 Nov 12, 2020
0.1.3 Feb 23, 2019
0.1.1 Jan 10, 2019

#572 in Asynchronous

Download history 282/week @ 2024-01-07 495/week @ 2024-01-14 436/week @ 2024-01-21 612/week @ 2024-01-28 555/week @ 2024-02-04 398/week @ 2024-02-11 379/week @ 2024-02-18 429/week @ 2024-02-25 432/week @ 2024-03-03 567/week @ 2024-03-10 401/week @ 2024-03-17 434/week @ 2024-03-24 454/week @ 2024-03-31 601/week @ 2024-04-07 761/week @ 2024-04-14 606/week @ 2024-04-21

2,428 downloads per month
Used in 4 crates

MIT license

14KB
201 lines

crates.io badge documentation Continuous integration

tokio-socketcan

SocketCAN support for tokio based on the socketcan crate.

Example echo server

use futures_util::stream::StreamExt;
use tokio_socketcan::{CANSocket, Error};

#[tokio::main]
async fn main() -> Result<(), Error> {
    let mut socket_rx = CANSocket::open("vcan0")?;
    let socket_tx = CANSocket::open("vcan0")?;
    while let Some(Ok(frame)) = socket_rx.next().await {
        socket_tx.write_frame(frame)?.await?;
    }
    Ok(())
}

Testing

Integrating the test into a CI system is non-trivial as it relies on a vcan0 virtual can device existing. Adding one to most linux systems is pretty easy with root access but attaching a vcan device to a container for CI seems difficult to find support for.

To run the tests locally, though, setup should be simple:

sudo modprobe vcan
sudo ip link add vcan0 type vcan
sudo ip link set vcan0 up
cargo test

Dependencies

~5–18MB
~191K SLoC