Skip to main content

python-can-hub

Native python-can backend for can-hub: consume remote CAN interfaces exported by can-hub agents, directly over the binary protocol — unix socket, plain TCP, TLS or QUIC, with mTLS identity and TOFU pinning on the encrypted transports. No bridge process in between.

import can

bus = can.Bus(
    interface="canhub",
    channel="truck42/can0",
    url="quic://hub.example.com:7227",
)
bus.send(can.Message(arbitration_id=0x123, data=b"\xDE\xAD\xBE\xEF"))
for message in bus:
    print(message)
  • channel: namespaced interface agent/iface (or the numeric id from can-hub-client list).
  • url: omit to connect to the local hub unix socket.
  • state_dir: client TLS identity + pin store location (tls/quic).
  • receive_own_messages: standard python-can echo semantics.
  • reliable: carry the channel on a dedicated reliable QUIC stream (lossless, ordered) instead of the lossy datagram plane. Needs a quic:// url and a hub that advertises the capability; otherwise the open fails.
  • ignore_rx_error_frames: drop the controller error frames (is_error_frame), received by default as on python-can's socketcan interface.

Received messages are canhub.CanHubMessage, a can.Message with one more attribute: bridged is true when the hub injected the frame into this bus along a bridge route or group.

Write access follows the hub client ACLs: if the ACL grants read-only, the bus opens read-only and send() raises.

The bus is thread-safe: a can.Notifier receiving in its thread while other threads call send() is supported. Calls into the native session are serialised first come, first served, and a blocking receive gives way to a waiting send within about 10 ms.

Drop counters

Two drops happen inside the library and never reach the hub, so the hub's own counters cannot show them: send() raises when the pace relayed by the hub leaves no budget for the frame, and the receive ring overwrites its oldest entry when you read slower than the bus produces. drop_counters() returns both as monotonic totals, so a quiet bus is distinguishable from a lossy one:

bus.drop_counters()     # {"rate_limited": 0, "ring_dropped": 12}

Configuring the interface

configure() reconfigures the bus's interface on its agent, everything in one step, with the keywords of ip link set ... type can; interface_settings() reads it back. The bus must be opened by its agent/iface name, and the hub allows it only with an rwa ACL grant (unix and plain tcp clients are trusted).

bus.configure(bitrate=500000, sample_point=0.875, fd=True, data_bitrate=2000000)
bus.configure(restart_ms=100, txqueuelen=1000, termination=120, listen_only=False, up=True)
from canhub import BitTiming
bus.configure(bit_timing=BitTiming(tq=125, prop_seg=6, phase_seg1=7, phase_seg2=2, sjw=1))
bus.interface_settings()
# InterfaceSettings(up=True, state='error-active', bitrate=500000, sample_point=0.875, ...)

Both return an InterfaceSettings with None where the device reports nothing (a vcan has no bit timing). A refusal raises CanOperationError with the reason.

Listing interfaces

CanHubBus.list_interfaces() asks a hub for the interfaces it exports. Each entry is a python-can config dict you can splat straight into can.Bus:

from canhub import CanHubBus
import can

for config in CanHubBus.list_interfaces(url="quic://hub.example.com:7227"):
    print(config["channel"])          # e.g. "can-agent/can0"
bus = can.Bus(**CanHubBus.list_interfaces()[0])   # first interface, local hub

It accepts the same connection arguments as the bus (url, identity_cert, identity_key, hub_fingerprint, state_dir); omit url to query the local hub unix socket.

This also wires python-can's discovery: can.detect_available_configs("canhub") returns the same dicts. With no explicit target it reads the connection from the environment — CANHUB_URL, CANHUB_STATE_DIR, CANHUB_IDENTITY_CERT, CANHUB_IDENTITY_KEY, CANHUB_HUB_FINGERPRINT — falling back to the local hub unix socket. So CANHUB_URL=quic://hub.example.com:7227 points discovery at a remote host without any code.

The wheel bundles libcanhub.so with the TLS/QUIC stack linked in statically; the only runtime dependency is glibc.

Testing

The unit tests stub the native library, so they run without a build:

pip install -e python/.[test]
pytest python/tests

