From: John Ernberg <john.ernberg@actia.se>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
"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 12:40:14 +0000 [thread overview]
Message-ID: <554CAEB0.8000302@actia.se> (raw)
In-Reply-To: <554CACAD.9070604@pengutronix.de>
On 2015-05-08 14:31, Marc Kleine-Budde wrote:
> 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
>
Here's what my ifconfig and brctl looks like when I am running a
container with working ethernet bridging.
$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:62708 errors:0 dropped:0 overruns:0 frame:0
TX packets:62708 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26174279 (26.1 MB) TX bytes:26174279 (26.1 MB)
lxcbr0 Link encap:Ethernet HWaddr fe:8e:ec:8f:13:24
inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0
inet6 addr: fe80::801b:d5ff:fe73:3464/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9845 (9.8 KB) TX bytes:20560 (20.5 KB)
vcan0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vethTRGO6W Link encap:Ethernet HWaddr fe:8e:ec:8f:13:24
inet6 addr: fe80::fc8e:ecff:fe8f:1324/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3787 (3.7 KB) TX bytes:8005 (8.0 KB)
$ brctl show
bridge name bridge id STP enabled interfaces
lxcbr0 8000.fe8eec8f1324 no vethTRGO6W
Best regards // John Ernberg
next prev parent reply other threads:[~2015-05-08 12:40 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
2015-05-08 12:40 ` John Ernberg [this message]
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=554CAEB0.8000302@actia.se \
--to=john.ernberg@actia.se \
--cc=adam.engstrom@actia.se \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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.