Re: Raw CAN socket support in LXC?

[John Ernberg <john.ernberg@actia.se>]

On 2015-05-08 13:54, Marc Kleine-Budde wrote:
> On 05/08/2015 01:17 PM, John Ernberg wrote:
>> On 2015-05-08 10:54, Marc Kleine-Budde wrote:
>>> On 05/08/2015 10:45 AM, John Ernberg wrote:
>>>> Our main use-case is to prevent a possible misbehaving application to
>>>> bring down the entire system through memory leaks, crashes etc.
>>>> At this time we have not considered any filtering or blocking of directions.
>>> Can you see the your CAN interface inside of the LXC container? Or are
>>> the RAW sockets the problem?
>>>
>>> Marc
>>>
>>> btw: you can use systemd to do memory limiting, too. It makes use of the
>>> same feature in the kernel (cgroups).
>>>
>> Hi
>>
>> With the experimenting I have been able to do on an Ubuntu 14.04 LTS
>> computer, I cannot find any CAN or virtual CAN interfaces inside the
>> container.
>> When I change the config to specifically forward CAN interfaces, like this:
>> lxc.network.type = can
>> lxc.network.link = lxcbr0
>> lxc.network.flags = up
>> lxc.network.hwaddr = 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> You're probably following an ethernet example here, right? So let's
> first figure out, that lxc does in the background and see how this
> translates into the CAN world.
>
> Marc
>
Hi

I first tried to figure out what kind of settings that would be the most 
appropriate to tinker with, but I could not find anything more relevant 
so I copied the ethernet example in the end.
I will dig into the LXC code and see what can be done in terms of 
getting the CAN network interfaces through.

Best regards // John Ernberg