Can support at Linux LXC?

DISCUSSION Dererk 2 participants 3 messages Nov 20, 2015 – Nov 21, 2015 CAN network drivers

Share & tools

Dererk

author

2015-11-20 21:52 UTC #0 lore raw

Hi!

I'm playing with some bus CANs and linux LXC. But it seems that there must be some kind of support missing on the LXC side.
Even vcan seems to have the very same results on it when trying to open the socket:

socket(PF_CAN, SOCK_RAW, 1) = -1 EAFNOSUPPORT (Address
family not supported by protocol)

Have you have any experience with this?

Is there a proper place where I could route this doubts at an specialized mailing list on the linux kernel that you know might be more appropiate?

Thanks in advance!

Cheers,

Dererk

Signature · 2 lines

BOFH excuse #449:
greenpeace free'd the mallocs

Oliver Hartkopp

2015-11-21 12:33 UTC #1 lore raw

Hi Dererk,

Quoted 9 lines · Dererk

I'm playing with some bus CANs and linux LXC. But it seems that there must be some kind of support missing on the LXC side.
Even vcan seems to have the very same results on it when trying to open the socket:
socket(PF_CAN, SOCK_RAW, 1) = -1 EAFNOSUPPORT (Address
family not supported by protocol)
Have you have any experience with this?

Looks like CONFIG_CAN and other CAN specific components are not enabled in your kernel.

Debian kernels usually have this enabled:

$ grep CONFIG_CAN /boot/config-3.16.0-4-amd64
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m
CONFIG_CAN_VCAN=m
CONFIG_CAN_SLCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_LEDS is not set
CONFIG_CAN_SJA1000=m
CONFIG_CAN_SJA1000_ISA=m
# CONFIG_CAN_SJA1000_PLATFORM is not set
CONFIG_CAN_EMS_PCMCIA=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_PEAK_PCMCIA=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=y
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_C_CAN is not set
# CONFIG_CAN_CC770 is not set
# CONFIG_CAN_MCP251X is not set
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
CONFIG_CAN_GS_USB=m
CONFIG_CAN_KVASER_USB=m
CONFIG_CAN_PEAK_USB=m
CONFIG_CAN_8DEV_USB=m
CONFIG_CAN_SOFTING=m
CONFIG_CAN_SOFTING_CS=m
# CONFIG_CAN_DEBUG_DEVICES is not set

Quoted 3 lines

Is there a proper place where I could route this doubts at an specialized mailing list on the linux kernel that you know might be more appropiate?

You are definitely at the right place for CAN related questions here :-)

Best regards,
Oliver

Oliver Hartkopp

2015-11-21 12:58 UTC #2 lore raw

Hi Dererk,

just looked for more LXC information.

The Linux CAN subsystem is currently not aware of net namespaces.

We already had some discussions about it:
http://marc.info/?l=linux-can&w=2&r=1&s=namespace&q=b

but it did not get further from the last posting of Andri Yngvason as we all seem not to be the name space specialists.

Regards,
Oliver

Quoted 67 lines · Oliver Hartkopp

Hi Dererk,
Quoted 9 lines · Dererk
I'm playing with some bus CANs and linux LXC. But it seems that there must be some kind of support missing on the LXC side.
Even vcan seems to have the very same results on it when trying to open the socket:
socket(PF_CAN, SOCK_RAW, 1) = -1 EAFNOSUPPORT (Address
family not supported by protocol)
Have you have any experience with this?
Looks like CONFIG_CAN and other CAN specific components are not enabled in your kernel.
Debian kernels usually have this enabled:
$ grep CONFIG_CAN /boot/config-3.16.0-4-amd64
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m
CONFIG_CAN_VCAN=m
CONFIG_CAN_SLCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
# CONFIG_CAN_LEDS is not set
CONFIG_CAN_SJA1000=m
CONFIG_CAN_SJA1000_ISA=m
# CONFIG_CAN_SJA1000_PLATFORM is not set
CONFIG_CAN_EMS_PCMCIA=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_PEAK_PCMCIA=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=y
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PLX_PCI=m
# CONFIG_CAN_C_CAN is not set
# CONFIG_CAN_CC770 is not set
# CONFIG_CAN_MCP251X is not set
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
CONFIG_CAN_GS_USB=m
CONFIG_CAN_KVASER_USB=m
CONFIG_CAN_PEAK_USB=m
CONFIG_CAN_8DEV_USB=m
CONFIG_CAN_SOFTING=m
CONFIG_CAN_SOFTING_CS=m
# CONFIG_CAN_DEBUG_DEVICES is not set
Quoted 3 lines
Is there a proper place where I could route this doubts at an specialized mailing list on the linux kernel that you know might be more appropiate?
You are definitely at the right place for CAN related questions here :-)
Best regards,
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-can" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html