Linux CAN drivers development
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Angeloni Andrea <andrea.angeloni@alfamationglobal.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: BCM loopback - Information request
Date: Tue, 20 Sep 2016 11:53:33 +0200	[thread overview]
Message-ID: <1509366.LC0YPQ3zn0@ws-stein> (raw)
In-Reply-To: <BECC71D675C45C4F912901A0BBE9A3A41493CD7D@srv-mail.DominioAlfa.local>

Hi Andrea,

On Tuesday 20 September 2016 09:42:53, Angeloni Andrea wrote:
> In my application there is a thread for each initialized CAN interface that
> sends over TCP all the read data to a Windows Client. Data are read using
> Socket RAW. Application is also capable to send cyclic messages using
> Broadcast manager.
> 
> Here is my question: how can I configure my application so that reading
> thread does not get messages sent by BCM on the same interface?

I think the socket option CAN_RAW_LOOPBACK is what you need. Please refer to 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/can.txt#n536
You will not receive CAN frames sent from interface (BCM and other CAN 
frames), thus only messages from other CAN nodes.

HTH
Alexander


  reply	other threads:[~2016-09-20  9:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20  9:42 BCM loopback - Information request Angeloni Andrea
2016-09-20  9:53 ` Alexander Stein [this message]
2016-09-20 10:19   ` Angeloni Andrea
2016-09-20 15:06     ` Oliver Hartkopp
2016-09-20 15:19       ` Angeloni Andrea
2016-09-20 15:29         ` Oliver Hartkopp
2016-09-20 15:43           ` Angeloni Andrea
2016-09-21 13:35           ` Angeloni Andrea
2016-09-21 15:03           ` Angeloni Andrea

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=1509366.LC0YPQ3zn0@ws-stein \
    --to=alexander.stein@systec-electronic.com \
    --cc=andrea.angeloni@alfamationglobal.com \
    --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