Martin Hundebøll

Hi @stoupa-cz Thanks for working on this. I've been experimenting with `[socketcand](https://github.com/linux-can/socketcand)`. It has the same limitation as `cannelloni` (root on both ends for `vcan` setup), but the protocol is...

> > Hi @stoupa-cz > > Thanks for working on this. I've been experimenting with `[socketcand](https://github.com/linux-can/socketcand)`. It has the same limitation as `cannelloni` (root on both ends for `vcan` setup),...

Hi @stoupa-cz I tried running an exporter with your PR, where a `USBCANPort` is exported as an `NetworkCANPort`. On the client, I implemented the `cannelloni` protocol in the driver ([can.py](https://github.com/user-attachments/files/24166243/can.py))....

> It seems we have different needs. For us, a client-side "real" `vcan` interface is necessary. Fortunately, we have a configurable driver, so any client (e.g., your cannelloni protocol reimplementation)...

> On exporter side, the interface is controlled (e.g., down, set-bitrate, up) when the place is acquired. The bitrate configuration comes from the expoter configuration. It is similar on client...

I agree. Just let the CANPort resource default to no bitrate setting, and only run `ip link ...` commands if a bitrate is configured. Having a default is probably bad...

@jluebbe @Bastian-Krause What do you think?