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 14:31:41 +0200 [thread overview]
Message-ID: <554CACAD.9070604@pengutronix.de> (raw)
In-Reply-To: <554CAAF1.3040707@actia.se>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On 05/08/2015 02:24 PM, John Ernberg wrote:
> 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.
It probably sets up an etherner bridge and some kind of virtual ethernet
device between the container and the host.
Can you start a container with a working ethernet setup and post the
output of:
brctl show
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 --]
next prev parent reply other threads:[~2015-05-08 12:31 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
2015-05-08 12:24 ` John Ernberg
2015-05-08 12:31 ` Marc Kleine-Budde [this message]
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=554CACAD.9070604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.