The backend is also exercised end-to-end against real binaries (recv, send, list_interfaces, and can.detect_available_configs discovery) by test/e2e/tests/python_can.robot; run the whole bench with make e2e.

Building from source

./scripts/build-python-wheel.sh        # host arch, glibc-tagged (local dev)
pip install python/dist/*.whl

Distributable manylinux wheels are built per architecture in a manylinux container and repaired by auditwheel (needs docker, plus QEMU binfmt for the cross arches):

./scripts/build-python-wheel.sh x86_64   # python/dist/x86_64/*.whl
./scripts/build-python-wheel.sh aarch64
./scripts/build-python-wheel.sh armv7l

The release workflow builds these three on native runners (aarch64/armv7l on the arm64 hosted runner, no QEMU) plus a cross-compiled win_amd64 wheel, and publishes all four to PyPI on a v* tag.

Metadata

Release files for python-can-hub 0.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for python-can-hub 0.5.1
File Actions
python_can_hub-0.5.1-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for python_can_hub-0.5.1-py3-none-win_amd64.whl
python_can_hub-0.5.1-py3-none-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl Python 3 none Linux glibc 2.26+ x86-64, Linux glibc 2.28+ x86-64 Details for python_can_hub-0.5.1-py3-none-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl
python_can_hub-0.5.1-py3-none-manylinux_2_26_armv7l.manylinux_2_31_armv7l.whl Python 3 none Linux glibc 2.26+ ARMv7l, Linux glibc 2.31+ ARMv7l Details for python_can_hub-0.5.1-py3-none-manylinux_2_26_armv7l.manylinux_2_31_armv7l.whl
python_can_hub-0.5.1-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl Python 3 none Linux glibc 2.28+ ARM64, Linux glibc 2.26+ ARM64 Details for python_can_hub-0.5.1-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Total release size: 3.1 MB

Release files / python_can_hub-0.5.1-py3-none-win_amd64.whl

Download URL python_can_hub-0.5.1-py3-none-win_amd64.whl
Size 714.1 kB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
c128ed20f3fa2e2ae5ce2a8084a74660d90481503aa325a200f5677ed8d19590
BLAKE2b-256 checksum
How to use checksums
27fc811784c49732fe3c4b80c78ed47280d4cfa077e8874ea44aab707a4b99d8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / python_can_hub-0.5.1-py3-none-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl

Download URL python_can_hub-0.5.1-py3-none-manylinux_2_26_x86_64.manylinux_2_28_x86_64.whl
Size 923.8 kB
Tags Linux glibc 2.26+ x86-64 Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
d2fddfc5be9caae5c4bb392d1d367cdd3c8d277cf1c925f7c14d59ee64c822e1
BLAKE2b-256 checksum
How to use checksums
c2f8db04f470ade00d71037e52775e655beda0eec01bc3e6ae6edbf5d4d057d9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / python_can_hub-0.5.1-py3-none-manylinux_2_26_armv7l.manylinux_2_31_armv7l.whl

Download URL python_can_hub-0.5.1-py3-none-manylinux_2_26_armv7l.manylinux_2_31_armv7l.whl
Size 750.4 kB
Tags Linux glibc 2.26+ ARMv7l Linux glibc 2.31+ ARMv7l Python 3
SHA-256 checksum
How to use checksums
84397d4fe5be4f9bc3c96982274748caf7894d0fa924673d7d9b16ff61aa21b7
BLAKE2b-256 checksum
How to use checksums
c9411cbaddb4956ed99a131d0da3cda1e972b19515c360a6a4edff6b361bd6bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / python_can_hub-0.5.1-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl

Download URL python_can_hub-0.5.1-py3-none-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
Size 739.6 kB
Tags Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 Python 3
SHA-256 checksum
How to use checksums
ec1e46f8da710377db17914151128c0333f7b6e250aa61fd65e81773404a905f
BLAKE2b-256 checksum
How to use checksums
c4ef12e36df130b33c91c19cc2c7c5de2454d8cae8a5f33da0e36139641b5594
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Security for python-can-hub 0.5.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 4 files in this release have been uploaded with provenance metadata.

Select from 4 files

Attestation for python_can_hub-0.5.1-py3-none-win_amd64.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page