From: Andri Yngvason <andri.yngvason@marel.com>
To: "Osborne, Paul" <Paul.Osborne@digi.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Expose filtered CAN interface to processes
Date: Mon, 1 Feb 2016 10:13:05 +0000 [thread overview]
Message-ID: <20160201101305.GA3878@maxwell.marel.net> (raw)
In-Reply-To: <EB7F4954055D8D47BE2774BFC0597392301E144B@MTK-SMS-XCH02.digi.com>
On Fri, Jan 29, 2016 at 09:53:01PM +0000, Osborne, Paul wrote:
>
> Hello Oliver/Andri,
>
> >> I am new to network namespaces; Am I missing something? Is this a
> >> real use case for network namespace support? It sounded like there
> >> was uncertainty on this point with the RFC that was posted back in
> >> September by Andri: http://comments.gmane.org/gmane.linux.can/8589.
> >
> > Yes. I think this would be the right way to go.
> >
> > My current idea regarding namespace aware virtual CAN interfaces is to create
> > virtual CAN interfaces inside a network namespace. These 'vcan with namespace'
> > interfaces could then be connected via cangw in the initial (real world)
> > namespace to other can/vcan interfaces (with/without namespace) with cangw rules.
> >
> > The good thing about this approach is that you can use the filter and
> > modification capabilities from cangw at the same time.
>
> Alright, good to know I am not barking up the wrong tree. As I am
> needing this functionality in the not-too-distant future, I may take a
> shot at putting something together based on the work Andri has done
> and your comments.
>
That would be much appreciated. My patch set crashes on my SMP system but not on
a non-SMP qemu VM.
Feel free to ask me questions. I'll try to answer to the best of my knowledge.
Thanks,
Andri
prev parent reply other threads:[~2016-02-01 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 19:06 Expose filtered CAN interface to processes Osborne, Paul
2016-01-29 20:05 ` Oliver Hartkopp
2016-01-29 21:53 ` Osborne, Paul
2016-01-30 10:24 ` Oliver Hartkopp
2016-02-01 10:13 ` Andri Yngvason [this message]
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=20160201101305.GA3878@maxwell.marel.net \
--to=andri.yngvason@marel.com \
--cc=Paul.Osborne@digi.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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;
as well as URLs for NNTP newsgroup(s).