From: Kurt Van Dijck <kurt.van.dijck@eia.be>
To: Wolfgang <wutz@unterderbruecke.de>
Cc: linux-can@vger.kernel.org
Subject: Re: recv list
Date: Tue, 10 Jan 2012 16:23:42 +0100 [thread overview]
Message-ID: <20120110152341.GD2524@e-circ.dyndns.org> (raw)
In-Reply-To: <loom.20120110T112815-928@post.gmane.org>
On Tue, Jan 10, 2012 at 10:45:30AM +0000, Wolfgang wrote:
> > I take back this conclusion. I looked again, and came on this:
> > clear the src_addr.can_ifindex, since that's for sure wrong when bridging.
>
> It is working, thanks.
> As far as I can judge this, your patch is also working I can bind different
> sockets on one interface, and then send with different src addr.
Thanks for testing!
>
>
> > In a later iteration, You could (if necessary, since I have no clue what kind
> > of traffic you will bridge):
> > * make the receiving socket (s) 'promiscuous', i.e. receiving all traffic.
> > * fetch the original destination by using recvmsg() as illustrated in jspy
>
> OK, I think I am that far, making one socket promiscuous and than depending
> on the source address send it with the corresponding socket.
> Is there any 'easy' iteration, of that. Or do I have to rebuild the jspy.c,
> libj1939.c, libj1939.h according to my wishes?
jspy just serves as illustration here. I don't think you will need the binary.
But I consider using recvmsg() a bit complicated, easily forgotten ...
Kind regards,
Kurt
next prev parent reply other threads:[~2012-01-10 15:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 13:26 recv list Kurt Van Dijck
2012-01-09 16:35 ` Wolfgang
2012-01-10 8:51 ` Kurt Van Dijck
2012-01-10 10:45 ` Wolfgang
2012-01-10 15:23 ` Kurt Van Dijck [this message]
2012-01-11 16:06 ` promiscuous mode Wolfgang
2012-01-12 15:37 ` bridge Kurt Van Dijck
2012-01-12 15:23 ` recv list Wolfgang
2012-01-12 15:43 ` Kurt Van Dijck
2012-01-12 18:08 ` bridging with can-gw - was " Oliver Hartkopp
2012-01-13 11:12 ` bridging with can-gw Kurt Van Dijck
2012-01-13 11:31 ` Wolfgang
2012-01-16 10:04 ` MSG_DONTROUTE Wolfgang
2012-01-16 13:31 ` MSG_DONTROUTE Kurt Van Dijck
2012-01-16 15:28 ` sendmsg Wolfgang
2012-01-16 15:36 ` sendmsg Kurt Van Dijck
2012-02-07 14:21 ` max dlc Wolfgang
2012-02-07 15:11 ` sendmsg Wolfgang
2012-02-08 8:46 ` sendmsg Kurt Van Dijck
2012-02-16 9:58 ` How to get the DA Wolfgang Wagner
2012-02-16 19:49 ` Kurt Van Dijck
2012-02-24 15:23 ` Transport Protocol Wolfgang Wagner
2012-02-27 14:05 ` Kurt Van Dijck
2012-02-28 10:46 ` Transport Protocol: example Kurt Van Dijck
2012-02-28 15:21 ` Wolfgang Wagner
2012-02-28 16:26 ` Kurt Van Dijck
-- strict thread matches above, loose matches on Subject: below --
2011-12-20 15:05 API calls Kurt Van Dijck
2011-12-20 15:43 ` Wolfgang
2011-12-20 16:32 ` Kurt Van Dijck
2011-12-21 10:46 ` Wolfgang
2011-12-21 13:43 ` using can-j1939 Kurt Van Dijck
2011-12-21 15:11 ` Wolfgang
2011-12-21 15:53 ` Kurt Van Dijck
2011-12-22 13:06 ` Wolfgang
2011-12-23 11:04 ` Kurt Van Dijck
2011-12-28 10:49 ` Wolfgang
2012-01-04 9:47 ` Kurt Van Dijck
2012-01-04 16:28 ` recv list Wolfgang
2012-01-04 20:41 ` Kurt Van Dijck
2012-01-05 10:55 ` Wolfgang
2012-01-05 12:09 ` Kurt Van Dijck
2012-01-05 21:24 ` Wolfgang
2012-01-06 12:25 ` Kurt Van Dijck
2012-01-06 18:25 ` Wolfgang
2012-01-09 9:33 ` Kurt Van Dijck
2012-01-09 10:46 ` Wolfgang
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=20120110152341.GD2524@e-circ.dyndns.org \
--to=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.org \
--cc=wutz@unterderbruecke.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 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).