Linux CAN drivers development
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: John Ernberg <john.ernberg@actia.se>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: "Adam Engström" <adam.engstrom@actia.se>
Subject: Re: Raw CAN socket support in LXC?
Date: Fri, 8 May 2015 13:54:35 +0200	[thread overview]
Message-ID: <554CA3FB.6070307@pengutronix.de> (raw)
In-Reply-To: <554C9B67.1030201@actia.se>

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

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

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2015-05-08 11:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  8:12 Raw CAN socket support in LXC? John Ernberg
2015-05-08  8:28 ` Marc Kleine-Budde
2015-05-08  8:45   ` John Ernberg
2015-05-08  8:54     ` Marc Kleine-Budde
2015-05-08 11:17       ` John Ernberg
2015-05-08 11:54         ` Marc Kleine-Budde [this message]
2015-05-08 12:24           ` John Ernberg
2015-05-08 12:31             ` Marc Kleine-Budde
2015-05-08 12:40               ` John Ernberg
2015-05-11 11:45         ` Pavel Pisa
2015-05-11 13:06           ` John Ernberg
2015-05-12 18:09             ` Oliver Hartkopp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=554CA3FB.6070307@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=adam.engstrom@actia.se \
    --cc=john.ernberg@actia.se \
    --cc=linux-can@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox