CONFIG_CAN_VXCAN: Virtual CAN Tunnel (vxcan)

General informations

The Linux kernel configuration item CONFIG_CAN_VXCAN:

• prompt: Virtual CAN Tunnel (vxcan)
• type: tristate
• depends on: (none)
• defined in drivers/net/can/Kconfig
• found in Linux kernels: 4.12–4.20, 5.0–5.19, 6.0–6.12
• modules built: vxcan

Help text

Similar to the virtual ethernet driver veth, vxcan implements a local CAN traffic tunnel between two virtual CAN network devices. When creating a vxcan, two vxcan devices are created as pair. When one end receives the packet it appears on its pair and vice versa. The vxcan can be used for cross namespace communication.

In opposite to vcan loopback devices the vxcan only forwards CAN frames to its pair and does *not* provide a local echo of sent CAN frames. To disable a potential echo in af_can.c the vxcan driver announces IFF_ECHO in the interface flags. To have a clean start in each namespace the CAN GW hop counter is set to zero.

This driver can also be built as a module. If so, the module will be called vxcan.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module vxcan CONFIG_CAN_VXCAN : drivers/net/can/Kconfig : "Virtual CAN Tunnel (vxcan)" # in 4.12–4.20, 5.0–5.19, 6.0–6.12

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: